The ADKAR model is a popular change management framework that helps individuals and organizations understand the stages of change, and how to manage change effectively. The ADKAR model was developed by Jeff Hiatt, the founder of Prosci, a leading change management firm.

ADKAR is an acronym that stands for:

1. Awareness: This stage involves creating awareness about the need for change among the people who will be affected by it. This includes understanding the reasons for the change, the benefits of the change, and the potential impact of the change.

2. Desire: In this stage, individuals need to have a desire to support the change. This involves understanding why the change is necessary and how it will benefit them and the organization.

3. Knowledge: Once individuals have a desire to support the change, they need to acquire the knowledge necessary to make the change successfully. This includes training, education, and communication about the change.

4. Ability: In this stage, individuals must have the skills and ability to make the change happen. This may involve providing additional resources, tools, or support to help people adapt to the change.

5. Reinforcement: Finally, in this stage, individuals need to be reinforced and rewarded for making the change. This includes recognizing and celebrating successes, and providing ongoing support and encouragement to ensure that the change becomes a part of the organizational culture.

The ADKAR model is a useful framework for managing change because it focuses on the individual level, and helps to ensure that people have the necessary knowledge, skills, and motivation to make the change happen. By following the ADKAR model, organizations can increase their chances of success and achieve their desired outcomes.

PMI (the Project Management Institute) has recently introduced new content into it's curriculum....the Process Owner and Process Manager.  The distinction between these two roles seems to originate from ServiceNow's influence.

In small organizations the same person wears both hats, but in larger organizations these two roles may be split between two people.  Basically the Process Owner is a senior person responsible for "working on" the process, to improve it, while the Process Manager "works in" the process to execute it with efficiency.  A description of each role follows:

Job Description for Process Owner:

Process Owner's are responsible for the end-to-end oversight of a particular business process within an organization. Their main responsibilities include designing, implementing, monitoring, and continuously improving the process to ensure it meets the organization's goals and objectives. Process owners also ensure that the process is compliant with regulatory requirements and industry standards. They work closely with cross-functional teams to identify areas for improvement and implement changes that increase efficiency, reduce costs, and enhance quality. Other key responsibilities of a process owner include:

• Developing and maintaining process documentation, including standard operating procedures (SOPs), process flowcharts, and process metrics.
• Monitoring process performance using key performance indicators (KPIs) and other metrics, and identifying areas for improvement. (Note, both roles include this bullet point as it is an ongoing common point of review and discussion.)
• Leading process improvement initiatives, including process re-engineering and process automation.
• Collaborating with other process owners to ensure that processes are integrated and aligned across the organization.
• Communicating process changes to stakeholders, including senior management, process users, and customers.
• Providing training and support to process users to ensure that they understand and follow the process.

Job Description for Process Manager:

Process managers are responsible for the day-to-day management of a particular business process within an organization. They ensure that the process is executed efficiently and effectively, and that process users comply with the process requirements. Process managers work closely with process owners and cross-functional teams to identify areas for improvement and implement changes that increase efficiency, reduce costs, and enhance quality. Other key responsibilities of a process manager include:

• Ensuring that the process is executed in compliance with regulatory requirements and industry standards.
• Monitoring process performance using KPIs and other metrics, and identifying areas for improvement. (Note, both roles include this bullet point as it is an ongoing common point of review and discussion.)
• Providing training and support to process users to ensure that they understand and follow the process.
• Identifying and addressing process issues and bottlenecks that impact process performance.
• Collaborating with other process managers and process owners to ensure that processes are integrated and aligned across the organization.
• Communicating process changes to stakeholders, including senior management, process users, and customers.
• Developing and maintaining process documentation, including SOPs, process flowcharts, and process metrics.

Overall, while both roles are involved in managing and improving business processes, the process owner has a more strategic and high-level focus, while the process manager has a more operational and hands-on focus. The process owner is responsible for setting the direction of the process, while the process manager is responsible for executing the process according to the owner's direction. The process owner is more involved in initiating and leading process improvement initiatives, while the process manager is more involved in implementing and monitoring process changes on a day-to-day basis.

The Hidden Factory is everything your group does over again because it didn't go right the first time around.

This ranges from re-doing a failed multi-year project, to re-pushing a production release which had some minor issues the first time around. Sometimes these activities are called "Fire Fighting."

Most groups I talk to tell me that about 35% of their teams efforts are lost to this problem.

Someone must pay for this, and it's very expensive.  Higher prices, lower wages, and lower shareholder dividends are one way to quantify the hidden factory.  In addition, the opportunity cost of not being able to reach your project monetization goals 33% faster means you left money and customers on the table.

The Stable Framework™ is a performance management framework for IT designed to give IT departments the tools needed to tame this wild Hidden Factory beast and bring the fire-fighting down to nearly zero, where it should be.

Read more about it here

Mike Berry

Managing project risks and issues is an important aspect of project management. Here are some best practices to help you manage project risks and issues effectively:

1. Identify and assess risks: Identify potential risks that could impact the project and assess their likelihood and potential impact. This can help you prioritize and focus on the risks that are most important. List these risks in a document called a Risk Register, so that you can keep track of them.  Updated it regularly.

2. Develop a risk management plan: Develop a plan for managing identified risks, including how they will be monitored, mitigated, and communicated to the project team and stakeholders.

3. Proactively manage risks: Proactively manage risks by taking steps to mitigate them before they become bigger problems. This could involve developing contingency plans, adjusting project schedules, or reallocating resources.

4. Monitor and control risks: Regularly monitor and control risks throughout the project by tracking their status and taking corrective action as needed. This can help you minimize the impact of risks on the project.

5. Establish a process for managing issues: Establish a process for managing issues that arise during the project, including how they will be reported, evaluated, and resolved. This can help you quickly identify and address issues before they become larger problems.

6. Document and track issues as they occur: Document all issues that arise during the project, including the impact on the project, the action taken to address the issue, and the resolution status. This can help ensure that issues are properly tracked and managed.

7. Communicate effectively: Communicate risks and issues to the project team and stakeholders in a timely and transparent manner. This can help ensure that everyone is aware of the risks and issues and can work together to address them.

By following these best practices, you can help ensure that project risks and issues are managed effectively and that the project is delivered successfully.

There are many project management tools and software available to help you plan, manage, and execute projects effectively. Here are some of the key project management tools and software:

1. Project management software: Project management software provides a centralized platform for managing project tasks, timelines, budgets, resources, and communications. Some popular project management software includes Asana, Trello, Basecamp, Jira, and Microsoft Project.

2. Gantt chart software: Gantt chart software allows you to create visual timelines that show the progress of tasks and the overall project. This can help you track dependencies, identify critical path tasks, and manage timelines effectively. Some popular Gantt chart software includes TeamGantt, GanttPRO, and Wrike.

3. Collaboration software: Collaboration software provides a platform for team members to communicate and collaborate on project tasks, documents, and files. Some popular collaboration software includes Microsoft Teams, Slack, Discord, and Google Workspace.

4. Time tracking software: Time tracking software allows you to track how much time team members spend on project tasks, which can help with resource planning, billing, and project management. Some popular time tracking software includes Harvest, Toggl, and RescueTime.

5. Risk management software: Risk management software allows you to identify, assess, and manage project risks. This can help you proactively mitigate risks and minimize their impact on the project. Some popular risk management software includes Riskalyze, RiskyProject, and any tool that will provide a Risk Matrix.

6. Agile software: Agile software provides a platform for managing agile projects and workflows, including Scrum, Kanban, and Lean methodologies. Some popular agile software includes Atlassian's Jira Software, and Targetprocess.

These are just a few examples of the project management tools and software available to help you manage projects effectively. The best tools and software for your project will depend on your specific needs, budget, and team structure.

Managing project scope and change is a critical aspect of project management. Here are some best practices to help you manage project scope and change effectively:

1. Define the project scope: Clearly define the project scope, including what is included and what is excluded. This will help you and your team understand what needs to be delivered and what is out of scope.

2. Develop a change management plan: Develop a plan for managing changes to the project scope. This plan should outline how changes will be requested, evaluated, and approved, as well as how they will be communicated to the team and other stakeholders.

3. Establish a change control board: Establish a change control board or similar group of stakeholders who will review and approve or reject change requests. This helps ensure that changes are evaluated objectively and with the project's overall goals in mind.

4. Document changes: Document all changes to the project scope, including the reason for the change, the impact on the project, and the approval status. This helps keep everyone informed and ensures that changes are properly tracked.

5. Monitor and control the project scope: Regularly review the project's progress against the project scope and make adjustments as needed. This can help ensure that the project stays on track and within the defined scope.

6. Manage stakeholder expectations: Manage stakeholder expectations throughout the project by communicating clearly and regularly about the project's goals, scope, and any changes that may occur. This can help minimize surprises and ensure that stakeholders remain engaged and supportive throughout the project.

7. Identify and manage risks: Identify and manage risks that could impact the project scope or lead to changes. This can help you proactively address potential issues before they become bigger problems.

By following these best practices, you can help ensure that project scope and changes are managed effectively and that the project is delivered successfully.

There are several project management methodologies and practices to choose from, and the best approach depends on the specific needs and goals of the project. Here are some of the most popular project management methodologies and practices:

1. Agile: Agile is a flexible, iterative approach to project management that emphasizes collaboration, adaptability, and delivering value to the customer. Agile methodologies include Scrum, Kanban, and Lean.
   
   
2. Waterfall: Waterfall is a linear, sequential approach to project management that involves completing each phase of the project before moving on to the next. It's a more traditional approach and is useful for projects where the requirements are well-defined and unlikely to change.
   
   
3. Stable: The Stable Framework™ is an Operational Excellence model for project management and operations that can be combined with Agile, or can be performed stand-alone.
   
   
4. RINCE2: PRINCE2 is a project management methodology that provides a structured approach to managing projects, including defined roles and responsibilities, a focus on the business case, and a step-by-step approach to project delivery.
   
   
5. PMI's PMBOK: The Project Management Body of Knowledge (PMBOK) is a framework developed by the Project Management Institute (PMI) that provides guidelines for managing projects across a range of industries and project types.
   
   
6. OPPM: The One Page Project Manager is a spreadsheet-based approach to Project Management.
   
   
7. VI Sigma: Six Sigma is a data-driven methodology that focuses on improving processes and reducing defects in products and services. It's often used in manufacturing and other industries where quality control is critical.
   
   

In addition to these methodologies, there are several project management practices that can help ensure project success, including:

• Defining clear project objectives and deliverables
• Establishing effective communication channels and regular project status updates
• Assigning roles and responsibilities to team members
• Developing a comprehensive project plan and schedule
• Identifying and managing risks throughout the project
• Monitoring and controlling the project's progress against the plan

Ultimately, the best project management methodology and practices will depend on the specific needs and goals of your project. It's important to assess the unique requirements of the project and choose the approach that's best suited to meet those needs.

1. Creating a project plan involves several steps, including defining the project scope, identifying the project objectives, identifying the project stakeholders, determining the project deliverables, developing a project schedule, allocating resources, and creating a project budget. Here's a general overview of how to create a project plan:
2. Define the project scope: Clearly define the boundaries of the project, including what is included and what is excluded.
3. Identify the project objectives: Determine what the project aims to accomplish and how it will be measured.
4. Identify the project stakeholders: In addition to the sponsor who commissioned you, who else needs to be involved in the project?
5. Determine the project deliverables: Create a list of all the products, services, or results that the project will deliver to meet the objectives.
6. Develop a project schedule: Create a timeline that outlines the tasks, milestones, and deadlines that are required to complete the project. Use a Gantt chart or a similar tool to visualize the schedule.
7. Allocate resources: Determine the resources needed to complete each task, including staff, equipment, and materials.
8. Create a project budget: Estimate the cost of each resource, and use this information to create a project budget.
9. Identify risks and mitigation strategies: Identify potential risks to the project and develop strategies to mitigate or manage them.
10. Develop a communication plan: Identify who needs to be informed about the project, how often, and what information they need.
11. Monitor and control the project: Regularly review the project's progress against the plan, and make adjustments as needed to keep it on track.

It's a common practice to include a project Charter--a single page cover sheet describing the project's' essential information.  The helps others quickly understand the purpose of the project.

Creating a project plan can be a complex process, but it's an essential step in ensuring the project's success. Consider using project management software to help you plan and manage the project. Popular project planning software includes Microsoft Project, Jira, Smartsheet, Asana, and One-Page.

Here are some interview questions that can be useful when hiring a project manager:

1. Can you describe your experience managing projects? What was the size and complexity of the projects you managed? How did you manage the project scope, schedule, and budget?

2. How do you communicate project progress and issues to stakeholders? What strategies do you use to ensure that stakeholders are kept informed and engaged throughout the project?

3. Can you walk me through your project management process? How do you plan a project, identify risks and issues, and manage changes?

4. Can you give an example of a time when you had to deal with a difficult stakeholder or team member? How did you handle the situation?

5. How do you manage team members who are not performing as expected? What strategies do you use to motivate and engage team members?

6. How do you prioritize tasks and manage multiple projects at once? What strategies do you use to ensure that each project receives the attention it needs?

7. Can you describe your experience with agile or other project management methodologies? How do you adapt your approach to the needs of each project?

8. How do you measure project success? What metrics do you use to track progress and determine whether a project has met its goals?

9. Can you give an example of a time when a project did not go as planned? How did you manage the situation and what did you learn from it?

10. Can you describe your experience managing remote or distributed teams? What strategies do you use to ensure effective communication and collaboration?

These interview questions can help you assess a candidate's experience, skills, and approach to project management, as well as their ability to adapt to different situations and work effectively with stakeholders and team members.

The term "Gherkin" is associated with Agile user stories because it is the name of a specific format for writing user stories that was introduced by the Cucumber testing framework. Cucumber is a popular open-source tool for Behavior-Driven Development (BDD), which is a software development methodology that emphasizes collaboration between developers, testers, and business stakeholders. The actual name is credited to Dan North, the creator of BDD, in a May 2006 blog post.

The Gherkin syntax is a way of writing user stories in a structured format that can be easily understood and shared by all team members, including non-technical stakeholders. The Gherkin syntax uses a simple language that is designed to be readable by both technical and non-technical people. It consists of a set of keywords, such as "Given", "When", and "Then", that describe the steps of a user story.

The Gherkin syntax is named after the small pickled cucumber, which is a reference to the idea of "pickling" or preserving the requirements of a user story in a structured, easy-to-understand format. The name was chosen to reflect the simplicity and ease of use of the syntax.

The Gherkin syntax has become popular in the Agile development community because it provides a standardized format for writing user stories that can be easily understood and shared by all team members. It can also be used to automate acceptance testing, as the steps of a user story can be mapped to test cases that verify that the software meets the requirements specified in the user story.