IMPACT PROJECT MANAGEMENT FRAMEWORK
- Discovery
- Initiation
- Planning
- Delivery
- Closure
- Value
- Recovery
- Overview
- Business Case
- Project Level Assessment
Project Discovery
Prior to the Initiation phase, there is an evaluative phase called discovery, where the “idea” is explored to determine whether it is a viable project vs an operation vs a “just do it” activity. This phase also determines whether the idea moves forward for further evaluation in the project lifecycle process. The completion of this phase ends with the determination of project feasibility, assessment of project level, and development of the business case for approval.
Discovery begins after ideas are prioritized. A Business Case is developed that conveys a clear description of the business challenge(s) that needs to be solved, the benefits of the project aligned with organizational strategy, and the information needed to prioritize work against initiatives within the portfolio. Feasibility and Project Level Assessments are completed. Once the work in this phase is complete, deliverables are submitted to the portfolio management process for review, acceptance, and prioritization.
Value of Discovery
The Discovery phase is important because this part of the project life-cycle is where problem/idea identification and solution definition take place. The governance board evaluates the idea and makes a decision to carry it forward for further consideration as a portfolio project. Additionally, the business need is defined, the need for resources justified, and the prioritization process completed. Further results include clearly describing the business challenge(s) to be solved, aligning the benefits of the project with the organization’s strategic goals/objectives, assessing the idea’s feasibility, the management effort needed, and the information needed to prioritize this work against other initiatives within the portfolio has been collected.
Step 1: Business Case
Project Charter Template
The Project Charter Template is a structured tool to outline essential project elements for successful initiation. It covers the project’s purpose, key stakeholders, specific objectives, and required resources, providing clear guidance on the "why" and "what" of the project. Each section helps define scope, assumptions, constraints, critical success factors, and expected benefits. Additionally, it includes a risk overview, budget estimation, and deliverables to ensure alignment with strategic goals and set clear milestones for success.
Business Case Template
The Business Case Template provides a structured approach to evaluate and justify a project by detailing the business problem or opportunity it addresses. It guides users through defining the project’s purpose, describing expected changes, setting measurable goals, and identifying benefits that align with strategic objectives. Key components include outlining the project’s scope, critical success factors, and major deliverables with acceptance criteria, ensuring clarity on what is included and excluded from the project. This template serves as the project’s foundation, establishing a solid rationale, objectives, and success measures for informed decision-making and project alignment.
Business Case Alternative Analysis
The Business Case Alternatives Analysis Worksheet is a tool for comparing different solutions to a proposed project, helping teams evaluate the costs and benefits of each option. For each alternative, users can document a brief description, proposed actions, and any anticipated cost and benefit impacts. By assessing up to three alternatives, this worksheet supports informed decision-making by clarifying the advantages and trade-offs of various approaches, guiding the selection of the most effective solution for achieving project goals.
Operations - Project Checklist
The Operations - Project Checklist helps clarify whether an initiative should be classified and managed as a Project or an Operation. By reviewing criteria such as purpose, duration, output, and budget, this template guides users to assess if the initiative is a temporary, unique effort (a project) or an ongoing, repetitive activity (an operation). Once completed, this checklist enables teams to determine the most appropriate approach for implementation, aligning the initiative’s management with its intended goals and organizational needs.
Implementation
The Business Case explains the project purpose and goals – the reasons for undertaking the project. It will become the foundation for the project because it describes the project, defines the project (both by inclusion and by exclusion), explains the reasons for creating the project, and defines the key benefits produced by the project. The Business Case is the left side of the Project Charter template. A standalone version of the Business case template is also available. For larger, more complex projects, it may be warranted to further analyze alternatives to the proposed action – use the Business Case Alternatives Analysis Worksheet when necessary.
Step 2: Project Level Assessment
Project Level Assessment Template
Implementation
Sizing a project determines the relative size of a project effort. The size of the project determines the extent to which project management practices are formally applied to the project. All projects need a minimum of project management to ensure project success. However, project management process should not overtake the project.
Detailed Guidance
When applying the project management practices, you must consider differences in project size. Leverage a scalable methodology that considers size on multiple levels so you can develop the right level of project management process based on the impact of the project. The first consideration in determining the level of project management rigor required is the triple constraint factors of time, scope and cost, as well as the measures of resources required, and strategic impact the project is expected to have when completed. The second factor is the experience level of the project manager. If the project manager is very experienced, you might allow him to manage larger projects with less rigor, or at least up to a higher effort threshold. On the other hand, you may ask an inexperienced project manager to manage a 1000 hour project as if it was a large one, since they may need more structure. The third factor is the complexity and business criticality of the project. For example, you may want to manage a 1000 hour project as if it were large, if the project is extremely critical to the business. Or, you may want to manage a 500 hour project as a small one because you have managed two similar projects before and therefore it seems to be low risk.

Project Levels

Project Scale – Small, Medium, Large
Too Much? Excessive process can result in too much time spent on reviews and approvals, which creates delays in the project schedule and causes milestones to be missed.
None? The final deliverable may not satisfy business requirements. Quality may suffer. Timeline and expenses may grow uncontrollably.
Just Right! Appropriate templates and tools are used when and how they best serve to enable the project to move forward while decreasing negative risks and ensuring project outcome quality.
A project management methodology is not intended to be one-size-fits-all. Enforcing each prescribed activity because it’s on the list is not always the most appropriate for less complex projects.
To avoid over- or under-engineering the process, properly assess risk and complexity during project initiation and then set your control levels accordingly.
Leverage a scalable methodology that considers size on multiple levels so you can develop the right level of project management process based on the impact of the project. The first consideration in determining the level of project management rigor required is the triple constraint factors of time, scope and cost, as well as the measures of resources required, and strategic impact the project is expected to have when completed. The second factor is the experience level of the project manager. If the project manager is very experienced, you might allow him to manage larger projects with less rigor, or at least up to a higher effort threshold. On the other hand, you may ask an inexperienced project manager to manage a 1000 hour project as if it was a large one, since they may need more structure. The third factor is the complexity and business criticality of the project. For example, you may want to manage a 1000 hour project as if it were large, if the project is extremely critical to the business. Or, you may want to manage a 500-hour project as a small one because you have managed two similar projects before and therefore it seems to be low risk.

Project Level Assessment Template
- Overview
- Project Charter
- Stakeholder Management
- Project Kick Off
Project Initiation
Project Initiation
Initiation is the first phase in the Project Life-cycle and begins when the project is approved and scheduled to begin. You initiate a project by further defining the project purpose and scope, the justification for initiating it, and the solution to be implemented.
Once the project is defined, outcomes expected determined, and project resources identified, you can present the project to your sponsor to obtain feedback and approval to proceed to Project Planning.
During the Initiation phase, the project is fully described in the Project Charter, linked to the organization's strategy, resource requirements are defined, and expected results and value are determined.
Goals:
- Identify key stakeholder expectations and interests
- Approve project charter
- Identify and commit key resources needed for setting up the project
- Approve project charter, funding, and delivery
- Define stakeholder roles and responsibilities
- Develop kick-off meeting agenda
Value of Initiation
The initiation phase is important because it identifies the “Why” and “What” of a project or, in other words, the scope and planned business value of the initiative. Sponsors will use this information to determine if the project should receive funding. In this phase, full description and linking of the project to organizational strategy, and definition of resource requirements occurs. Additionally, expected results and benefits are determined. Securing of sponsor support and approval has taken place, as well as approval of funding to proceed with delivery. Identification of key stakeholder expectations and interests, approval of the project charter, and identification and commitment of the key resources needed for setting up the project are to be completed during this phase.
Step 1: Project Charter
Project Charter Template
The Project Charter Template is a structured tool to outline the foundational details necessary for project initiation and alignment. It guides teams through defining the project’s purpose, identifying stakeholders, setting clear objectives, and specifying required resources. Each section prompts considerations around goals, assumptions, constraints, and potential risks, offering a complete view of why the project is needed and what it aims to achieve. Additionally, it includes areas for key deliverables, scope boundaries, budget estimates, and a timeline, helping ensure clear expectations and strategic alignment from the start.
PMI Guidance: Develop Project Charter
Develop Project Charter is the process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Outputs
Implementing the Guidance
The charter provides a delineation of roles and responsibilities, outlines the project objectives, identifies the main stakeholders, and defines the authority of the project manager. It serves as a reference of authority for the future of the project. The charter gives the project manager the authority to initiate the project. Use the Project Charter template.
Completed during the prior Discovery phase, the left side of the charter (the Business Case) defines the “why.” The right side defines the “what” in more detail. Completed during this initiation phase, it includes a definition of the following information:
- Main stakeholders
- Project organization/resource requirements (governance and roles/responsibilities)
- Assumptions
- Constraints
- Potential risks (high-level risk assessment)
- Risk to the business of executing the project
- Risk to the business of not undertaking the project
- Expected budget and spending authority
- Proposed timeline
Step 2: Stakeholder Management
Stakeholder Roles and Responsibilities Template
The Stakeholders Roles and Responsibilities Template outlines the roles and duties of key participants in a project, including Project Governance, Sponsor, Project Manager, Project Team, Stakeholders, and Subject Matter Experts. Each role is defined with specific responsibilities, such as strategic direction, project management, business value delivery, and expertise. This template helps ensure that everyone understands their responsibilities and contributions, promoting accountability and alignment with project objectives. By establishing clear expectations, it supports effective collaboration and smooth project execution.
Stakeholder Engagement Plan Template
The Stakeholder Engagement Plan Template helps project managers capture key information about stakeholders, including their role, interests, influence, and needs. It provides fields to document the stakeholder’s understanding, motivation, knowledge, skills, and organizational power. Additionally, it includes sections for influence strategies and engagement plans. This template enables project managers to develop customized approaches to build stakeholder support, align with project objectives, and meet expectations effectively.
PMI Guidance: Identify Stakeholders
Identify Stakeholders is the process of identifying the people, groups, or organizations that could impact or be impacted by a decision, activity, or outcome of the project, analyzing and documenting relevant information regarding their interests, involvement, interdependencies, influence, and potential impact on project success. The key benefit of this process is that it allows the project manager to identify the appropriate focus for each stakeholder or group of stakeholders.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Inputs
Implementing the Guidance
A stakeholder is any person, group, or organization affected by, or who perceives they might be affected by, the project. It is also who can affect the project. The Key Stakeholder is usually someone in a management role, or who has decision-making power, who will be able to influence the project and/or will be impacted by project outcomes. It is critical to project success to identify stakeholders, prioritize them according to influence and involvement, and assign roles and responsibilities.
Detailed Guidance
When assessing an individual or group, ask whether they can impact/be impacted by any decision, change, or activity executed as part of the project. This might include individuals outside of the organization.
- Is affected by the project
- Perceives that they might be affected by the project
- Can be affected by the project
- is in a management role,
- has decision-making power
- Will be able to influence the project
- Will be impacted by project outcomes.
- Examples: Sponsor, business executive, CIO
- Influence: To what degree can this stakeholder impact project progress and outcomes?
- Involve: How involved is the stakeholder in the project already?
- Support: Is the stakeholder a supporter of the project? Neutral? A resister? Label supporters with green sticky notes, resisters with red notes, and the rest with a third color.

Stakeholder Management
Based on the assessment, assign the stakeholder a green, red, or other color code, and assign them an appropriate place on the stakeholder “power map,” as shown in the figure below.

Stakeholder Analysis – Reading the Power Map
Review the Project and define the various roles and responsibilities, including any Project Governance entities, the project group (Sponsor, PM & team), and all stakeholders – per the definitions provided in the “Stakeholders Roles & Responsibilities” template. For Medium projects, also use the Stakeholder Engagement Plan template. Governance may vary per Project as to which entities (individuals or bodies such as the BoD) have key deliverable or milestone/gate approvals, or critical input to provide.
Use the “Stakeholders Roles & Responsibilities” template to define the range of stakeholders and their roles and to determine the project resources requirements necessary to meet the defined project needs. Use it to identify the specific people or entities to fill those roles and to determine whether internal resources or vendors will be working with you to implement the project.
Record information gathered during the stakeholder analysis is recorded in the Stakeholder Engagement Plan template. Update it regularly as changes occur (new stakeholder added or removed).
Factors in the plan include:
- What is your strategy to deal with resisters?
- What is your strategy to leverage supporters?
- How are you going to ensure that impacted stakeholders communicate the change to the rest of the organization in an effective way?
- Do you have change champions?
Make every effort to define stakeholder roles and responsibilities. Assign key responsibilities to stakeholders with the appropriate level of influence and involvement. An effective approach to stakeholder communication will often form part of a broader stakeholder engagement process.
Factors you should consider in developing the stakeholder engagement plan include:
- Why – what are our key objectives in communicating?
- Who – who are our stakeholders and influencers? Who do we need to persuade?
- What – what do we plan to do to achieve our objectives?
- Where – which platforms and channels are available to us?
Step 3: Project Kick-off Meeting
Kick-off Meeting Agenda Template
Implementation
The Kick-off Meeting is the first meeting with the project team and the client of the project. It is a critical part of project communication and stakeholder engagement and management. Use the “Kick-off Meeting Agenda” template.
This all-important meeting brings together all of the stakeholders directly engaged in the project processes to:
- Set expectations
- Understand the business and strategic objectives the project is expected to deliver and,
Develop and agree to the operating model for planning and executing the project work.
It introduces the members of the project team and the client and provides the opportunity to discuss the role of each team member.
Kick-off Agenda Topics include:
- Project Goals & Objectives (to set a common goal for the team)
- Plan, Deliverables, Structure and Responsibilities
- Critical Success Factors & Project Acceptance Criteria
- Issues and Risk Management
- Communication Strategy
- Change Management
The Kick off meeting also heralds the Planning phase of the project.
- Overview
- PM Plan
- Org Change
- Scope
- Schedule
- Cost
- Quality
- Stakeholders
- Resources
- Communication
- Risk
- Procurement
- Value
Project Planning
Upon approval of the scoped project, the project moves into the planning phase. The first steps in the planning phase are defining the project and appointing the project team. The planning phase involves collaborating with the project team to develop a set of planning documents to help guide the team throughout the project In this phase, further develop the project solution in as much detail as possible and plan the steps necessary to meet the project’s objective. This involves the team identifying all the work, and creating a detailed description and breakdown of the project work into discrete deliverables.
The purpose of the Planning phase is to establish the project structure and operating model, including the project team, work breakdown structure, detailed project execution plan, and deliverables.
Goals:
- Create and approve Project management plan and schedule
- Establish Project governance structure
- Define expected project parameters /constraints
- Conduct sprint planning event (if Agile)
Sprint Planning
Sprint planning is an event in scrum that kicks off a particular sprint. The purpose is to define what can be delivered and how that work will get done. It is usually a set period of time (e.g., a 30-day sprint) that address what will get done, how it will get done, who will do it, the inputs, and the outputs.
Value of Planning
Planning is of major importance to the project life-cycle, as it defines the Who, What, When, Where, and How of a project. During the planning phase, the project structure and operating model are established, the work breakdown structure is developed, a detailed project delivery plan created, and deliverables defined. Furthermore, the project management plan and schedule are approved, the project governance structure is established, the benefits realization plan defined, and expected project parameters/constraints are defined.
The Planning Process
The amount of planning performed should be commensurate with the scope of the project and the usefulness of the information developed. Some of the processes used when defining the project approach are:
- Plan the activities
- Determining resource needs and roles
- Identifying associated costs
In this phase, the project manager will manage the stakeholder’s expectations by monitoring and controlling the triple constraint (time, scope, and cost).
Create a project plan, or schedule, outlining the activities, tasks, dependencies, resources and associated costs, and time-frames. Assign each task of the project from beginning to end to one of the project team members. An output of the planning process is a project management plan that details the scope, schedule, resources, and associated cost.
The project management plan, or plans, are used to explain how aspects of the project will be managed. The level of detail and complexity of the plans is determined by company standards and the complexity of the project work. Please refer to the project sizing assessment to determine the level of project management rigor required for each project. Depending on project complexity, additional separate project planning documents to use include:
- Risk Management
- Quality Management
- Benefits Realization
- Change Management
- Communications plan
- Stakeholder Management
If required, the project manager coordinates the preparation of a project budget by providing cost estimates for labor, equipment, and materials. Financial reporting techniques monitor and control cost expenditures during project implementation, or the delivery phase.
Once the project team has identified the work, prepared the schedule, and estimated the costs, the team identifies and tries to deal with anything that might pose a threat to the successful completion of the project. This is “risk management.” In risk management, we identify “high-threat” potential problems along with the action to take on each high-threat potential problem, either to reduce the probability that the problem will occur or to reduce the impact on the project if it does occur. Additionally, the PM identifies all project stakeholders and establishes a communication plan describing the information needed and the delivery method used to keep the stakeholders informed.
Finally, the PM creates a quality plan providing quality targets, assurance, and control measures, along with an acceptance plan and the customer acceptance criteria. At this point, the project is detailed, planned, and ready to be executed.
Depending on your project implementation methodology, the processes in planning may be subject to multiple iterations before the planning phase is complete. For example, as the scope is further refined in the requirements process, you may realize you need further resource allocation, which could drive timeline changes based on resource availability.
Step 1: PM Plan
Project Charter
PMI Guidance: Develop Project Management Plan
Develop Project Management Plan is the process of defining, preparing, and coordinating all subsidiary plans and integrating them into a comprehensive project management plan. The key benefit of this process is a central document that defines the basis of all project work.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Outputs
Implementing the Guidance
The Project Management Plan is a standardized document, or collection of documents, that explains how to manage various aspects of the project. These topics may include: communications, quality, risk, stakeholder engagement & management, procurement and change management.
Step 2: Organizational Change
Change IMPACT Statement
The Change IMPACT Statement can be used to describe the defining characteristics of the proposed “change” considering the type, scope, characteristics, and potential IMPACT of the change.
Change Management Plan
The Change Management Plan can be used throughout the duration of the Change Management Simplified course and during any change effort to build your own change management plan for a project.
Implementation
Detailed Guidance
The Change Impact Statement describes the defining characteristics of the proposed change considering the type, scope, characteristics and potential impact of the change.
Using the Change Impact Statement template as the starting point to assess project change impacts and plan your change and communication strategy. Build upon the results of the Project Charter, Scope Statement, Benefits Realization Plan, and Stakeholder Engagement Plan:
- List all of the key changes that are expected to result from the project,
- Assess the implications of these impacts for specific groups (business areas, vendors, etc.) or individuals. Identifying and engaging these stakeholders is critical for the success of the project or change initiative.
- Estimate what needs to be modified to accomplish the change. High level items should be listed early in the process; when the project’s design is more stable, more detailed items can be added.
- Explain the reasoning behind change approval including a brief summary of the approval process, description of anticipated benefits and related consequences for a failure to act.
- Describe in detail the steps and procedures that will be followed in implementing the change.
Project Management: What work we will do to create the change. The techniques for creating change outcomes (i.e. PMBOK® )
Change (figure below) is about how the project is implemented successfully through and with people. It is about the techniques for leading people through the change.
The purpose of the Change Management Plan includes:
- Setting expectations among stakeholders
- Assessing the impact of the change the project is creating
- Developing thoughtful change messages
- Engaging stakeholders in the change process
- Preparing stakeholders to accept the change
- Ensuring stakeholders have what they need to adopt the change
- Ensuring that stakeholders adopt the change
Ineffective change management often equals project failure because change resistance often comes from a lack of understanding of value, misunderstanding of approach, stakeholders not being included in the process, and lack of transparency/information sharing.

Change Management
Appropriate change messaging can go a long way in explaining the outcomes of the change the project will create and help stakeholders understand the value. Articulate the value proposition as identified in the business case and charter:
- Why, Who, what, when, where, why, and how
- What will be changing?
- Who will be impacted?
- When will the change happen?
- Where will the change take place?
- Why are we making this change?
- How will the change be implemented?
AND…Business outcomes you expect to achieve that will have a positive impact!
Include the change messaging in the Communications Plan:
- Understand your stakeholders:
- Who is impacted, or believes themselves to be, impacted by this change?
- What is their position on this change?
- What are their incentives (WIIFM) for engaging in the change process?
- Are there resistors to this change and what is motivating them to resist the change?
- Then develop strategies for each stakeholder:
- What training or development will they need to properly accept the change?
- How will you communicate the impact of the change to them?
- How will you engage them in the change process?
- Change management is not for one person on the team!
- Make it clear upfront that the entire team and all stakeholders are change champions
- Leverage project supporters to spread the key message to their affected users
- Identify negatively impacted stakeholders and users who are potential resistors and take the time to create a meaningful mitigation strategy to foster support for the Change Engagement Plan
Step 3: Scope
Work Breakdown Structure & Schedule Planning Worksheet
PMI Guidance: Plan Scope Managment
Plan Scope Management is the process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled. The key benefit of this process is that it provides guidance and direction on how scope will be managed throughout the project.
Inputs
- Project charter
- Project management plan
- Quality management plan
- Project life cycle description
- Development approach
- Enterprise environmental factors
- Organizational process assets updates
- Tools / Techniques
PMI Guidance: Collect Requirements
Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives. The key benefit of this process is that it provides the basis for defining and managing the project scope including product scope.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Define Scope
Define Scope is the process of developing a detailed description of the project and product. The key benefit of this process is that it describes the product, service, or result boundaries by defining which of the requirements collected will be included in and excluded from the project scope.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Create WBS
Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. The key benefit of this process is that it provides a structured vision of what has to be delivered.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Tools / Techniques
Implementing the Guidance
Detailed Guidance
Use the WBS-Schedule Planning Worksheet template. Determine the format you will use for the WBS (and stick with it). Define the deliverables for each major component of the project; break that down further into other, lower-level deliverables. The work packages are the lowest level of the WBS. They are the groupings of activities that must be executed to complete the project deliverables. This is the level to which the project manager manages/oversees the work. Don’t worry if you don’t know all of the details upfront. You will use a method called progressive elaboration to uncover the details as you go. It may be difficult to decompose the project only by project phase because most of the deliverables fall under the planning and delivery phases; and many deliverables are completed during more than one phase (e.g. scoping is done during project initiation and planning).
It may be difficult to decompose the project only by project phase because most of the deliverables fall under the planning and delivery phases; and many deliverables are completed during more than one phase (e.g. scoping is done during project initiation and planning).

Phase-based WBS

Deliverable-based WBS
If the project is decomposed only by to major deliverables, the scheduled activities that result will not be organized in the order that they should be completed, making it harder to build a schedule using the WBS.
Consider a combination of both approaches. If the project is decomposed according to major deliverables, the scheduled activities that result will not be organized in the order that they should be completed, making it harder to build a schedule using the WBS. Use the project phases for the highest level of the WBS. Each phase has independent deliverables that must be completed before the next phase can commence, avoiding an overlap of deliverables between phases. The schedule activities that result will be organized closer to chronological order, allowing you to estimate corresponding time and resources, and add activities to the schedule in a seamless fashion.
Step 4: Project Schedule
Work Breakdown Structure & Schedule Planning Worksheet
The Work Breakdown Structure & Schedule Planning Worksheet helps teams organize tasks and schedule project phases. It includes columns for task IDs, subtasks, resources, effort hours, deliverables, dependencies, duration, and start/end dates. This template provides a clear overview for project managers and sponsors to track progress, manage resources, and ensure timely delivery.
Change Definition Worksheet
PMI Guidance: Plan Schedule Management
Develop Project Charter is the process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
- Tools / Techniques
- Outputs
PMI Guidance: Define Activities
Develop Project Charter is the process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Tools / Techniques
PMI Guidance: Sequence Activities
Develop Project Charter is the process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Estimate Activity Durations
Develop Project Charter is the process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Develop Schedule
Develop Project Charter is the process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Outputs
Implementing the Guidance
The schedule is developed as a result of organizing the work according to dependencies and combining the work that must be done with the resources necessary to complete the work, as defined in the WBS and staffing plan above.
Detailed Guidance
The project schedule is a tool that communicates what work needs to be performed, which resources of the organization will perform the work, and the time-frames in which that work needs to be performed. The project schedule should reflect all of the work associated with delivering the project on time. It builds on the WBS started using the WBS-Schedule Planning Worksheet and a tool such as MS Project.

Create the Schedule
Without a full and complete schedule, the project manager will be unable to communicate the complete effort, in terms of cost and resources necessary to deliver the project. Complete the schedule on the right side of the WBS-Schedule Worksheet template. Invest effort in estimating the time and resources required to complete activities, and placing these activities in the correct sequence. Decomposing and sequencing work will make it easier to accurately estimate cost of deliverables for the budget, because you will have estimated exact time and resources required for each individual activity. Now you can determine project length according to the dependencies and work effort
Develop the schedule by adding the following to your sequence of activities:
• Estimating the effort required to complete each activity.
• Base duration of activity on the availability of necessary skilled resources.
• Consider constraints and assumptions from the scope statement, such as contract obligations, including contingency time in the estimates.

Develop the Schedule


Sequencing Activities

Activity Diagram

Adding Duration

Critical Path
Step 5: Cost
Work Breakdown Structure & Schedule Planning Worksheet
The Work Breakdown Structure & Schedule Planning Worksheet helps teams organize tasks and schedule project phases. It includes columns for task IDs, subtasks, resources, effort hours, deliverables, dependencies, duration, and start/end dates. This template provides a clear overview for project managers and sponsors to track progress, manage resources, and ensure timely delivery.
Budget Planning Worksheet
The Budget Planning Worksheet is used to develop an estimate, as needed, primarily for external or vendor expenses.
Benefits Register Template
The Benefit Register is used to define project value, set the baseline measurements for each benefit metric, measure and track benefits, report outcomes, determine gaps and monitor and report/mitigate/remediate gaps between goals and actual results.
PMI Guidance: Plan Cost Management
Plan Cost Management is the process that establishes the policies, procedures, and documentation for planning, managing, expending, and controlling project costs. The key benefit of this process is that it provides guidance and direction on how the project costs will be managed throughout the project.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Tools / Techniques
- Outputs
PMI Guidance: Estimate Costs
Estimate Costs is the process of developing an approximation of the monetary resources needed to complete project activities. The key benefit of this process is that it determines the amount of cost required to complete project work.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Determine Budget
Determine Budget is the process of aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline. The key benefit of this process is that it determines the cost baseline against which project performance can be monitored and controlled.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Inputs
Implementing the Guidance
Using the WBS-Schedule Planning Worksheet template to develop activity estimates, add together all activity estimates to get to a total project cost. The Budget Planning Worksheet (EXCEL) is used to develop estimates, as needed, for external or vendor expenses.
Detailed Guidance

Create a Budget

Creating a Cost Estimate
The are a variety of methods to develop project estimates, as summarized below.

Project Cost Estimating
"Bottom-up” estimating will be the most accurate method of project cost estimating, but still based on estimates for each activity. Below you will find a slide with more detail on each method of estimating for your information:

Analogous Estimating


Three-point Estimating

Program Evaluation & Review Technique (PERT)

Bottom Up Estimating
Step 6: Quality
Quality Management Plan
PMI Guidance: Plan Quality Management
Plan Quality Management is the process of identifying quality requirements and/or standards for the project and its deliverables, and documenting how the project will demonstrate compliance with relevant quality requirements and/or standards. The key benefit of this process is that it provides guidance and direction on how quality will be managed and validated throughout the project.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Tools / Techniques
Implementation
Quality management ensures that the project produces deliverables that achieve the expected outcomes.
Detailed Guidance
The quality management plan defines the acceptable level of quality, which is defined by the customer, and describes how the project will ensure this level of quality in its deliverables and work processes. Quality management activities ensure that:
- Products are built to meet agreed upon standards and requirements
- Work processes are performed efficiently and as documented
- Non-conformances found are identified and appropriate corrective action is taken
Quality Management plans apply to project deliverables and project work processes. Use the Quality Management plan template to develop your project quality plan. Quality control activities monitor and verify that project deliverables meet defined quality standards. Quality assurance activities monitor and verify that the processes used to manage and create the deliverables are followed and are effective.
Quality management ensures that the project produces deliverables that achieve the expected outcomes.
The purpose of the quality management plan is to:
- Identify quality policies that must be followed and standards that must be met
- Develop plans on how quality will be measured throughout the project
- Execute and control quality during project work
- Gain stakeholder acceptance of the quality of all deliverables
The quality management process should include:
- Who is responsible for measuring quality
- The approach to ensuring and measuring quality
- The metrics to validate quality
The first step is to ensure that quality goals trace back to requirements.
- Ensure quality: Tie project deliverables to the use cases / business requirements that defined the characteristics of the deliverables.
- Completed projects that do not meet requirements are no better than projects that fail.
- The management plan indicates how you will measure quality.

Quality Metrics Identification

Sample Quality Metrics
Step 7: Stakeholders
Stakeholder Roles & Responsibilities
Stakeholder Roles & Responsibilities worksheet allows you to review the project and define the various roles and responsibilities, including any project governance entities, the project group, and all stakeholders.
Change Stakeholder Engagement Plan
The Change Stakeholder Engagement Plan Template is used to identify your critical stakeholders and define your approach or strategy to either win them around, move them to the preferred level of engagement, or manage their opposition.
PMI Guidance: Plan Stakeholder Management
Plan Stakeholder Engagement is the process of developing appropriate management strategies to effectively engage stakeholders throughout the project life cycle, based on the analysis of their needs, interests, and potential impact on project success. The key benefit of this process is that it provides a clear, actionable plan to interact with project stakeholders to support the project's interests.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Inputs
- Outputs
Implementing the Guidance
During the planning process, the project manager or scrum master should identify their stakeholders. These stakeholders may help the project team achieve success by providing their own unique experiences and perspectives. Their participation is critical to the success of a project.
Detailed Guidance
During the Planning phase, a project master or scrum master should meet each of the stakeholders, understand their WIIFM (What's in it For Me), and identify the best way to communicate with them and keep them engaged. If you're having trouble identifying your stakeholders, get input from your project sponsor. If it's a system that's being implemented, ask yourself (and the team) who are the end users? Who might support the system? Who must pay for the system? Who will want reports out of the system, or will want to be notified if changes are made? It's also helpful to conduct a brainstorming session with your sponsor, project team, and other identified stakeholders, to see who might be missing.
Step 8: Resources
Staffing Plan
The Staffing Plan is used to facilitate the acquisition of the best team and resources for the project, considering both the resources needed and the resources available, and if all ideal resources are not available internally, how these will gaps be filled.
RACI Matrix
The RACI Matrix is a powerful tool to assist in the identification of roles and assigning of cross-functional responsibilities to a project deliverable or activity.
PMI Guidance: Plan Resource Management
Plan Resource Management is the process of how to estimate, acquire, manage and use team and physical resources. The key benefit of this process is that it establishes the approach and level of management effort needed for managing project resources based on the type and complexity of the project.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Estimate Activity Resources
Estimate Activity Resources is the process of estimating the type and quantities of material, human resources, equipment, or supplies required to perform each activity. The key benefit of this process is that it identifies the type, quantity, and characteristics of resources required to complete the activity which allows more accurate cost and duration estimates.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
The purpose of the staffing plan is to make certain the project has sufficient staff with the right skills and experience to ensure successful project completion.
Detailed Guidance
Staffing is the process of assigning specific individuals, or RESOURCES, to project roles and responsibilities. Use the Staffing Plan template.
Use the RACI Chart template to determine roles and responsibilities in terms of Responsible, Accountable, Consulted, and Informed.
This process includes:
- Documenting time periods each member can work on the project
- Reflecting scheduling conflicts, vacation time, and commitments to other projects
- Enabling the building out of the final human resource budgets

Staffing Plan
The figure below breaks down the elements of the staffing plan into the level of detail necessary for adequate planning. Use the Resources Tab and the resource column on MS Project to assign staff to work packages. It is likely that ideal resources will not be available for every role, so be prepared to be flexible!

Elements of the Staffing Plan
Gather the staffing information and assign resources to the project. Then, final project estimates can be determined based on the resource availability and schedule adjustments.

Step 9: Communication
Communication Plan
The Communication Plan Template is a one-page plan to define the communication strategy message content, delivery mechanism, sender, and time-frame (the “when”) throughout the phases of the change initiative.
RACI Matrix
The RACI Matrix is a powerful tool to assist in the identification of roles and assigning of cross-functional responsibilities to a project deliverable or activity.
PMI Guidance: Plan Communication Management
Plan Communications Management is the process of developing an appropriate approach and plan for project communications based on stakeholders’ information needs and requirements, and available organizational assets. The key benefit of this process is that it identifies and documents the approach to communicate most effectively and efficiently with stakeholders.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Tools / Techniques
Implementing the Guidance
The Communications Plan template explains what types of communications will occur during the project life cycle, the mechanisms for doing those communications, and the recipients of the communication deliverables. Process for a project is of the utmost importance. This plan explains what communications will happen during the life-cycle of the project, to what stakeholders, and in what forms. Use the RACI Chart template to determine roles and responsibilities in terms of Responsible, Accountable, Consulted, and Informed.
Detailed Guidance
Communication and Meeting Best Practices:
- Regardless of project complexity, it is important not to overwhelm stakeholders with information that is not relevant to them.
- Think about what information that stakeholder requires to feel comfortable with the state of the project and its progress.
- Do not invite stakeholders to meetings unless their attendance is absolutely necessary; for some stakeholders, an e-mail report will be sufficient to keep them informed.
- Stakeholders who are being consulted should be present, as their feedback can impact project decisions and outcomes.
- Set a firm agenda for the meeting and stay on message.
- For key stakeholders who are involved in several projects/initiatives, it is important to book meetings well in advance. If possible, hold status meetings at the same time and on the same day each week/month.
- Sending more detailed information than is necessary might mean that it does not get read.
- Distributing reports too widely may lead to people assuming that someone else is reading it, causing them to neglect reading it themselves.
- Only distribute reports to the stakeholders who need the information.

Stakeholders & Communications Plan

Communications Requirements
Step 10: Risk Management
Risk Register
The Risk Register template assists in identifying, assessing, and managing project risks. It categorizes risks, rates their probability and impact, and calculates a risk score to prioritize responses. The template guides the user in defining risk responses (avoid, transfer, mitigate, or accept), assigning responsibility, and tracking triggers. It also includes updates on risk status, helping the team stay proactive in managing risks for project success.
Issue Log Template
The Issue Log Template is for tracking and resolving project issues, recording details like description, urgency, impact, responsible party, action plan, and due date. Each entry includes status updates and comments for clarification. This log helps the team stay organized and responsive to project challenges.
Project Management Evaluation – Change Lessons Learned
The Project Management Evaluation – Change Lessons Learned is a lessons learned template to evaluate the project management process and the elements of the change process that occurred during the project.
PMI Guidance: Plan Risk Management
Plan Risk Management is the process of defining how to conduct risk management activities for a project. The key benefit of this process is it ensures that the degree, type, and visibility of risk management are commensurate with both the risks and the importance of the project to the organization. The risk management plan is vital to communicate with and obtain agreement and support from all stakeholders to ensure the risk management process is supported and performed effectively over the project life cycle.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Tools / Techniques
- Outputs
PMI Guidance: Identify Risks
Identify Risks is the process of determining which risks may affect the project and documenting their characteristics. The key benefit of this process is the documentation of existing risks and the knowledge and ability it provides to the project team to anticipate events.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Qualitative Risk Analysis
Perform Qualitative Risk Analysis is the process of prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact. The key benefit of this process is that it enables project managers to reduce the level of uncertainty and to focus on high-priority risks.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Quantitative Risk Analysis
Perform Quantitative Risk Analysis is the process of numerically analyzing the effect of identified risks on overall project objectives. The key benefit of this process is that it produces quantitative risk information to support decision-making in order to reduce project uncertainty.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Outputs
PMI Guidance: Plan Risk Responses
Plan Risk Responses is the process of developing options and actions to enhance opportunities and to reduce threats to project objectives. The key benefit of this process is that it addresses the risks by their priority, inserting resources and activities into the budget, schedule, and project management plan as needed.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Inputs
Implementing the Guidance
A risk is an uncertain condition or event that, if it occurs, could positively or negatively impact one or more project objectives. It is best to leverage a simple process for handling risks on the project.
The main differences between Risks and Issues are related to timing and probability. The language used to describe risks is future tense because it is about an event and impacts that have not happened yet but may happen. Plan and work out mitigation plans for high-impact risks. Risk mitigation plans are all about reducing the impact or probability of a risk event. When risk materializes as an issue and moved to the Issue log, it is noted as such on the Risk Register. As part of lessons learned, these specific risks are reviewed to better plan future projects. The Risk Register should be reviewed periodically—weekly or less frequently during status review meetings.
Detailed Guidance

Why Plan for Risks
A risk management plan identifies the processes for defining the risks that could positively or negatively impact the success of the project, how responses to those risks will be handled to reduce the potential of their occurrence, the process for monitoring the risks, and owner of responses. Use the Risk Register to manage risks and the Issue Log template to mange risks that are realized.

Risk Management Plan
The Risk Register acts as a central repository for all risks identified by the organization through the risk assessment process. For each risk identified, include information such as source, nature, treatment option, existing counter-measures, and recommended countermeasures. Use the Risk Register template to document project risks.

A “risk assessment” is just the systematic process for identifying and evaluating events (i.e., possible threats or opportunities) that could affect the achievement of objectives, positively or negatively. It provides a mechanism for identifying which risks represent potential pitfalls. Risk assessments give organizations a clear view of variables to which they may be exposed, whether internal or external.
- Starting with the Project Charter and using the Risk Register, develop a list of risks for your project.
- Identify the top three or more project risks and assess:
- The probability of each risk event occurring.
- The potential impact of each risk event.
- Prioritize risks from most to least critical, based on probability and impact.
- Have your Team brainstorm mitigation response plans, especially for potentially high risks to reduce the chance of their actual occurrence
- Assign a potential owner for each risk.
- Have the Team present its risk response plan and discuss the results.
- Does the cost of the risk response match the probability and impact of that risk?
- For example, there may be an identified security risk with a high potential impact, but a very low probability of occurrence.
- Does it cost more to address the breach after it happens, or to prevent it entirely?
While risk is the potential issue that may or may not happen and can impact the project positively or negatively, once a risk actually occurs, it is denoted as “Risk Realized” on the Risk Register, and a corresponding issue is immediately opened on the Issue Log and Action Plan development commences to resolve the issue. The realized risks should also be noted for further discussion on the Project Mgmt. Evaluation – Change Lessons Learned for analysis during Project Closure.
Step 11: Procurement
PMI Guidance: Plan Procurement Management
Plan Procurement Management is the process of documenting project procurement decisions, specifying the approach, and identifying potential sellers. The key benefit of this process is that it determines whether to acquire outside support, and if so, what to acquire, how to acquire it, how much is needed, and when to acquire it.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
During the Planning phase, a project manager or scrum master will begin creating a procurement work plan, if one is needed.
Detailed Guidance
It is critical, during the Planning phase, to work with your organization's Procurement team (if one exists) as you begin the procurement process. There may be established policies and procedures that your project team must follow when procuring goods and services.
As you being to identify potential vendors and go down the RFP (Request for Proposal) process, you must have your requirements identified, as well as any critical dates, resources, etc.
Step 12: Value
Benefits Register
The Benefit Register is used to define project value, set the baseline measurements for each benefit metric, measure and track benefits, report outcomes, determine gaps and monitor and report/mitigate/remediate gaps between goals and actual results.
Implementation
The purpose of the Benefits Realization Plan is the plan for tracking proposed benefits over the initiative’s total life-cycle to ensure that the deliverable that the project provides generates benefits as intended (or perhaps new, unforeseen ones) over its life-cycle. For each potential benefit identified, the plan details how to measure, track, and report them as achieved. The Project Manager is responsible for the successful completion of the project, and the organization/sponsor is responsible for realizing the benefits. Use the Benefits Register to properly record the benefits and track value realization, including:
- Identify benefit categories important to the organization
- Describe the benefit expected
- Determine if the benefit is quantitative (hard) or qualitative (soft)
- Measure outcomes by defining the benefits metrics, including what will be measured to determine whether or not the benefit has been captured, how it will be measured, and how often
- Designate an owner responsible for signing-off on the measurement, and,
- Understand roles.
Detailed Guidance

Benefits Realization Plan
Once the metric(s) defined, benefits reporting should be part of the Communications Plan, including defining:
- How benefits tracking will be communicated to the appropriate stakeholders
- Who needs to be kept updated on the status of this benefit
- What form will this communication take
- How often benefit(s) communications will be distributed.
The purpose of the Benefits Register is the plan for tracking benefits over the initiative’s total life-cycle to ensure that the deliverable that the project provides generates benefits as intended (or perhaps new, unforeseen ones) over its life-cycle. This is defined in the Benefits Realization Plan and for each potential benefit identified, the plan details how to measure, track, and report them as achieved. The Project Manager is responsible for the successful completion of the project, and the organization/sponsor is responsible for realizing the benefits. Use the Benefits Register template to properly record the benefits and track value realization, including:
- Identify benefit categories important to the organization
- Describe the benefit expected
- Determine if the benefit is quantitative (hard) or qualitative (soft)
- Measure outcomes by defining the benefits metrics, including what will be measured to determine whether or not the benefit has been captured, how it will be measured, and how often
- Designate an owner responsible for signing-off on the measurement
- Understand roles

Measuring Outcomes
- Identify project benefit(s) (BENEFIT TYPE and DESCRIPTION)
- Includes a detailed narrative description of the benefit
- Start from those defined in the Business Case.
- For this benefit to be realized, determine what impact(s) will be derived by the project. For example, document whether the benefits are:
- Tangible (“hard” benefit that you can measure, e.g. cost savings) vs Intangible benefits (“soft” benefit that is often more difficult to concretely measure, e.g. employee morale increases)
- Near-term vs. mid-term vs. long-term (Time Horizon)
- Intermediate (benefits enable other benefits) or End benefits (beneficial end states that the organization desires)
- Define the benefits METRIC (what will be measured to determine whether or not the benefit has been captured).
- It should include:
- How metric will be measured
- How often will metric be measured
- Metric Types:
- Current:
- Developed in Initiation phase as project value is determined
- Sets a baseline measurement;
- Ensure that these goals are realistic and reflect the project scope
- Defines benefits or value before/during the project
- Actual:
- Developed in Value phase when measurements of benefits take place
- Defines actual benefit
- Value at defined intervals when benefits are actualized
- GOAL:
- “Expected Metric”
- Defines expected benefits or value during the value realization stage
- i.e., “expected or proposed state”
- Current:
- It should include:
- What happens if there is a difference between what is expected/planned and what is found:
- VARIANCE: Measured gaps between the goal and actual results
- EXCEPTION CAUSE: Reason for the variance
- REMEDIATION: Plan to resolve variance
- Who will be designated as the owner responsible for signing-off on the measurement.
- Overview
- Work Management
- Scope Management
- Schedule Management
- Cost Management
- Issue Management
- Change Control
- Org Change Management
- Quality Management
- Resource Management
- Communication
- Risk Management
- Benefits and Value
- Procurement Management
- Stakeholder Management
Project Delivery
With a clear definition of the project and a suite of detailed project plans and an approved project schedule, budget, resource plan, and business case, the project can now enter the Delivery phase.
During the Delivery phase, the development and delivery of the project benefits are managed and monitored. Of equal importance, keep all stakeholders informed of progress and escalate any issues.
Goals:
- Deliver benefits
- Actively communicated progress to plan
- Analyze and manage risks and issues
- Status reports
- Execute mitigation plans to reduce risk and action plans to resolve issues
Delivery of Benefits
The Delivery phase is where the application of funds to the project creates the defined service, product, deliverable, process or solution. Through the appropriate level of project monitoring and control, the project manager will provide transparency into the project and appropriate information to allow stakeholders to make educated and informed decisions. Using these project tools, the project manager will be able to effectively manage the triple constraint (time, scope, and cost) that delivers the greatest value to the organization.
During the Delivery phase, the implementation of the planned solution solves the problem specified in the project’s requirements. In product and system development, a design (or solution) created results in a specific set of product requirements.
Managing the production of the product, service, process, or deliverable through any implementation methodology including Agile, Scrum, Waterfall, or others. Generally, all will follow what is essentially a “design-build-test-deploy” approach. Using this approach, you will create certain deliverables that are unique to your implementation methodology and attach them to your project file structure or store them in an on-line project repository such as SharePoint.
As the Delivery phase progresses, others across the organization will become more involved in planning for the final testing, production, and support, if the solution requires such. Throughout this step, keep the project sponsor and other key stakeholders informed of the project’s status according to the agreed-on frequency and format of communication. Update and publish the project plan on a regular basis. Emphasize the anticipated end in terms of cost, schedule, and quality of deliverables in status reports. Review each project deliverable produced for quality and measured against the acceptance criteria.
Continuously monitored progress, make appropriate adjustments and record them as variances from the original plan. So, during the construction of each deliverable during the Delivery phase, a suite of management processes are undertaken to monitor and control the deliverables being output by the project.
Report progress information in the delivery stage through regular team meetings and via PPM reports and the dashboard. The project manager uses this information to maintain control over the direction of the project by comparing the progress reports with the project plan to measure the performance of the project activities and take corrective action as needed. The first course of action should always be to bring the project back on course. If that cannot happen, the team should record variations from the original plan and record and publish modifications to the plan. These processes include managing time, cost, quality, change, risks, issues, suppliers, customers, and communication.
Once all the deliverables are completed and a clear review and approval process has taken place with appropriate project stakeholders and the project sponsor, the project is ready for closure.
Value of Delivery
Funds applied in the Delivery phase to the project create the defined service, product, deliverable, process, or solution. Through the appropriate level of project monitoring and control, the project manager will provide transparency into the project and appropriate information to allow stakeholders to make educated and informed decisions. Through these project tools, the project manager effectively manages the triple constraint (time, scope, and cost) that delivers the greatest value to the organization. Communication, stakeholder management, and change control are critical processes during this phase.
Monitoring and Controlling
Project Delivery, along with project monitoring and control, involves the application of project resources to do the required work as defined in the project planning process. During Delivery, measure project performance against planned in order to identify variances from the planned project outcomes. Variances are documented via status reports. The next step is for the PM to determine whether there is a need for corrective action. When moving from Planning to Delivery, the project will require key steps and the production of deliverables to assist with making sure your project meets the desired outcomes, during the time frame expected, and with the resources anticipated.
In order to effectively manage the scope of work and ensure that the project achieves the original objectives under the original scope, schedule, and budget constraints, the organization will establish a Change Control Board (CCB) for all (medium and large) projects. The CCB is a committee that makes decisions regarding whether approval for implementation of presented proposed changes to a project above an agreed-upon threshold. The CCB and Project sponsor must approve any changes to the baseline project above an agreed-upon threshold after review with the Project manager and the project team. The project manager and project sponsor present the changes to the CCB during a regularly scheduled review meeting after performing an appropriate impact analysis of the change to the project scope, schedule, cost, and resources. If the CCB approves, communicate the changes and the impacts to the project – up to and including re-base lining the project – to the project team and all project stakeholders through the project communications management plan process. The CCB consists of the governance board, project stakeholders, or their representatives, and must include the project sponsor and the portfolio owner. Decisions reached by the CCB are final and binding.
Delivery Implementation Methodology
Any implementation methodology including Agile, Scrum, Waterfall, or others can be used to manage the production of products, services, processes, or deliverables. Generally, all will follow a “design-build-test-deploy” approach. Using this approach, you will create certain deliverables that are unique to your implementation methodology and store them in an online repository.
Work Management
Action Items
The Action Items Template helps organize meetings by tracking agenda items, decisions, and action items with responsibilities, due dates, and statuses. Share the agenda in advance, update action items during the meeting, and distribute revisions within two business days. Unused fields can be removed for simplicity.
1-on-1 Meeting Agenda
The 1-on-1 Meeting Agenda Template ensures productive and organized meetings. It includes sections for decisions, agenda items, and action items with responsibilities and due dates. Share the agenda beforehand to allow preparation, and update it during the meeting. Send the revised version within two business days to confirm next steps.
PMI Guidance: Direct and Manage Work
Direct and Manage Project Work is the process of leading and performing the work defined in the project management plan and implementing approved changes to achieve the project's objectives. The key benefit of this process is that it provides overall management of the project work.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Tools / Techniques
PMI Guidance: Manage Project Knowledge
Manage Project Knowledge is the process of using existing knowledge and creating new knowledge to achieve the project’s objectives and contribute to organizational learning. The key benefits of this process are that prior organizational knowledge is leveraged to produce or improve project outcomes, and the knowledge created by the project is available to support organizational operations and future projects.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Monitor and Control Work
Monitor and Control Project Work is the process of tracking, reviewing, and reporting the progress to meet the performance objectives defined in the project management plan. The key benefit of this process is that it allows stakeholders to understand the current state of the project, the steps taken, budget, schedule, and scope forecasts.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
Work Management is the approach taken to ‘getting the work done’ which may include projects, processes, planning, and tools. The goal is to provide clarity to project team members on how work is to be done, while collaborating across all levels of an organization. Done correctly, work management ensures that everyone has the information they need to accomplish the work that matters most.
Detailed Guidance
A good place to start when defining how the team should work is through the Project Charter. A charter will state what is being done, how much it will cost, what is in and out of scope, etc. Essentially, it answers the 5 W’s – Who, What, When, Where, and Why.
An effective project manager or scrum master would also provide guidance on any other specific processes necessary to deliver a project, such as change and deployment management, or how to escalate issues.
Scope Management
Business Requirements
Business Requirements describe the characteristics of the product, service or result that the project is undertaken to create, and can be used to further clarify the contents of the charter and elaborate on the details of the scope items. It is helpful to further enumerate a list of all major deliverables in terms of business function and the outcomes of business functions, as well as any other detailed project information available.
Business Requirements describe the characteristics of the product, service or result that the project is undertaken to create, and can be used to further clarify the contents of the charter and elaborate on the details of the scope items. It is helpful to further enumerate a list of all major deliverables in terms of business function and the outcomes of business functions, as well as any other detailed project information available.
Functional Requirements – Requirements Mapping
In Functional Requirements – Requirements Mapping, functional requirements define specific steps to achieve the task defined in the use case – how the user will do the work to meet the business requirements. It is a detailed breakdown of the features list. Requirements mapping ties or “maps” a Business Requirement ID to Business Requirement Description to Functional Requirement ID to Functional Requirement Description to Use Case to Test Case.
PMI Guidance: Validate Scope
Validate Scope is the process of formalizing acceptance of the completed project deliverables. The key benefit of this process is that it brings objectivity to the acceptance process and increases the chance of final product, service, or result acceptance by validating each deliverable.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Tools / Techniques
PMI Guidance: Control Scope
Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. The key benefit of this process is that it allows the scope baseline to be maintained throughout the project.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Tools / Techniques
Implementing the Guidance
As Dwight D. Eisenhower said “In preparing for battle, I have always found that plans are useless but planning is indispensable”
Requirements define the scope of a project and the criteria for its success. They also describe what the system must do. Whether or not the system fulfills those requirements determines the success or failure of a project. Managing requirements effectively increases the probability of a project’s success. Therefore, defining clear, correct, and complete requirements, and managing them during the project, is critical for a system development project and for maintaining the integrity and performance of a system over time.
Detailed Guidance
During the Initiation Phase, the team works from the big picture (scope) to a detailed description of how the requirements will be met (technical requirements). During the Delivery phase, the requirements are further refined from the business requirements through to the test case, as indicated below.

Requirements Management
The Requirements Plan identifies the process and procedures used to plan, develop, monitor, and control requirements in all stages of a project’s life-cycle. This document is the foundation for all project requirement management policies and procedures. Each step feeds the next one, and all steps are documented in a Requirements Trace-ability Matrix (RTM) to check to see if the current project requirements are being met (figure below). Use the Business Requirements and Functional Requirements – Requirements Mapping Templates. The RTM can be found as a sheet in the Functional Requirements template.

Requirements Trace-ability Matrix
Schedule Management
Work Breakdown Structure & Schedule Planning Worksheet
The Work Breakdown Structure & Schedule Planning Worksheet helps teams organize tasks and schedule project phases. It includes columns for task IDs, subtasks, resources, effort hours, deliverables, dependencies, duration, and start/end dates. This template provides a clear overview for project managers and sponsors to track progress, manage resources, and ensure timely delivery.
Change Definition Worksheet
PMI Guidance: Control Schedule
Control Schedule is the process of monitoring the status of project activities to update project progress and manage changes to the schedule baseline to achieve the plan. The key benefit of this process is that it provides the means to recognize deviation from the plan and take corrective and preventive actions and thus minimize risk.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
Schedule Management is the process of defining project tasks, their durations, dependencies, and assigned resources, to complete the project within a designated time frame. It also includes monitoring and reporting on the schedule to ensure the project is delivered on time.
Detailed Guidance
Managing your schedule, dependencies, and resources assigned does not have to be implemented using a PPM tool. If a tool is not available, applications such as Microsoft Excel are a great resource for creating simple task lists, or something a bit more sophisticated, that appears like a Gantt chart.
In an Agile project, this would equate to understanding what is being delivered in each sprint, while using the daily stand-ups to determine progress towards completing tasks in the sprint. The goal is to ensure that the team is aligned on tasks, priorities, and due dates, while also providing a clear view into the critical path.
Cost Management
Work Breakdown Structure & Schedule Planning Worksheet
The Work Breakdown Structure & Schedule Planning Worksheet helps teams organize tasks and schedule project phases. It includes columns for task IDs, subtasks, resources, effort hours, deliverables, dependencies, duration, and start/end dates. This template provides a clear overview for project managers and sponsors to track progress, manage resources, and ensure timely delivery.
Budget Planning Worksheet
The Budget Planning Worksheet is used to develop an estimate, as needed, primarily for external or vendor expenses.
Benefits Register Template
The Benefit Register is used to define project value, set the baseline measurements for each benefit metric, measure and track benefits, report outcomes, determine gaps and monitor and report/mitigate/remediate gaps between goals and actual results.
PMI Guidance: Control Costs
Control Costs is the process of monitoring the status of the project to update the project costs and managing changes to the cost baseline. The key benefit of this process is that it provides the means to recognize variance from the plan in order to take corrective action and minimize risk.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
- Tools / Techniques
- Outputs
Implementing the Guidance
Cost management is the process of estimating, allocating, and controlling project costs. This may include project labor, contract costs, hardware and or software, direct, and indirect costs. Even in the case of Agile projects, where costs may seem to be a bit more fixed because of fixed sprint durations, you may have outside costs such as contract labor or software licenses, subscriptions, etc., that need to be managed and monitored. By managing costs, you may prevent budget overruns, avoid the risk of unforeseen expenses, and help with future project planning.
Detailed Guidance
The goal of managing your costs is to ensure that your project is delivered within budget, as well as to predict costs at the completion of the project. When a budget is established at the beginning of a project, it is the Project Manager’s or Scrum Master’s job to monitor and control the budget and report any variances.
When establishing and reporting on your budget, it’s important to ensure that you’re gathering all of your cost sources – labor (internal and external), assets (software licenses, hardware), any fixed costs, direct/indirect costs, or sunk costs. Your organization may provide you with guidance on the specific types of costs they’d like to capture and manage.
There are 4 components to cost management: resource planning, cost estimation, cost budget, and cost control. Part of cost management is ensuring that a process is in place for requesting additional funds, or, how to ‘return’ funds if any go unused.
Issue Management
Issue Log
The Issue Log will aid in managing issues once determined.
Implementation
The main differences between Risks and Issues are related to timing and probability. The language used about issues is in the present tense because it describes threats or opportunities at hand and how to deal with them – a situation that is certain, and an impact and what to do about it. For all issues at hand, the project team needs to act immediately to resolve them, and an action plan is needed that has action items listed in priority. Issues are not “mitigated” – they are resolved. Issues recorded in the issues log should be discussed almost every day.
While risk is the potential issue that may or may not happen and can impact the project positively or negatively, once a risk actually occurs, it is denoted as “Risk Realized” on the Risk Register and a corresponding issue is immediately opened on the Issue Log. Action Plan development immediately commences to resolve the Issue.
Additionally, during the Project Life-cycle, unforeseen issues can arise independently of the risk management process, which also may impact the ability of the project to meet its stated objectives. The key to project success is in having a process in place to review and resolve issues before they severely impact the project. Issue management is an ongoing process iteratively performed throughout the project life-cycle at regular intervals and as the environment changes.
Detailed Guidance
The Issue Log is a tool for reporting and communicating what is happening with the project. It contains a list of ongoing and closed issues of the project. Every issue that arises, either transferred from the Risk Register or arising independently, should be entered in the issue log, along with a resolution plan, action owner, issue source (risk register vs. other sources/independent generation) and target resolution date. The person who was assigned to the risk should also be assigned as issue owner is possible. Once the issue has been resolved, it should be closed in the log. Open issues, particularly those that have not been resolved by the target resolution date, must be logged on project status reports so that stakeholders are made aware of them and they can be escalated appropriately for faster resolution. Use the Issue Log template to track and monitor project issues.
Change Control
Change Request
The Change Request Template is used to expand or reduce the project scope, modify policies, processes, plans, or procedures, modify costs or budgets, or revise schedules.
Change Request Log
The Change Request Log allows you to track changes to business requirements and functional requirements.
PMI Guidance: Perform Integrated Change Control
Perform Integrated Change Control is the process of reviewing all change requests; approving changes and managing changes to deliverables, organizational process assets, project documents, and the project management plan; and communicating their disposition. It reviews all requests for changes or modifications to project documents, deliverables, baselines, or the project management plan and approves or rejects the changes.
The key benefit of this process is that it allows for documented changes within the project to be considered in an integrated fashion while reducing project risk, which often arises from changes made without consideration to the overall project objectives or plans.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
Change happens on every project, and like everything else, it must be managed and communicated to ensure success. Clear communication and agreement is key to managing stakeholder expectations as the project evolves and change happens!
Detailed Guidance
Even with a clearly defined scope, there will almost always be requests for change as the project progresses. Don’t be fooled! Even a high number of “small” changes can negatively impact the project schedule and budget. To avoid scope creep, route all changes, including small ones, through a simple, formal Change Control Process. The process should match the complexity and risk of the changes; in other words, the more complex the change, the more rigorous the process for change approval. Come to agreement on a standard and simple change control process for changes. Make sure that the change control process that matches project complexity and risk of the changes. Come to an agreement on an approach for escalation of change requests and the appropriate or threshold level of decision-making authority for the approval of change – from the project management level, through sponsor, to a governance or Change Control Board (CCB). Clear communication and agreement is key to managing stakeholder expectations!
The project manager acts as the change “gate-keeper” and performs the initial impact assessment, reviewing for:
- Relevance to project
- Impact on requirements
- Impact on budget
- Impact on schedule
- Impact on resourcing
If the answer is “yes” to impacts related to the triple constraints, then proceed to the change process and determine the appropriate level of escalation.
During the Initiation Phase, the team works from the big picture (scope) to a detailed description of how the requirements will be met (technical requirements). During the Delivery phase, the requirements are further refined from the business requirements through to the test case.

Assess Change Impact
Evaluating the level of change impact in terms of whether the requested change requires significant changes to existing business requirements or new business requirements entirely:
- Level 1: Change Related to Existing Requirements
- Level 2: Multiple Requirements Changing – Greater impact
- Level 3: No Requirements Found; New Requirements Identified – Generally largest impact
Return to the stakeholder who submitted the request to go through the process of identifying the potentially new requirement/requirements that relate to this change. If the sponsor agrees to the new requirements, the project manager may be able to approve the change.

Change Control Process
Organizational Change Management
Project Charter Template
The Project Charter Template is a structured tool to outline the foundational details necessary for project initiation and alignment. It guides teams through defining the project’s purpose, identifying stakeholders, setting clear objectives, and specifying required resources. Each section prompts considerations around goals, assumptions, constraints, and potential risks, offering a complete view of why the project is needed and what it aims to achieve. Additionally, it includes areas for key deliverables, scope boundaries, budget estimates, and a timeline, helping ensure clear expectations and strategic alignment from the start.
Stakeholder Engagement Plan Template
The Stakeholder Engagement Plan Template helps project managers capture key information about stakeholders, including their role, interests, influence, and needs. It provides fields to document the stakeholder’s understanding, motivation, knowledge, skills, and organizational power. Additionally, it includes sections for influence strategies and engagement plans. This template enables project managers to develop customized approaches to build stakeholder support, align with project objectives, and meet expectations effectively.
Stakeholder Roles and Responsibilities Template
The Stakeholders Roles and Responsibilities Template outlines the roles and duties of key participants in a project, including Project Governance, Sponsor, Project Manager, Project Team, Stakeholders, and Subject Matter Experts. Each role is defined with specific responsibilities, such as strategic direction, project management, business value delivery, and expertise. This template helps ensure that everyone understands their responsibilities and contributions, promoting accountability and alignment with project objectives. By establishing clear expectations, it supports effective collaboration and smooth project execution.
Communication Plan
The Communication Plan Template is a one-page plan to define the communication strategy message content, delivery mechanism, sender, and time-frame (the “when”) throughout the phases of the change initiative.
Implementation
Change happens on every project, and like everything else, it must be managed and communicated to ensure success. Clear communication and agreement is key to managing stakeholder expectations as the project evolves, delivers benefits, and change happens!
Detailed Guidance
- Stop talking and listen
- Have they heard this before?
- What do they fear?
- What do they know that you don’t?
- Remove the secrecy
- Bring them with you
- Don’t assume they get it
- Make it matter (WIIFM)
Stakeholder issues can be managed if you engage from the start! Stakeholders are identified during the development of the Project Charter, Stakeholder Engagement Plan, and Stakeholder Roles & Responsibilities activities of the Initiation phase, and Communication Plan needs to be designed during the project Planning phase. They will be actively reviewed, updated, executed and managed during the delivery phase as the project begins to deliver change. While the project manager is responsible for communications management – making sure all communications are received and understood by stakeholders – ensure that you have the right people engaged to communicate issues to business stakeholders. Enforcing communication at key milestones provides for regular feedback by stakeholders while stakeholder engagement at earlier milestones will help head off potential issues. Using language that stakeholders are familiar with and relate to will avoid miscommunication brought on by highly technical communications that result in stakeholders misunderstanding your message, and a missed opportunity to involve them in resolving issues.

Know Your Stakeholders
Evaluate and re-evaluate your stakeholders frequently, as indicated in the figures above and below. Consider anyone that can influence your project success or believes your project will impact them:
- Do they understand?
- Do they understand benefits?
- Do they believe the change is reasonable?
- Do they know how?
- Experience with change management techniques
- Experience with project management
- Are they motivated?
- What is their WIIFM (“What’s In It For Me?”) for the project?
- Are they engaging in the process?
- What are their key interests associated with this project?
- What is their power?
- What is their level of influence on the project outcomes?
- Do they have the capacity to participate?

Re-check Their Quadrant
As you periodically re-evaluate, follow with active stakeholder engagement & management:
- Help them understand
- Give them relevant information so they can support the effort
- Show them how
- Share techniques and tools
- Explain why you are performing certain tasks
- Show them how to help you help them
- Support motivation
- Tie their goals to your project
- Show progress, outcomes and benefits
- Leverage power
- Seek out influencers
- Think broadly
- Stakeholder issues can be managed if you engage from the start!
- Ensure that you have the right people engaged to communicate issues to business stakeholders.
- The project manager is responsible for communications management – making sure all communications are received and understood by stakeholders.

Manage Stakeholders
- Communication plans need to be designed during the project planning phase.
- Enforce communication at key milestones, so that stakeholders can give regular feedback as the project progresses.
- Stakeholder engagement at earlier milestones helps mitigate potential issues.
- Sending a project status update will not be sufficient for all of your stakeholders.
- Avoid sending too much information; decide how to best inform each stakeholder.
- Commit to “just right” communications
- Be careful with “CC”
- Don’t invite everyone to every meeting
- Avoid too little or too much detail
- “Pop in” / hallway conversations – be careful that you have all appropriate stakeholders kept up to speed when this is happening
- Keep communications short, clear, focused
- Vehicles for Project status updates:
- Project meetings
- Change log
- Risk and issues reporting
- Project deliverables
- Status report guidelines:
- All projects should have some level of project status reporting to communicate plans progress, and outcomes according to planned budget and schedule.
- If a project is yellow or red status, more frequent status reports are required to properly escalate so that issues can be monitored and resolved.
- Use language that stakeholders are familiar with and relate to.
- If your communication is highly technical, your stakeholders might misunderstand your message, and you will miss an opportunity to involve them in resolving issues.
- Frequency of sponsor/stakeholder meetings, reports and updates will depend on the complexity and size of the project and the issues/risks/external dependencies that arise:
- If the project is large, you may want to consider weekly status meetings and communications.
- Adhoc meetings should be called as necessary to report on and solve project issues, address risks, or as needed to review project deliverables.
Quality Management
Quality Management Plan
PMI Guidance: Manage Quality
Manage Quality is the process of auditing the quality requirements and the results from quality control measurements to ensure that appropriate quality standards and operational definitions are used. The key benefit of this process is that it facilitates the improvement of quality processes.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
To ensure that the project results in deliverables that meet the customer’s requirements, it is necessary to use a formal Quality Management Process. This process involves implementing the Quality Assurance and Control activities specified within the Quality Plan to manage the level of quality within the project.
Detailed Guidance

Quality Management Process
- Level 1: Conduct tests at the end of the project to ensure required quality levels are met
- Level 2: Measure quality at defined stage gates and compare actual to target values. Document and investigate deviations and create remediation plans.
- Level 3: Evaluate quality of deliverables throughout the project life-cycle as features are completed. Document and investigate deviations and create remediation plans.

Quality Measures
Document your quality management results. Getting the business involved early and often in the quality process will help you ensure that deliverables are meeting business requirements.
- Start with business and functional requirements
- Create a quality plan for performing tests
- Build test cases
- Perform testing and document results
- For each deviation from a quality target, investigate and record the cause of the deviation, and put a remedial action plan in place
- Each action plan should have a resolution date and sign-off owner
- Note the date of sign-off once the deviation has been resolved
Resource Management
Staffing Plan
The Staffing Plan is used to facilitate the acquisition of the best team and resources for the project, considering both the resources needed and the resources available, and if all ideal resources are not available internally, how these will gaps be filled.
RACI Matrix
The RACI Matrix is a powerful tool to assist in the identification of roles and assigning of cross-functional responsibilities to a project deliverable or activity.
PMI Guidance: Acquire Resources
Acquire Resources is the process of confirming human resource availability and obtaining the team necessary to complete project activities. It’s also the process of obtaining other necessary resources such as facilities, equipment, materials, and supplies. The key benefit of this process consists of outlining and guiding resource selection.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Develop Team
Develop Team is the process of improving competencies, team member interaction, and overall team environment to enhance project performance. The key benefit of this process is that it results in improved teamwork, enhanced people skills and competencies, motivated employees, reduced staff turnover rates, and improved overall project performance.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
PMI Guidance: Manage Team
Manage Team is the process of tracking team member performance, providing feedback, resolving issues, and managing team changes to optimize project performance. The key benefit of this process is that it influences team behavior, manages conflict, resolves issues, and appraises team member performance.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
Resource Management
Detailed Guidance
There’s a lot of reasons, do any of these resonate with you? When you were asked to start a PMO, was it to:
- improve project performance?
- reduce costs and increase value delivery?
- better utilization and allocation of resources?
- improve productivity?
- ensure alignment with strategy?
Perhaps you fall in the category of, “I’m just being asked to help get it done with projects. Our projects need to be aligned with strategy and our PMO needs to help ensure that that happens.”
All of these are great reasons why PMOs are started. Here are a few things to think about when you’re focusing on why your PMO is existing or being asked to be created in the first place.
Communication
Action Items
The Action Items is used to assign Action Items and track them to closure.
1 on 1 Meeting Agenda
The 1 on 1 Meeting Agenda is used for small informal meetings to note decisions, options, discussion points, assign Action Items and track them to closure.
One Page Executive Dashboard
(Excel) The One Page Executive Dashboard is the key that you must give executives the information – at the individual project level – they need to make educated and informed decisions – tells them what they need to know to make educated and informed decisions.
Communication Plan
The Communication Plan Template is a one-page plan to define the communication strategy message content, delivery mechanism, sender, and time-frame (the “when”) throughout the phases of the change initiative.
RACI Matrix
The RACI Matrix is a powerful tool to assist in the identification of roles and assigning of cross-functional responsibilities to a project deliverable or activity.
PMI Guidance: Management Communication
Manage Communications is the process of creating, collecting, distributing, storing, retrieving, and the ultimate disposition of project information in accordance to the communications management plan. The key benefit of this process is that it enables an efficient and effective communications flow between project stakeholders.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
Depending on the size and formality of the project meeting, their decision-outcomes, and all Action Items, the Actions Items Template is useful for tracking and documenting. The 1 on 1 Meeting Agenda can be used for smaller or less formal meetings. It is important to assign Action Items and track them to closure, and this template will assist the project manager in this important activity.
Detailed Guidance
Reporting should be simple and information sharing straightforward. Use the Status Reports/Executive Dashboard template to provide information for each project and to provide input for the entire organizational portfolio of projects. The key to this report is that you must give executives the information they need to make educated and informed decisions…then STOP! Do not provide too much information. It only muddies the waters of effective decision-making. If you want your executives to focus, give them that focus.
Make it a living document and fill it in as you have updates – it will make your life so much easier. Submit it at the end of the week before the weekend comes and you can forget everything!
- Summary: Provide a simple Bottom Line Up Front (BLUF) status that can stand alone to describe the project status.
- Key Decisions Made: Focus on a summary of decision and outcomes as a result of the decision.
- Items Requiring Management Attention: This is where you identify support you need from management. USE THIS to manage up.
- Activities Accomplished This Reporting Period: Highlights of what got done.
- Planned Activities for Next Reporting Period: Highlights of what you intend to get done.
- Deliverables & Milestones:
- Major points of progress for the project
- Leverage COLOR to tell the story of status
- Track % complete of deliverable/milestone – you can include column for “Expected % Complete”
- Original vs Current Delivery date = shows planned vs actual on any fields where metric is needed
- Comments: if white, then explain progress towards baseline; if green, then explain how it’s progressing or how it got BACK there; if amber/red, what are you doing to return deliverable to green status
- Issues & Risks:
- Focus on focus on the high impact items
- Leverage COLOR to tell the story of status
- Always identify an owner
- Prevent blindsiding management
Risk Management
Project Management Evaluation – Change Lessons Learned
The Project Management Evaluation is a lessons learned template to evaluate the project management process and the elements of the change process that occurred during the project.
Risk Register
The Risk Register is an excel worksheet that helps quantify and mitigate identified risk.
Issue Log
The Issue Log will aid in managing issues once determined.
PMI Guidance: Implement Risk Responses
Implement Risk Responses is the process of implementing agreed-upon risk response plans. The key benefit of this process is that it ensures that risk responses are executed as planned in order to address project risk exposure and minimize project threats while maximizing project opportunities.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
Risk and Issue management is an ongoing process iteratively performed throughout the project life cycle at regular intervals and as the environment changes. While risk is the potential issue that may or may not happen and can impact the project objectives positively or negatively, once a risk actually occurs, it is denoted as “Risk Realized” on the Risk Register and notes on the Project Mgmt. Evaluation – Change Lessons Learned for further analysis during Project Closure. A corresponding issue is immediately opened on the Issue Log template and Action Plan development commences to resolve the Issue.
Detailed Guidance
It is a process that involves everyone on the Team. The role of the project manager, sponsor, or stakeholder is to understand how to execute risk response plans effectively, and to assess the success of current risk response execution.
Monitoring and Control
As part of ongoing Delivery Phase Monitoring and Control, use the Risk Register that was developed during the Planning phase:
- Are risks current and assumptions valid?
- Is potential impact and probability still accurate?
- Are there new risks?
- Are risk response plans being executed to effectively reduce the probability of risk occurrence?
- Is risk probability and impact being reduced or eliminated?
- Are Action Plans being implemented when risks become issues?
- Have responses been effective in mitigating or reducing the risk?
Risk Identification and Assessment
Track each risk throughout project execution:
- Has the risk actually occurred?
- Status: Open or closed
- Compare cause identified during planning to actual cause of risk event.
- If the risk occurred, if the risk actually became an ISSUE, what was the actual impact on the project?
Risk Response
- Reassess open risks:
- Compare initial risk assessment to current assessment.
- Reassess impact of risk event occurring.
- Re-assess response: Does the initial decision to avoid, transfer, mitigate, or accept the risk still apply?
- Should a new response be chosen?
- If necessary, create a new response plan to mitigate or resolve the risk.
Risk management is an ongoing activity. Every project status meeting should include a review of risk and issues as a standing agenda item.
- Risk management should be a topic for all status meetings and included on all Project status meetings as standard agenda items:
- Schedule
- Budget
- Scope
- Progress
- Risks
- Issues
- Review current risks and request updates from owners
- Evaluate responses to ensure they still make sense
- Has the environment caused a change in probability or impact?
- Evaluate priority with this new information
- Determine action items as a result of discussion
Benefits and Value
Benefits Register
The Benefit Register is used to define project value, set the baseline measurements for each benefit metric, measure and track benefits, report outcomes, determine gaps and monitor and report/mitigate/remediate gaps between goals and actual results.
Implementation
Use the Benefits Register developed during the Planning phase to review, measure and report on benefits realized and delivered during this phase. It assists in defining how benefits tracked are communicated to the appropriate stakeholders, as defined in the Benefits Realization Plan. Use it to determine who needs to be kept updated on project benefits as they are realized (or not, and why not), what form this communication will take, and how often will it be distributed.
Detailed Guidance
Active benefits realization requires more than just measuring and reporting:
- Where possible, begin measurements while the project is on-going. It is easier to make adjustments that will affect benefits realization while the team is active and resources are dedicated to the project.
- If a metric cannot be gathered until the project is completed, use a related quality measure as a close indicator of how large of a gap exists between the goal measurement and the actual measurement.
- Intervene at the first sign of an issue and make a course correction. A project that is completed on-time and on-budget, but fails to deliver benefits is a failed project.
- If early tests reveal that the project is at risk of failing to realize benefits, the Project Manager must reassess the project plan and scope.
- Escalate to the Sponsor to decide whether benefit goals need to be adjusted, or whether scope, budget, or schedule must be expanded.
- Communicate project success. Communicating measured benefits, especially early on, can increase stakeholder buy-in and enthusiasm for the project and its outcomes, and decrease organizational resistance during implementation.
Procurement Management
PMI Guidance: Conduct Procurements
Conduct Procurements is the process of obtaining seller responses, selecting a seller, and awarding a contract. The key benefit of this process is that it provides alignment of internal and external stakeholder expectations through established agreements.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
In project management, Procurement is the management of vendors during 4 main phases:
- Planning – Identifying the need for vendors/procurement of resources
- Conducting – the process of selecting a vendor
- Controlling procurements – contract management
- Closure – closing out the contract(s)
Procurement Management is important for several reasons. It helps the company ensure that they make the most informed decision when it comes to purchasing goods and services, and sets the path for a lasting, successful relationship with the vendor. It also ensures that the company gets what they want, what they need, and for the price they want to pay.
Detailed Guidance
A project manager does not need to be a professional contract administrator to be successful with Procurement Management. If your company has a specific procurement department, it’s important to work with them, and include them in your processes, to avoid any potential delays. If there is no procurement department, try to leverage what has been done in the past.
As a project manager, it’s important to understand the contract in its entirety. Some key areas to really focus on include:
-
- Specific deliverables to be provided – is it software? Documentation? Hardware?
- Resources assigned – if you asked for specific resources, make sure you get them!
- Deliverable dates – review, and then review again, the dates that items are to be delivered.
- Escalation path – who do you call if a deliverable is not provided on the specified date? Who should you talk to if a resource is not performing as expected, which may jeopardize your delivery date?
- Termination clause – if you need to cancel the project for any reason, understand your termination clause, and potential costs to your organization.
Stakeholder Mangement
PMI Guidance: Manage Stakeholder Management
Manage Stakeholder Engagement is the process of communicating and working with stakeholders to meet their needs/expectations, address issues as they occur, and foster appropriate stakeholder engagement in project activities throughout the project life cycle. The key benefit of this process is that it allows the project manager to increase support and minimize resistance from stakeholders, significantly increasing the chances to achieve project success.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
Stakeholder Management enables project managers and/or scrum masters to manage the people and relationships with those who have an impact on your project. By understanding how they can influence and impact your project, you can use effective communication techniques to keep them ‘on board.’
Detailed Guidance
Managing stakeholders may take time in the very beginning of a project or sprint, but if done correctly, can become quick and efficient over time. To ensure effective stakeholder management, project managers and scrum masters should do the following:
- Identify all stakeholders – this includes those can positively or negatively impact your project, or, anyone who thinks they can
- Create a stakeholder engagement plan
- Ensure continuous stakeholder interaction
- Report back to stakeholders
- Overview
- Acceptance
- Lessons Learned
- Archive
- Transfer
- Celebrate
Project Closure
Project Closure involves releasing the final deliverable to the customer, handing over project documentation to the business and support teams, terminating supplier contracts, releasing project resources, and communicating project closure to all stakeholders. In both traditional waterfall and Agile projects, a lessons learned or sprint retrospective is the last step conducted.
Growth comes from learning and so a critical part of this phase is the lessons learned process. It is important for project performance to be evaluated so the organization can determine what worked well and should be repeated and what may need to change for future projects.
Goals:
- Review status of benefits with stakeholders
- Dismantle project team and operating model
- Celebrate project success
- Collect and prepare lessons learned for future project application
Project Closure
The closing process formalizes the end of a phase or project. Having tasks defined in the closing phase of your project ensures administrative and contract items are completed, disseminated, and archived. Completing the closure phase will generate the final performance metrics for the project, document and distribute lessons learned, as well as obtain formal project approval from the project sponsor. The project team should conduct a post-project review to discuss materials presented, areas for improvement, and what has been successful. If there are any vendor contracts, remaining invoices, or costs, reconciliations should be re-conducted as part of this phase.
The closing phase involves the specific tasks summarized below:
- Releasing the final deliverable to the sponsor
- Writing a formal project review report which contains the following elements: a formal acceptance of the final product (by the client)
- Conducting a post-implementation review with project stakeholders and distributing results to the stakeholders, as well as the PPMO for incorporation into the PPMO repository
- Conducting a project documentation review and transition with the business
- Completing weighted critical measurements (a match between the initial requirements laid out by the client against the final delivered product)
- Terminating supplier contracts and initiating support contracts, if applicable
- Conducting a lessons learned/sprint retrospective (this is a new step)
- Releasing project resources
- Formal project closure notification to higher management
- Communicating project closure to all stakeholders
- Celebrating the project completion with stakeholders
Project Closure Process
The Project Closure Checklist template provides the mechanism for group review and assessment of the project closure process to ensure the following of all closure steps.
Value of Closure
The completion of this phase ensures that all project activities and deliverables are finished and project documentation is archived. By following a closure process, you can ensure that vendors are paid, resources are released from project activities, and appropriate lessons learned have been completed and documented. Closure provides for the proper shutdown of activities and ensures a smooth handover to production or operations. It also provides for the assessment of the success of the project and gathers lessons learned to apply to future projects/sprints.
Acceptance
Project Charter
The Project Charter is a structured tool to outline the foundational details necessary for project initiation and alignment. It guides teams through defining the project’s purpose, identifying stakeholders, setting clear objectives, and specifying required resources. Each section prompts considerations around goals, assumptions, constraints, and potential risks, offering a complete view of why the project is needed and what it aims to achieve. Additionally, it includes areas for key deliverables, scope boundaries, budget estimates, and a timeline, helping ensure clear expectations and strategic alignment from the start.
Implementation
This is the first step taken when closing a project to confirm with stakeholders that the project has completed and deliverables accepted. It is important to list the summary of the project, reviewing the expected outcomes and planned deliverables from the business case and charter with the actual project deliverables.
Detailed Guidance
The purpose of obtaining project acceptance is formal recognition that all deliverables produced during the project implementation phase have been completed, tested, accepted approved by the project’s client/customer, and sanctioned by the project sponsor. As part of the acceptance process:
- Obtain project tool (templates) acceptance before they are leveraged to drive creation of deliverables.
- Obtain deliverable acceptance for major deliverables throughout the project life-cycle, when possible.
- Ensure deliverables are aligned with scope and requirements to avoid change requests.
- If deliverables are not approved and changes are out of scope, change request process must be followed.
- Use the scope and requirements documents, and the outcomes of the quality assurance and testing process, to ensure all deliverables meet acceptance criteria.
- Depending on size/complexity, more frequent deliverable acceptance helps ensure project success (see figures below):
- Small projects – deliverable acceptance at project completion
- Medium projects – Acceptance at major deliverable milestones & final deliverable acceptance at project completion
- Large projects – Acceptance at intermediate & major deliverable milestones; acceptance at project completion with final deliverable acceptance
- Obtain project acceptance at the end of the project from the sponsor, and is generally in the form of a meeting.
- However, waiting until the end of the project to start deliverable acceptance increases the chance of late changes and delayed project acceptance and closure.

Deliverable Acceptance

Multiple Deliverable Acceptance Milestones
Document deliverable completion and acceptance and the concurrence of the project customer, sponsor, and other stakeholders that the deliverable meets its objectives according to the acceptance criteria. The most common form of formal acceptance is a customer acceptance statement or document, acknowledging that the project deliverable was developed as the customer originally requested. Each major deliverable should identify:
- Deliverable name
- Acceptance criteria
- Are all features defined in requirements available and working as defined?
- Does the deliverable satisfy the requirements or scope statement?
- Are there any functionality gaps or issues:
- Create remediation plan and Change Requests if out of scope
- Identify date for re-evaluation of deliverable
- Acceptance date
- Acceptance approval (usually sponsor)
Lessons Learned
Project Management Evaluation – Change Lessons Learned
The Project Management Evaluation – Change Lessons Learned is a lessons learned template to evaluate the project management process and the elements of the change process that occurred during the project.
PMI Guidance: Close Project or Phase
Close Project or Phase is the process of finalizing all activities across all of the Project Management Process Groups to formally complete the project or phase. The key benefit of this process is that it provides lessons learned, the formal ending of project work, and the release of organization resources to pursue new endeavors.
Inputs
- Business Documents
- Business Case
- Agreements
- Enterprise Environmental Factors
- Organizational Process Assets
Implementing the Guidance
The lessons learned review should be held as close to the finish date of the project as possible to allows the business to identify the level of success of the project and list any lessons learned for future projects.
Detailed Guidance
Growth comes from learning. Both you and the organization need to learn from the experience…what worked well, what not so good…
There are three components of quality assurance that kick in once the project deliverables have been completed.
- Make sure you evaluate the tools and process you used to determine if the right level was applied for this project, and what other resources you may want for future projects. This process is called “Project Performance Assessment.”
- It is important for project performance to be evaluated so you can determine what worked well and should be repeated, and what may need to change for future projects. That process is called “Lessons Learned.”
- Upon completion of the project, the project benefits initially identified, then measured and tracked, need to be measured again to determine if the value expected to be obtained was realized during the days, weeks and months after the project was completed. This process is “Measuring Value” and it is the final phase of the project lifecycle. The differing foci of these three quality evaluations are compared in the figure below.

Growth comes from learning: It is important for project performance to be evaluated so you can determine what worked well and should be repeated, and what may need to change for future projects.
PROJECT PERFORMANCE ASSESSMENT | |
---|---|
Project Management Area
|
Assessment Question |
Templates |
|
Methodology
|
|
Tools | Did the tools used facilitate more effective project team members and more efficient project management process? |
Schedule | Gap between planned and actual start/end dates |
Budget | Gap between estimated and actual budget |
Resources | Gap between estimated and actual resource requirements |
Scope Changes | How many change requests were submitted and escalated? |
Team |
Team building, performance appraisal, development, and collaboration
|
Quality | Did deliverables satisfy quality requirements the first time at stage gates? |
Change Management |
|
Risk & Issues |
|
Stakeholder Management |
|
Use the Change Lessons Learned – Project Mgmt. Evaluation template to document your project closure evaluations. However, it is not enough to just hold the Project Closure Evaluation meetings – you need to:
- Include all project team members in the discussion. Everyone that was involved in project delivery should be a part of evaluating their role and the project as a whole.
- This is not an opportunity to point fingers, but really the time to dig into the root causes of the good and bad parts of the project.
- Analyze the information to determine what actually worked and what did not – and WHY so you can repeat or delete.
- Seek input from appropriate stakeholders. You can obtain valuable insights by asking key stakeholders to share their experience in engaging with the project team and process.
- Identify all project management strengths and weaknesses. The key to this is having an honest and open discussion with project team members. Restrict this meeting to the project team (which might include vendors), so that team members feel comfortable giving honest feedback about how the project was managed.
- Consider engaging a facilitator from outside the project to act as a neutral moderator of the meeting.
- After the meeting, compile a report based on what was discussed. Before finalizing the report, send it out to all participants to make sure they feel it accurately reflects what was said. Archive this information in your content management system.
- Share lessons learned with everyone. The key to building a culture that is accepting of this process, and truly investing in improving project performance, is to share what was learned and how improvements can be made going forward for future projects.
Document Archive
Project Documents to Archive
Use the Project Documents to Archive to capture all documents that should be archived with a link to their archival location.
Implementation
The documentation created as a part of the project life cycle should be stored in an accessible location for use as reference by project, support and operations resources, as well as future project resources leveraging the project information to support future projects.
Detailed Guidance
Historic project data is an important source of information to help improve future projects and needs to be stored in a central place. This important information will be leveraged by staff who will refer to the project archives for:
- Project outcomes created
- Information on similar projects
- Samples of completed templates
- Updating the project methodology with samples or new templates
- Assisting with project benefits realization planning and measurements
- Leverage for staff to learn about the project outcomes created.
- Refer to documentation when creating future enhancements.
- Leverage for similar projects.
- Samples of completed templates.
- Update the project methodology with samples or new templates.
- Leverage for assisting with project benefits realization planning and measurements.
- To assist when future changes take place.
- To help to remember why certain decisions were made.
All records, both electronic and hard copy should be stored according to organization record retention guidelines. Release the technical records to the personnel responsible for maintenance and operation of the system or program after it is deployed. If an electronic archival system is not used, a Project Documents To Archive should be created to document the location of all project records and materials.
Project Transfer
Transition Plan
The Transition Plan provides a brief overview fo the transition goals, any assumptions that the plan is based on, and any risks that have been identified that could severely limit your ability to complete the transition on schedule.
Transition Planning Checklist
The Transition Planning Checklist ensures that deliverables will be brought to full operational status, integrated into ongoing operations and maintained in a sustainable manner.
Project Closure Checklist
The Project Closure Checklist provides for group review and assessment of the project closure process to ensure the following of all closure steps.
Implementation
This is the process of bringing up to speed all of the stakeholders responsible for running the new project outcomes (system, tool, business process, etc.) upon completion of the project.
Detailed Guidance
Closure provides for the proper shutdown of all project activities and ensures a smooth handover from the project team and/or vendor to the customer (business owner) and the production or operations (support staff), as reflected in the figure below. An integral part of this process is making sure the support staff is set up for success. Use the Transition Plan, the Transition Planning Checklist, and Project Closure Checklist. Planning ahead to answer the following question will facilitate the transition:
- What issues have been identified with project deliverables during the quality assurance and testing process?
- What workarounds or methods are available to address known issues?
- How will the project be transitioned to the operational state?
- How will the project be supported by project staff during the transition period?
- What are the expectations of all resources associated with the project?
- What dependencies have been identified?
- How will support issues be escalated?

Project Hand off
Recognize and Celebrate Outstanding Project Work
Implementation
Celebrating the success of completing a project with positive reinforcement can be extremely rewarding for project teams. When a project is completed successfully, be certain to provide some kind of recognition to the team. If individuals are singled out for significant achievements, do not forget to recognize the entire team as well.
Detailed Guidance
Manage the Project Team
- Overview
- Benefits Realization
- IMPACT Metrics
Project Value
Upon completion of the project, the project benefits should be measured and tracked to determine if the value expected to be obtained was realized during the days, weeks, and months after the project was completed.
During the Value phase, a series of incremental post-implementation reviews, and then a final summary review and analysis, are conducted to ensure benefits derived met the expected business outcomes defined during Discovery and Initiation phases. The project must achieve a sufficient return on investment to be considered a success.
Goals:
- Analysis and preparation of lessons learned for future projects
- Identification of future enhancements and projects
- Enhancement of project management methodology
- Measurement of benefits and outcomes
Value of Measuring Value
The value phase is important because it determines if the value expected to be obtained was ever realized during the days, weeks, and months after the project was completed. It is time to assess the value of the project by asking and answering the following questions:
- Quality of the deliverables: Has the project deliverable (product, process, or service) been running/working well or have there been significant problems/issues?
- Benefits realization: Have the projected benefits been realized or are they falling short of expectations?
- Value realization: Did the project achieve its desired business outcomes in a way that made it worth doing?
- Project’s organizational IMPACT: Has the change been accepted by the users or is there resistance?
Benefits Realization
Benefits Register
The Benefit Register is used to define project value, set the baseline measurements for each benefit metric, measure and track benefits, report outcomes, determine gaps and monitor and report/mitigate/remediate gaps between goals and actual results.
Benefits Realization Report
(PowerPoint) The Benefits Realization Report is based on the project benefits tracked in the Benefits Register. Project benefits are measured and tracked over time to determine whether the value expected to be obtained during the days, weeks and months after the project was realized.
Benefits Realization Report
(Excel) The Benefits Realization Report is based on the project benefits tracked in the Benefits Register. Project benefits are measured and tracked over time to determine whether the value expected to be obtained during the days, weeks and months after the project was realized.
Implementation
Upon completion of the project, the project benefits should be measured and tracked to determine if the value expected to be obtained was realized during the days, weeks, and months after the project was completed.
The value phase is the closure of an iterative benefit realization process that started in the Initiation phase and continued throughout the project life-cycle.
Detailed Guidance

Benefits Measurements Process
Following proper project closure procedures ensures that all deliverables are accepted, the project can be supported properly, and appropriate lessons learned are documented for future use. The reason benefits are measured are to ensure that the project delivers the value originally set out in the business case.
A crucial part of determining project success is realized long after the project is completed, when the benefits the project was intended to create are actually realized. This process ensures that the benefits that were articulated as a part of the project business case and charter are tracked and reported to communicate project success.
Beyond tracking the benefits, a process can be leveraged to measure the accuracy of benefits estimates and anticipated outcomes achieved after the project is completed. This step is leveraged to determine with greater accuracy the effectiveness of the project scoping process and the delivery of the project outcomes.

Why Measure Benefits
The value realization review process is a multi-step process, as defined below.

Value Review Process
The Benefits Register is used throughout the project to monitor benefits realized. If during the analysis benefit gaps – “variances” – are identified, investigate the cause and initiate remedial action plans. If benefit metrics are tracked regularly, you will be able to identify and close gaps earlier.

Benefits Register, Value Phase
- Assess the quality of the deliverables: Has the project deliverable (product, process, or service) been running/working well or have there been significant problems/issues?
- Assess benefits realization: Have the projected benefits been realized or are they falling short of expectations?
- Assess the project’s organizational impact: Has the change been accepted by the users or is there resistance?
However, active benefits realization requires more than just measuring and reporting:
- Where possible, begin measurements while the project is on-going. It is easier to make adjustments that will affect benefits realization while the team is active and resources are dedicated to the project.
- If a metric cannot be gathered until the project is completed, use a related quality measure as a close indicator of how large of a gap exists between the goal measurement and the actual measurement.
- Intervene at the first sign of an issue and make a course correction. A project that is completed on-time and on-budget, but fails to deliver benefits is a failed project.
- If early tests reveal that the project is at risk of failing to realize benefits, the Project Manager must reassess the project plan and scope.
- Escalate to the Sponsor to decide whether benefit goals need to be adjusted, or whether scope, budget, or schedule must be expanded.
- Communicate project success. Communicating measured benefits, especially early on, can increase stakeholder buy-in and enthusiasm for the project and its outcomes, and decrease organizational resistance during implementation.
The Benefits Realization Report template is used to summarize the results of this process. For each project benefit, it provides a report on:
- Business Objective: the original business value to be achieved as defined in the Project Charter
- Benefit Type: type of benefit achieved (technical, HR, strategic, etc.)
- Benefit Description: brief description of the benefit achieved
- Outcome: actual business value of benefit achieved
- Impact: business impact of benefit achieved
- Impact Summary: summary of the total impact of all benefits achieved.
IMPACT Metrics
Implementation
Measuring the value and success of your project goes beyond Earned Value Management (EVM). If you ask anyone in the C-suite, they will tell you that Return on Investment (ROI) is more meaningful to them, than EVM, which talks about the performance of the project itself. IMPACT is about realizing outcomes that are greater than the investment. With IMPACT Metrics, we will show just how that is the case.
IMPACT Metrics
Detailed Guidance
When to identify Metrics?
Ideally, you should choose or identify your IMPACT metrics during the planning phase of your project. If you’re doing an Agile project, they can be identified during your Sprint Planning phase. Metrics can be modified throughout the project, based on sponsor needs or any relevant project changes. However, once you start measuring, you don’t want to keep making changes, if you want to see changes over time.
Reporting on IMPACT
Metrics are meaningful if you measure what matters. Ask your sponsors, business leaders, and any other stakeholders what matters to them – what will help them understand results, so they can make decisions. Here are some guidelines:
- Keep your list of IMPACT metrics short, but make sure that they are IMPACTful. Don’t measure everything!
- Ensure the metrics are simple and easy to follow
- Align metrics to project goals
- What capabilities are being provided? Is it a new capability, or are you making something more efficient?
- What decisions is the organization making, based on these metrics?
- Give time for the metrics to stick! You need to see measurement over time, before you can really know if you need to shift.
- Overview
- Key Insights
- Rescue Process
Project Recovery
There are times when good projects go bad. This section includes resources and guidance to support getting the project back on track!
Goals:
- Root cause analysis of why the project went off track
- Identify steps to get project back on track, or identify criteria for canceling the project
- Monitor progress to ensure project does not go off track again
Value of Planning for Project Recovery
Having a plan for recovering a project - whether it’s Agile, Waterfall, or some other implementation methodology - is important to show stakeholders that you have a process in place to help them when things inevitably happen. Providing guidance for project recovery gives everyone a place to start and once root cause has been identified, teams then know how to proceed. Whether you decide to move forward and deliver, or it's determined that you should cancel the project, you can show your stakeholders, team members, and leaders the assessment that took place that helped you arrive at your decision.
When does a project need to be “rescued?” When it is “off track” vs “troubled” vs “failing?” Before the question can be answered, the organization must have defined those action levels, at both the portfolio and project levels as appropriate. Once there is a mechanism to alert, a simple, straightforward process of assessment and remediation that clearly document the steps that will be taken, by who, and by when to get the project back to a successful status. The process, assessment, and plan need to be shared with the entire team to create a higher level of commitment and accountability. Below are some tips to help you get that project back on track and ensure that it stays that way!
- Manage expectations, not problems: Figure out the real bottom line. Don’t go down the who’s at fault or how do I hurry up and cover ourselves path, but actually look at what the real issue is and what can be done about it. What you are calling the problem may not be the whole story. You could fix the problem without actually addressing what caused it, thereby increasing the likelihood that it happens again. We actually need to be focused on outcomes. Outcomes are what people really need to know. Here’s an example: The problem is that you have a flat tire. The potential outcome is that you may not get to work on time. You could fix the flat tire (problem) and still not address the outcome you wanted to avoid – getting to work on time.
- Be forward-looking: Don’t focus all of your energy on where you are today (a.k.a. status). Remember to spend energy and the energy (attention) of your stakeholders by reminding them where you are going and how you plan to get there. This helps everyone keep their eye on the ball.
- Plan for planning: Make sure you allow time for all of the work you have to do as the project manager on the project. Sometimes I see plans with zero activities for the PM and wonder how they are going to stop time and make the work they have to do happen while they are fully booked on “other” tasks or meetings during the day. Don’t set yourself up for exhaustion…you won’t get time to recover between projects, I assure you!
- Use templates, checklists, and peers: Leverage a template or tool to help you think through all of the things that must be done on your project when you start a new one. That way, you are less likely to miss the gotchas that are coming down the road. Don’t forget to ask your peers to review your plans and give you feedback. You can avoid tons of pitfalls just by learning from the mistakes
- Think of yourself as an orchestrator: They are judged by the sound that is made, yet they make no noise. Don’t jump in and start playing the instruments when things are not going well. Just keep directing the orchestra. This allows you to keep the momentum forward without getting caught by the swirl of every issue that may arise.
- Write it down: Are the work products you are creating facilitating getting the work done or are you simply using them to document what happened? How many times did you update a project schedule to write down the work that happened after the fact?
- Know your stakeholders: The better you get to know your stakeholders, the better you will get at getting information out of them to prevent letting the project go downhill, and the faster you will be able how to address their WIIFM (what’s in it for me) to help you get the project back on track.
- Don’t expect people to read: People have very little time to read these days, unfortunately. Keep your communications clear and succinct then go find the people you need to talk to and actually talk to them. A five-minute conversation can save hours of miscommunication over email. Yes, write things down, but use one-page formats or simple bullet lists in an email to get your facts across in a very short time, then speak to people. They will tell you tons they won’t write down!!
- Manage to the right level of detail: If you manage at too high of a level, you are likely to miss details, risks, issues that are just waiting to jump out and grab you. This is not a license to micromanage the heck out of the project, just don’t assume that everyone has an entire sub-project under control without breaking that work down just a few layers.
- Always ask why: When you are presented with a problem, keep asking why until you get to the REAL concerns people have and the root cause of the problem. Seems simple, huh? How many times have you stopped at the first answer and not really understood how the problem occurred. If you want to prevent repeat problems, understand why they happened.
Key Insights
Project Charter
The Project Charter provides a structured outline to define a project’s purpose, stakeholders, goals, and resource needs. It includes sections for assumptions, benefits, risks, and constraints, helping to clarify the project scope and objectives. This template ensures all foundational details are captured for effective project planning and alignment with strategic goals.
Implementation
Whether you were asked to rescue a project in trouble, or you recognized the signs in your own project, you are now responsible for steering the project back on the right path. You may be working with a very eager team, or one that has been exhausted, trying to get back on track, or working endless hours to fix what might be broken.
As a project manager or scrum master (or any leader for that matter), you will need to transform your project team into a ‘rescue team.’ Prepare the team for what lies ahead – perhaps it’s long hours, or weekend work, or completing tasks in a way that hasn’t been done before. Regardless of what needs to be done, being honest, transparent, and helping the team understand what lies ahead will go a long way in getting your project back on track.
Detailed Guidance
Once you have your team established, you’re ready to enter ‘rescue mode!’ There are some additional things to consider as you pull your project back towards ‘green’ status:
1) Location and Communication – is it necessary for your team to be located together? In many cases people work remotely and location is no longer a barrier. If team members need access to each other all day, consider setting up a collaboration tool workspace, such as a Zoom call, or a chat where all relevant team members are present.
2) Begin with the End in Mind – start by revisiting your charter, project objectives, scope statement, and any other relevant documents that were pulled together throughout the planning phase. This will help anchor your team in the original goals and objectives and help you determine where you veered off course.
3) Deliverables – have the team review the deliverables that have been provided for what has worked thus far. Address what has not been completed, or what is incorrect.
4) Root Cause Analysis – once you identify where you went off track, figure out why. Perform the ‘5 Why’s’ to get down to the actual root cause of the problem.
5) Plan to Plan – Now that you know the root causes, give yourself, and your team, adequate time to come up with your recovery plan. Pay particular attention to risks and issues, as well as resources needed and any resource constraints that may arise. Get everyone together, and ensure that they participate in the planning process.
6) Plan to Communicate – Just as important as the recovery plan is the plan to communicate! Evaluate the projects previous communication plan and see if any changes need to be made. Additional communications to the sponsor and stakeholders may be needed until the project is back on track.
Recovery Process
Project Assessment and Remediation Plan
The Project Assessment and Remediation Plan can be simple, but should clearly document the steps that will be taken, by who, and by when to get the project back to Green status. The plan should be shared with the entire PPM team immediately upon development. Do not wait until the next meeting. This process creates a higher level of commitment and accountability.
Project Assessment Checklist
The Project Assessment Checklist allows you to audit existing projects and determine if there is additional support needed to help ensure project IMPACT is achieved.
Project Assessment Stakeholder Interviews
The Project Assessment Stakeholder Interviews are a key part of the project assessment process. This template captures each of your stakeholder’s understanding of the project and where it falls within the organization’s priorities, their expectations, their understanding of roles and responsibilities, and any project issues.
Project Assessment Documentation Review Checklist
The Project Assessment Documentation Review Checklist will aid in the review of project documentation for completeness as part of the project assessment process. This checklist includes artifacts for all project sizes and therefore not all artifacts types may be relevant to every project and assessment.
Project SWOT Analysis
The Project SWOT Analysis Template (Strength-Weakness-Opportunity-Threat) is used as part of the project assessment to determine where energy should be spent and to discover root causes. Once completed, the project’s SWOT matrix information can be used to develop the plan, strategy and to manage project risk.
Implementation
When does a project need to be “rescued?” When it is “off track” vs “troubled” vs “failing?” Before the question can be answered, the organization must have defined those action levels, at both the portfolio and project levels as appropriate. Once there is a mechanism to alert, a simple, straightforward process of assessment and remediation that clearly documents the steps that will be taken, by who, and by when to get the project back to a successful status. The process, assessment, and plan need to be shared with the entire team to create a higher level of commitment and accountability.
Detailed Guidance
Is it a communication issue for the project – you simply don’t know, or can’t tell at a glance what is going on with the project? Is it “over budget” or ‘behind schedule” and therefore ‘failing” and “not delivering value? 10%? 25%? How do you know? Have these thresholds been defined by the PPM for the organization or for the project? Basic success threshold or tolerance questions to be answered include:
- The project is being delivered within the estimated cost (plus or minus what tolerance?)
- The project is being delivered within its deadlines (plus or minus what tolerance?)
- All the major deliverables are being completed and accepted. (Some minor ones, or minor functionalities, might not be delivered.)
- The overall quality is acceptable. (Remember – it does not have to be perfect!)
- The project is meeting the defined Return on Investment (ROI) or defined/planned Benefit/Value
- The project is meeting the requirements of the Communication Plan
Ensure that the organization’s status reporting mechanism provides for answering these questions at a glance. Criteria should be defined (SEE PPM Playbook), reporting should be simple and information sharing straightforward (SEE Delivery Phase: Status Reports/Executive Dashboard). Use the Status Reports/Executive Dashboard template to provide information for each project and to provide reporting for the entire organizational portfolio of projects using the portfolio-level dashboard template. Leverage COLOR to tell the story of status – GREEN for on track, AMBER for slightly OFF TRACK, and RED for OFF TRACK/ REQUIRES IMMEDIATE MANAGEMENT ATTENTION.
Action should be initiated immediately upon project status change. Assessments and remediation plans can be simple, but should clearly document the steps that will be taken, by who, and by when to get the project back to Green status. The plan should be shared with the entire PPM team immediately upon development. Do not wait until the next meeting. This process creates a higher level of commitment and accountability.
Use the following templates for the Project Recovery process:
- The 2 stage Project Assessment & Remediation Plan
- Project Assessment Checklist
- Project Assessment Documentation Review Checklist
- Project Assessment Stakeholder Interviews
- Project SWOT (Strength-Weakness-Opportunity-Threat) Analysis
When a project is in AMBER status, perform the following steps:
- PM and Sponsor complete the Assessment
- Based on assessment results, a remediation plan developed with the goal of getting the project back to Green within 1 week
- The proposed plan is reviewed with the Portfolio Manager
- Plan shared broadly with the entire PPM team
- Initiate remediation
When the project is in RED status or proceeds from AMBER to RED:
- PM, Sponsor, and Portfolio Manager meet to develop a more detailed assessment of the project, using the Assessment Checklist
- Based on assessment results, PM and Sponsor develop a more thorough remediation plan
- Share the assessment results and proposed remediation plan with the entire PPM team immediately upon development
- PPM review assessment results and proposed remediation plan make remediation determination per organization PPM policy/criteria
- Implement PPM decision: initiate remediation vs close project
Business Documents
Business Documents
Business documents (business case and value management plan) are two key documents that are interdependent and initially developed prior to the project. The project manager is responsible for maintaining and iteratively updating business documents throughout the project.
Business Case
Business Case
The business case or similar document describes the necessary information from a business standpoint to determine whether or not the project is worth the required investment. It is commonly used for decision-making by managers or executives above the project level. Typically, the business need and the cost-benefit analysis are contained in the business case to justify and establish boundaries for the project, and such analysis is usually completed by a business analyst using various stakeholder inputs. The sponsor should agree to the scope and limitations of the business case.
Agreements
Agreements
A procurement agreement includes terms and conditions and may incorporate other items that the buyer specifies regarding what the seller is to perform or provide. It is the project management team’s responsibility to make certain that all agreements meet the specific needs of the project while adhering to organizational procurement policies. Depending upon the application area, an agreement can also be called an understanding, a contract, a subcontract, or a purchase order. Regardless of the document’s complexity, a contract is a mutually binding legal agreement that obligates the seller to provide the specified products, services, or results, and obligates the buyer to compensate the seller. A contract is a legal relationship subject to remedy in the courts.
Enterprise Environmental Factors
Enterprise Environmental Factors
Enterprise environmental factors refer to conditions, not under the control of the project team, that influence, constrain, or direct the project. Enterprise environmental factors are considered inputs to most planning processes, may enhance or constrain project management options, and may have a positive or negative influence on the outcome.
Organizational Process Assets
Organizational Process Assets
Organizational process assets are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization. They include any artifact, practice, or knowledge from any or all of the organizations involved in the project that can be used to perform or govern the project. The process assets also include the organization’s knowledge bases such as lessons learned and historical information. Organizational process assets may include completed schedules, risk data, and earned value data. Organizational process assets are inputs to most planning processes. Throughout the project, the project team members may update and add to the organizational assets as necessary. Organizational process assets may be grouped into two categories: (1) processes and procedures, and (2) corporate knowledge base.
Expert Judgment
Expert Judgment
Expert judgment is often used to assess the inputs used to develop the project charter. Expert judgment is applied to all technical and management details during this process. Such expertise is provided by any group or individual with specialized knowledge or training and is available from many sources.
Expert Judgment
Expert Judgment
Expert judgment is often used to assess the inputs used to develop the project charter. Expert judgment is applied to all technical and management details during this process. Such expertise is provided by any group or individual with specialized knowledge or training and is available from many sources.
Data Gathering
Data Gathering
Data gathering is a technique used to collect data and information from various sources for the purposes of later analyzing the data and assessing information.
Brainstorming
Brainstorming
Brainstorming is a common data-gathering technique that derives input from individuals and groups usually perceived as subject matter experts.
Focus Groups
Focus Groups
Focus groups bring together qualified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or result. A trained moderator guides the group through an interactive discussion, designed to be more conversational than a one-on-one interview.
Interviews
Interviews
An interview is a formal or informal approach to elicit information from stakeholders by talking to them directly. It is typically performed by asking prepared and spontaneous questions and recording the responses. Interviews are often conducted on an individual basis between an interviewer and an interviewee, but may involve multiple interviewers and/or multiple interviewees. Interviewing experienced project participants, sponsors and other executives, and subject matter experts can aid in identifying and defining the features and functions of the desired product deliverables. Interviews are also useful for obtaining confidential information.
Interpersonal and Team Skills
Interpersonal and Team Skills
Interpersonal and team skills are skills used to effectively lead and interact with team members and other stakeholders.
Conflict Management
Conflict Management
Sources of conflict include scarce resources, scheduling priorities, and personal work styles. Team ground rules, group norms, and solid project management practices, like communication planning and role definition, reduce the amount of conflict. Successful conflict management results in greater productivity and positive working relationships. When managed properly, differences of opinion can lead to increased creativity and better decision-making. If the differences become a negative factor, project team members are initially responsible for their resolution. If conflict escalates, the project manager should help facilitate a satisfactory resolution. Conflict should be addressed early and usually in private, using a direct, collaborative approach. If disruptive conflict continues, formal procedures may be used, including disciplinary actions.
Facilitation
Facilitation
Facilitation is the ability to effectively guide a group event to a successful decision, solution, or conclusion. A good facilitator ensures effective participation and inclusion.
Meeting Management
Meeting Management
Meeting management is the process of ensuring meetings achieve their intended objectives. Good meeting management does this effectively and efficiently through proper preparation, setting and managing expectations, keeping good records, and ensuring participant promptness and participation.
Meetings
Meetings
Research alone may not provide specific information to formulate a procurement strategy without additional information interchange meetings with potential bidders. By collaborating with potential bidders, the organization purchasing the material or service may benefit while the supplier can influence a mutually beneficial approach or product.
Project Charter
Project Charter
The project charter is the document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It documents the business needs, assumptions, constraints, the understanding of the customer’s needs and high-level requirements, and the new product, service, or result that it is intended to satisfy.
Assumption Log
Assumption Log
High-level strategic and operational assumptions and constraints are normally identified in the business case before the project is initiated and will flow into the project charter. Lower-level activity and task assumptions are generated throughout the project such as defining technical specifications, estimates, the schedule, risks, etc. The assumption log is used to record all assumptions and constraints throughout the project.
Outputs from Other Processes
Outputs from Other Processes
Outputs from other processes are exactly as stated, simply outputs from other processes.
Checklists
Checklists
A checklist is a list of items, actions, or points to be considered. It is often used as a reminder.
Project Management Plan
Project Management Plan
The project management plan integrates and consolidates all of the subsidiary management plans and baselines from the planning processes.
Project Documents
Project Documents
Project documents include, but are not limited to Assumptions log, Work performance reports, Earned value reports, Network diagrams, Baselines, and Other project information proven to be valuable in identifying risks.
Change Log
Change Log
A change log is used to document changes that occur during a project. These changes and their impact to the project in terms of time, cost, and risk, are communicated to the appropriate stakeholders. Rejected change requests are also captured in the change log.
Lessons Learned Register
Lessons Learned Register
The lessons learned register is created as an output of the Manage Project Knowledge process (4.4 Manage Project Knowledge) and is used as an input thereafter while being updated in many processes throughout the project. The lessons learned register can include the category and description of the situation. It may also include the impact, recommendations, and proposed actions associated with the situation. It may also record challenges, problems realized, risks and opportunities, or other content as appropriate.
Milestone List
Milestone List
A milestone is a significant point or event in a project. A milestone list is a list identifying all project milestones and indicates whether the milestone is mandatory, such as those required by contract, or optional, such as those based upon historical information. Milestones are similar to regular schedule activities, with the same structure and attributes, but they have zero duration because milestones represent a moment in time.
Project Communications
Project Communications
The Manage Communications process involves the activities that are required for information to be created, distributed, received, acknowledged, and understood. Project communications may include but are not limited to: performance reports, deliverables status, schedule progress, and cost incurred. Project communications can vary significantly and are influenced by factors such as, but not limited to, the urgency and impact of the message, its method of delivery, and level of confidentiality.
Project Schedule
Project Schedule
The outputs from a schedule model are schedule presentations. The project schedule is an output of a schedule model that presents linked activities with planned dates, durations, milestones, and resources. At a minimum, the project schedule includes a planned start date and planned finish date for each activity. If resource planning is done at an early stage, then the project schedule remains preliminary until resource assignments have been confirmed and scheduled start and finish dates are established. This process usually occurs no later than the completion of the project management plan. A target project schedule model may also be developed with a defined target start and target finish for each activity. The project schedule presentation may be presented in summary form, sometimes referred to as the master schedule or milestone schedule, or presented in detail.
Requirements Traceability Matrix
Requirements Traceability Matrix
The requirements traceability matrix is a grid that links product requirements from their origin to the deliverables that satisfy them. The implementation of a requirements traceability matrix helps ensure that each requirement adds business value by linking it to the business and project objectives. It provides a means to track requirements throughout the project life cycle, helping to ensure that requirements approved in the requirements documentation are delivered at the end of the project. Finally, it provides a structure for managing changes to the product scope.
Risk Register
Risk Register
The risk register is a document in which the results of risk analysis and risk response planning are recorded. It contains the outcomes of the other risk management processes as they are conducted, resulting in an increase in the level and type of information contained in the risk register over time. The preparation of the risk register begins in the Identify Risks process and then becomes available to other project management and risk management processes.
Risk Report
Risk Report
The risk report presents information on sources of overall project risk, together with summary information on identified individual project risks. The risk report is developed progressively throughout all of the Project Risk Management processes.
Approved Change Requests
Approved Change Requests
Approved change requests can include modifications to the terms and conditions of the contract, including the procurement statement of work, pricing, and descriptions of the products, services, or results to be provided. All procurement-related changes are formally documented in writing and approved before being implemented through the Control Procurements process.
Project Management Information System
Project Management Information System
Project management information system provides a standard set of tools for the project manager to capture, store, and distribute information to stakeholders about the project cost, schedule progress, and performance. It also allows the project manager to consolidate reports from several systems and facilitate report distribution to the project stakeholders. Examples of distribution formats may include table reporting, spreadsheet analysis, and presentations. Graphical capabilities can be used to create visual representations of project performance information.
Deliverables
Deliverables
A deliverable is any unique and verifiable product, result or capability to perform a service that is required to be produced to complete a process, phase, or project. Deliverables are typically tangible components completed to meet the project objectives and can include elements of the project management plan.
Work Performance Data
Work Performance Data
Work performance data are the raw observations and measurements identified during activities being performed to carry out the project work. Data are often viewed as the lowest level of detail from which information is derived by other processes. Data are gathered through work execution and passed to the controlling processes for further analysis.
Issue Log
Issue Log
Issues arise in the course of managing the project team. An issue log can be used to document and monitor who is responsible for resolving specific issues by a target date.
Project Documents Updates
Project Documents Updates
Project documents updates provide greater precision with respect to schedule, costs, and resource requirements to meet the defined project scope.
Activity List
Activity List
The activity list is a comprehensive list that includes all scheduled activities required on the project. The activity list also includes the activity identifier and a scope of work description for each activity in sufficient detail to ensure that project team members understand what work is required to be completed. Each activity should have a unique title that describes its place in the schedule, even if that activity title is displayed outside the context of the project schedule.
Requirements Documentation
Requirements Documentation
Requirements documentation, including user stories, describes how individual requirements meet the business need for the project. Requirements may start out at a high level and become progressively more detailed as more about the requirements is known. Before being baselined, requirements need to be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders. The format of a requirements document may range from a simple document listing all the requirements categorized by stakeholder and priority, to more elaborate forms containing an executive summary, detailed descriptions, and attachments.
Stakeholder Register
Stakeholder Register
A stakeholder register contains all details related to the identified stakeholders. The stakeholder register should be consulted and updated on a regular basis, as stakeholders may change or new ones identified throughout the life cycle of the project.
Stakeholder Analysis
Stakeholder Analysis
Stakeholder analysis refers to the range of tools and techniques used to identify and understand the needs and expectations of those who might have an interest in or influence on your project.
Project Team Assignments
Project Team Assignments
The project is staffed when appropriate people have been assigned to the team. The documentation of these assignments can include a project team directory, memos to team members, and names inserted into other parts of the project management plan, such as project organization charts and schedules.
Resource Breakdown Structure
Resource Breakdown Structure
The resource breakdown structure is a hierarchical representation of resources by category and type. Examples of resource categories include labor, material, equipment, and supplies. Resource types may include the skill level, grade level, or other information as appropriate to the project. The resource breakdown structure is useful for organizing and reporting project schedule data with resource utilization information.
Knowledge Management
Knowledge Management
The increasingly mobile and transitory workforce requires a more rigorous process of identifying knowledge throughout the project life cycle and transferring it to the target audience so that the knowledge is not lost. How will knowledge be managed in the project to foster a collaborative working environment?
Information Management
Information Management
Information management are tools and techniques that are used to create and connect people to information. They are effective for sharing simple, unambiguous, codified explicit knowledge. They include but are not limited to: methods for codifying explicit knowledge, lessons learned register, library services, information gathering, and project management information system (PMIS).
Active Listening
Active Listening
Active listening helps reduce misunderstandings and improves communication and knowledge sharing. Listening actively involves acknowledging, clarifying and confirming, understanding, and removing barriers that adversely affect comprehension.
Leadership
Leadership
Leadership is the knowledge, skills, and behaviors needed to guide, motivate, and direct a team, to help an organization achieve its business goals.
Networking
Networking
Networking is the formal and informal interaction with others in an organization, industry, or professional environment. It is a constructive way to understand political and interpersonal factors that will impact the effectiveness of various staffing management options. Human resource management benefits from successful networking by improving knowledge of and access to human resource assets such as strong competencies, specialized experience, and external partnership opportunities. Examples of human resources networking activities include proactive correspondence, luncheon meetings, informal conversations including meetings and events, trade conferences, and symposium. Networking can be a useful technique at the beginning of a project. It can also be an effective way to enhance project management professional development during the project and after the project ends.
Political Awareness
Political Awareness
Political awareness helps the project manager to plan communications based on the project environment as well as the organization’s political environment. It concerns the recognition of power relationships, both formal and informal, and also the willingness to operate within these structures. Political awareness assists the project manager in engaging stakeholders appropriately to maintain their support throughout the project.
Organizational Process Assets Updates
Organizational Process Assets Updates
The organizational process assets that may be updated include, but are not limited to, report formats and lessons learned documentation. This documentation may become part of the historical database for both this project and the performing organization and may include the causes of issues, reasons behind the corrective action chosen, and other types of lessons learned during the project.
Basis of Estimates
Basis of Estimates
The amount and type of additional details supporting the cost estimate vary by application area. Regardless of the level of detail, the supporting documentation should provide a clear and complete understanding of how the cost estimate was derived.
Cost Forecasts
Cost Forecasts
Cost forecasts are either a calculated EAC value or a bottom-up EAC value is documented and communicated to stakeholders.
Quality Reports
Quality Reports
Quality reports are project documents that include quality management issues, recommendations for corrective actions, and a summary of findings from quality control activities. Quality reports may include recommendations for process, project, and product improvements.
Schedule Forecasts
Schedule Forecasts
Schedule forecasts are estimates or predictions of conditions and events in the project’s future based on information and knowledge available at the time of the forecast. Forecasts are updated and reissued based on work performance information provided as the project is executed. The information is based on the project’s past performance and expected future performance, and includes earned value performance indicators that could impact the project in the future.
Work Performance Information
Work Performance Information
Work performance information is the performance data collected from various controlling processes, analyzed in context, and integrated based on relationships across areas. Thus work performance data has been transformed into work performance information. Data in itself cannot be used in the decision-making process as it has only out-of-context meaning. Work performance information, however, is correlated and contextualized, and provides a sound foundation for project decisions.
Data Analysis
Data Analysis
Data analysis is techniques used to organize, assess, and evaluate data and information.
Alternatives Analysis
Alternatives Analysis
Many schedule activities have alternative methods of accomplishment. They include using various levels of resource capability or skills, different size or type of machines, different tools (hand versus automated), and make-rent-or-buy decisions regarding the resource.
Cost-Benefit Analysis
Cost-Benefit Analysis
The primary benefits of meeting quality requirements include less rework, higher productivity, lower costs, increased stakeholder satisfaction, and increased profitability. A cost-benefit analysis for each quality activity compares the cost of the quality step to the expected benefit.
Earned Value Analysis
Earned Value Analysis
Earned value analysis provides an integrated perspective on scope, schedule, and cost performance. The performance measurement baseline is compared to actual results to determine if a change, corrective action, or preventive action is necessary. Schedule performance measurements such as schedule variance (SV) and schedule performance index (SPI) are used to assess the magnitude of variation to the original schedule baseline.
Root Cause Analysis
Root Cause Analysis
Root cause analysis is an analytical technique used to determine the basic underlying reason that causes a variance, defect, or risk. A root cause may underlie more than one variance, defect, or risk.
Trend Analysis
Trend Analysis
Trend analysis is an analytical technique that uses mathematical models to forecast future outcomes based on historical results.
Variance Analysis
Variance Analysis
Variance analysis is a technique for determining the cause and degree of difference between the baseline and actual performance. Project performance measurements are used to assess the magnitude of variation from the original scope baseline. Important aspects of project scope control include determining the cause and degree of variance relative to the scope baseline and deciding whether corrective or preventive action is required.
Decision Making
Decision Making
Decision making techniques are used to select a course of action from different alternatives. There are two decision-making tools and techniques.
Voting
Voting
Voting is a collective decision-making technique and an assessment process having multiple alternatives with an expected outcome in the form of future actions. These techniques can be used to generate, classify, and prioritize product requirements. Can include making decisions based on unanimity, majority, or plurality.
Work Performance Reports
Work Performance Reports
Work performance reports are the physical or electronic representation of work performance information compiled in project documents, intended to generate decisions, actions, or awareness. Project information may be communicated verbally from person to person. However, in order to record, store, and sometimes distribute work performance information, a physical or electronic representation in the form of project documents is required. Work performance reports are a subset of project documents, which are intended to create awareness and generate decisions or actions. Specific work performance metrics may be defined at the start of the project and included in the normal work performance reports provided to key stakeholders.
Change Management Plan
Change Management Plan
The change management plan is a component of the project management plan that establishes the change control board, documents the extent of it’s authority, and describes how the change control system will be implemented.
Scope Baseline
Scope Baseline
The scope baseline is the approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison. It is a component of the project management plan.
Schedule Baseline
Schedule Baseline
A schedule baseline is the approved version of a schedule model that can be changed only through formal change control procedures and is used as a basis for comparison to actual results. It is accepted and approved by the appropriate stakeholders as the schedule baseline with baseline start dates and baseline finish dates. During monitoring and controlling, the approved baseline dates are compared to the actual start and finish dates to determine whether variances have occurred. The schedule baseline is a component of the project management plan.
n.
Cost Baseline
Cost Baseline
The cost baseline is the approved version of the time-phased project budget, excluding any management reserves, which can only be changed through formal change control procedures and is used as a basis for comparison to actual results. It is developed as a summation of the approved budgets for the different schedule activities.
Change Requests
Change Requests
The completed deliverables that have not been formally accepted are documented, along with the reasons for the nonacceptance of those deliverables. Those deliverables may require a change request for defect repair. The change requests are processed for review and disposition through the Perform Integrated Change Control process.
Change Control Tools
Change Control Tools
In order to facilitate configuration and change management, manual or automated tools may be used. Tool selection should be based on the needs of the project stakeholders including organizational and environmental considerations and/or constraints. Tools are used to manage the change requests and the resulting decisions. Additional considerations should be made for communication to assist the CCB members in their duties as well as distribute the decisions to the appropriate stakeholders.
Autocratic Decision Making
Autocratic Decision Making
In this decision-making technique, one individual takes the responsibility for making the decision for the entire group.
Multicriteria Decision Analysis
Multicriteria Decision Analysis
Selection criteria are often used as a part of acquiring the project team. By use of a multicriteria decision analysis tool, criteria are developed and used to rate or score potential team members. The criteria are weighted according to the relative importance of the needs within the team.p.
Quality Control Measurements
Quality Control Measurements
Quality control measurements are the results of control quality activities. They are used to analyze and evaluate the quality of the processes of the project against the standards of the performing organization or the requirements specified. Quality control measurements can also compare the processes used to create the measurements, and validate actual measurements to determine their level of correctness.
Accepted Deliverables
Accepted Deliverables
Deliverables that meet the acceptance criteria are formally signed off and approved by the customer or sponsor. Formal documentation received from the customer or sponsor acknowledging formal stakeholder acceptance of the project’s deliverables is forwarded to the Close Project or Phase process.
Accepted Deliverables
Accepted Deliverables
Deliverables that meet the acceptance criteria are formally signed off and approved by the customer or sponsor. Formal documentation received from the customer or sponsor acknowledging formal stakeholder acceptance of the project’s deliverables is forwarded to the Close Project or Phase process.
Procurement Documentation
Procurement Documentation
Procurement documents are used to solicit proposals from prospective sellers. Terms such as bid, tender, or quotation are generally used when the seller selection decision will be based on price (as when buying commercial or standard items), while a term such as proposal is generally used when other considerations, such as technical capability or technical approach are paramount. Common terms are in use for different types of procurement documents and may include request for information (RFI), invitation for bid (IFB), request for proposal (RFP), request for quotation (RFQ), tender notice, invitation for negotiation, and invitation for seller’s initial response. Specific procurement terminology used may vary by industry and location of the procurement.
Document Analysis
Document Analysis
Document analysis is used to elicit requirements by analyzing existing documentation and identifying relevant requirements. Examples of documents that may be analyzed include, but are not limited to: business plans, marketing literature, agreements, requests for proposal, current process flows, logical data models, business rules repositories, application software documentation, business process or interface documentation, use cases, other requirements documentation, problem/issue logs, policies, procedures, and regulatory documentation such as laws, codes, or ordinances, etc.
Regression Analysis
Regression Analysis
Regression analysis is an analytical technique where a series of input variables are examined in relation to their corresponding output results in order to develop a mathematical or statistical relationship.
Final Product, Service or Result Transition
Final Product, Service or Result Transition
This output refers to the transition of the final product, service, or result that the project was authorized to produce (or in the case of phase closure, the intermediate product, service, or result of that phase).
Final Report
Final Report
The final report provides a summary of the project performance. It can include information such as: summary level description of the project or phase, scope objectives, quality objectives, cost objectives, a summary of the validation information for the final product, service, or result, schedule objectives, a summary of how the final product, service, or result achieved the business needs identified in the business plan, and a summary of any risks or issues encountered on the project and how they were addressed.
Quality Management Plan
Quality Management Plan
The quality management plan is a component of the project management plan that describes how the organization’s quality policies will be implemented. It describes how the project management team plans to meet the quality requirements set for the project. The quality management plan may be formal or informal, detailed, or broadly framed. The style and detail of the quality management plan are determined by the requirements of the project. The quality management plan should be reviewed early in the project to ensure that decisions are based on accurate information. The benefits of this review can include a sharper focus on the project’s value proposition and reductions in costs and in the frequency of schedule overruns that were caused by rework.
Project Life Cycle Description
Project Life Cycle Description
The project life cycle determines the series of phases that a project passes through from its inception to the end of the project.
Development Approach
Development Approach
Development approach is the method used to create and evolve the product, service, or result during the project life cycle, such as predictive, iterative, incremental, agile, or a hybrid method.
Scope Management Plan
Scope Management Plan
The scope management plan is a component of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and verified. The scope management plan is a major input into the Develop Project Management Plan process, and the other scope management processes.
Requirements Management Plan
Requirements Management Plan
The requirements management plan is a component of the project management plan that describes how requirements will be analyzed, documented, and managed. The project manager chooses the most effective relationship for the project and documents this approach in the requirements management plan. Many of the requirements management plan components are based on that relationship.
Requirements Management Plan
Requirements Management Plan
The requirements management plan is a component of the project management plan that describes how requirements will be analyzed, documented, and managed. The project manager chooses the most effective relationship for the project and documents this approach in the requirements management plan. Many of the requirements management plan components are based on that relationship.
Questionnaires and Surveys
Questionnaires and Surveys
Questionnaires and surveys are written sets of questions designed to quickly accumulate information from a large number of respondents. Questionnaires and/or surveys are most appropriate with varied audiences, when a quick turnaround is needed, when respondents are geographically dispersed, and where statistical analysis is appropriate.
Benchmarking
Benchmarking
Benchmarking involves comparing actual or planned practices, such as processes and operations, to those of comparable organizations to identify best practices, generate ideas for improvement, and provide a basis for measuring performance. The organizations compared during benchmarking can be internal or external.
Data Representation
Data Representation
Data representation is used to show graphic representations or other methods used to convey data and information. There are 15 data representation tools and techniques.
Affinity Diagrams
Affinity Diagrams
Affinity diagrams allow large numbers of ideas to be classified into groups for review and analysis.
Mind Mapping
Mind Mapping
Mind mapping is a technique used to consolidate ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas.
Nominal Group Technique
Nominal Group Technique
Nominal group technique enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization.
Observation and Conversation
Observation and Conversation
Observation and conversation are used to stay in touch with the work and attitudes of project team members. The project management team monitors progress toward project deliverables, accomplishments that are a source of pride for team members, and interpersonal issues.
Context Diagrams
Context Diagrams
The context diagram is an example of a scope model. Context diagrams visually depict the product scope by showing a business system (process, equipment, computer system, etc.), and how people and other systems (actors) interact with it. Context diagrams show inputs to the business system, the actor(s) providing the input, the outputs from the business system, and the actor(s) receiving the output.
Prototypes
Prototypes
Prototyping is a method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it. Since a prototype is tangible, it allows stakeholders to experiment with a model of the final product rather than being limited to discussing abstract representations of their requirements. Prototypes support the concept of progressive elaboration in iterative cycles of mock-up creation, user experimentation, feedback generation, and prototype revision. When enough feedback cycles have been performed, the requirements obtained from the prototype are sufficiently complete to move to a design or build phase. Storyboards are used in a variety of industries, such as film, advertising, instructional design, and on agile and other software development projects. In software development, storyboards use mock-ups to show navigation paths through web pages, screens, or other user interfaces.
Alternatives Generation
Alternatives Generation
Alternatives generation is a technique used to develop as many potential options as possible in order to identify different approaches to execute and perform the work of the project. A variety of general management techniques can be used, such as brainstorming, lateral thinking, analysis of alternatives, etc.
Product Analysis
Product Analysis
For projects that have a product as a deliverable, as opposed to a service or result, product analysis can be an effective tool. Each application area has one or more generally accepted methods for translating high-level product descriptions into tangible deliverables. Product analysis includes techniques such as product breakdown, systems analysis, requirements analysis, systems engineering, value engineering, and value analysis.
Project Scope Statement
Project Scope Statement
The project scope statement is the description of the project scope, major deliverables, assumptions, and constraints. The project scope statement documents the entire scope, including project and product scope. It describes, in detail, the project’s deliverables and the work required to create those deliverables. It also provides a common understanding of the project scope among project stakeholders. It may contain explicit scope exclusions that can assist in managing stakeholder expectations. It enables the project team to perform more detailed planning, guides the project team’s work during execution, and provides the baseline for evaluating whether requests for changes or additional work are contained within or outside the project’s boundaries.
Decomposition
Decomposition
Decomposition is a technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts. The work package is the work defined at the lowest level of the WBS for which cost and duration can be estimated and managed. The level of decomposition is often guided by the degree of control needed to effectively manage the project. The level of detail for work packages will vary with the size and complexity of the project.
Verified Deliverables
Verified Deliverables
A goal of the Control Quality process is to determine the correctness of deliverables. The results of performing the Control Quality process are verified deliverables. Verified deliverables are an input to Validate Scope for formalized acceptance.
Inspection
Inspection
Inspection includes activities such as measuring, examining, and validating to determine whether work and deliverables meet requirements and product acceptance criteria. Inspections are sometimes called reviews, product reviews, audits, and walk-throughs. In some application areas, these different terms have unique and specific meanings.
Configuration Management Plan
Configuration Management Plan
The configuration management plan is a component of the project management plan that describes how to identify and account for project artifacts under configuration control, and how to record and report changes to them.
Performance Measurement Baseline
Performance Measurement Baseline
The performance measurement baseline (PMB) includes integrated scope, schedule, and cost baselines that are used for comparison to manage, measure, and control project execution.
Schedule Management Plan
Schedule Management Plan
The schedule management plan is a component of the project management plan that establishes the criteria and activities for developing, monitoring, and controlling the schedule. The schedule management plan may be formal or informal, highly detailed or broadly framed, based upon the needs of the project, and includes appropriate control thresholds.
Rolling Wave Planning
Rolling Wave Planning
Rolling wave planning is an iterative planning technique in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level. It is a form of progressive elaboration. Therefore, work can exist at various levels of detail depending on where it is in the project life cycle. During early strategic planning, when information is less defined, work packages may be decomposed to the known level of detail. As more is known about the upcoming events in the near term, work packages can be decomposed into activities.
Activity Attributes
Activity Attributes
Activities, distinct from milestones, have durations, during which the work of that activity is performed, and may have resources and costs associated with that work. Activity attributes extend the description of the activity by identifying the multiple components associated with each activity. The components for each activity evolve over time. During the initial stages of the project, they include the activity identifier (ID), WBS ID, and activity label or name, and when completed, may include activity codes, activity description, predecessor activities, successor activities, logical relationships, leads and lags (Section 6.3.2.3), resource requirements, imposed dates, constraints, and assumptions. Activity attributes can be used to identify the person responsible for executing the work, geographic area, or place where the work has to be performed, the project calendar the activity is assigned to, and activity type such as level of effort (often abbreviated as LOE), discrete effort, and apportioned effort. Activity attributes are used for schedule development and for selecting, ordering, and sorting the planned schedule activities in various ways within reports. The number of attributes varies by application area.
Project Management Plan Updates
Project Management Plan Updates
The project management plan provides information on project baselines, communications management, and stakeholder engagement. Each of these areas may require updates based upon the current performance of the project against the performance measurement baseline (PMB). The performance measurement baseline is an approved plan for the project work to which the project execution is compared, and deviations are measured for management control. The performance measurement baseline typically integrates scope, schedule, and cost parameters of a project, but may also include technical and quality parameters.
Precedence Diagramming Method (PDM)
Precedence Diagramming Method (PDM)
The precedence diagramming method (PDM) is a technique used for constructing a schedule model in which activities are represented by nodes and are graphically linked by one or more logical relationships to show the sequence in which the activities are to be performed. Activity-on-node (AON) is one method of representing a precedence diagram. This is the method used by most project management software packages. PDM includes four types of dependencies or logical relationships. A predecessor activity is an activity that logically comes before a dependent activity in a schedule. A successor activity is a dependent activity that logically comes after another activity in a schedule.
Dependency Determination and Integration
Dependency Determination and Integration
Dependencies may be characterized by the following attributes: mandatory or discretionary, internal or external. Dependency has four attributes, but two can be applicable at the same time in the following ways: mandatory external dependencies, mandatory internal dependencies, discretionary external dependencies, or discretionary internal dependencies.
Leads and Lags
Leads and Lags
Leads and lags are refinements applied during network analysis to develop a viable schedule by adjusting the start time of the successor activities. Leads are used in limited circumstances to advance a successor activity with respect to the predecessor activity, and lags are used in limited circumstances where processes require a set period of time to elapse between the predecessors and successors without work or resource impact.
Project Schedule Network Diagrams
Project Schedule Network Diagrams
A project schedule network diagram is a graphical representation of the logical relationships, also referred to as dependencies, among the project schedule activities. Figure 6-11 illustrates a project schedule network diagram. A project schedule network diagram is produced manually or by using project management software. It can include full project details, or have one or more summary activities. A summary narrative can accompany the diagram and describe the basic approach used to sequence the activities. Any unusual activity sequences within the network should be fully described within the narrative.
Resource Calendars
Resource Calendars
A resource calendar is a calendar that identifies the working days and shifts on which each specific resource is available. Information on which resources (such as human resources, equipment, and material) are potentially available during a planned activity period, is used for estimating resource utilization. Resource calendars specify when and how long identified project resources will be available during the project. This information may be at the activity or project level. This knowledge includes consideration of attributes such as resource experience and/or skill level, as well as various geographical locations from which the resources originate and when they may be available.
Resource Requirements
Resource Requirements
Resource requirements are the types and quantities of resources required for each activity in a work package.
Analogous Estimating
Analogous Estimating
Analogous estimating is a technique for estimating the duration or cost of an activity or a project using historical data from a similar activity or project. Analogous estimating uses parameters from a previous, similar project, such as duration, budget, size, weight, and complexity, as the basis for estimating the same parameter or measure for a future project. When estimating durations, this technique relies on the actual duration of previous, similar projects as the basis for estimating the duration of the current project. It is a gross value estimating approach sometimes adjusted for known differences in project complexity. Analogous duration estimating is frequently used to estimate project duration when there is limited amount of detailed information about the project.
Parametric Estimating
Parametric Estimating
Parametric estimating is an estimating technique in which an algorithm is used to calculate cost or duration based on historical data and project parameters. Parametric estimating uses a statistical relationship between historical data and other variables (e.g., square footage in construction) to calculate an estimate for activity parameters, such as cost, budget, and duration. Activity durations can be quantitatively determined by multiplying the quantity of work to be performed by labor hours per unit of work. This technique can produce higher levels of accuracy depending upon the sophistication and underlying data built into the model. Parametric time estimates can be applied to a total project or to segments of a project, in conjunction with other estimating methods.
Three-Point Estimating
Three-Point Estimating
The accuracy of single-point activity duration estimates may be improved by considering estimation uncertainty and risk. This concept originated with the program evaluation and review technique (PERT). PERT uses three estimates to define an approximate range for an activity’s duration. Duration estimates based on three points with an assumed distribution provide an expected duration and clarify the range of uncertainty around the expected duration.
Bottom-Up Estimating
Bottom-Up Estimating
Bottom-up estimating is a method of estimating project duration or cost by aggregating the estimates of the lower-level components of the WBS. When an activity cannot be estimated with a reasonable degree of confidence, the work within the activity is decomposed into more detail. The resource needs are estimated. These estimates are then aggregated into a total quantity for each of the activity’s resources. Activities may or may not have dependencies between them that can affect the application and use of resources. If there are dependencies, this pattern of resource usage is reflected and documented in the estimated requirements of the activity.
Reserve Analysis
Reserve Analysis
Duration estimates may include contingency reserves, sometimes referred to as time reserves or buffers, into the project schedule to account for schedule uncertainty. Contingency reserves are the estimated duration within the schedule baseline, which is allocated for identified risks that are accepted and for which contingent or mitigation responses are developed. Contingency reserves are associated with the known-unknowns, which may be estimated to account for this unknown amount of rework. The contingency reserve may be a percentage of the estimated activity duration, a fixed number of work periods, or may be developed by using quantitative analysis methods such as Monte Carlo simulation. Contingency reserves may be separated from the individual activities and aggregated into buffers. As more precise information about the project becomes available, the contingency reserve may be used, reduced, or eliminated. Contingency should be clearly identified in schedule documentation. Estimates may also be produced for the amount of management reserve of time for the project. Management reserves are a specified amount of the project duration withheld for management control purposes and are reserved for unforeseen work that is within scope of the project. Management reserves are intended to address the unknown-unknowns that can affect a project. Management reserve is not included in the schedule baseline, but it is part of the overall project duration requirements. Depending on contract terms, use of management reserves may require a change to the schedule baseline.
Duration Estimates
Duration Estimates
Duration estimates provide quantitative assessments of project durations, ideally expressed as a range, indicating the degree of risk, where a structured review of the documents may indicate that the current estimate is insufficient and poses a risk to the project. Duration estimates provide the starting point from which schedule variability is evaluated.
Schedule Network Analysis
Schedule Network Analysis
Schedule network analysis is a technique that generates the project schedule model. It employs various analytical techniques, such as critical path method, critical chain method, what-if analysis, and resource optimization techniques to calculate the early and late start and finish dates for the uncompleted portions of project activities. Some network paths may have points of path convergence or path divergence that can be identified and used in schedule compression analysis or other analyses.
Critical Path Method
Critical Path Method
The critical path method is a method used to estimate the minimum project duration and determine the amount of scheduling flexibility on the logical network paths within the schedule model. This schedule network analysis technique calculates the early start, early finish, late start, and late finish dates for all activities without regard for any resource limitations by performing a forward and backward pass analysis through the schedule network. The critical path is the sequence of activities that represents the longest path through a project, which determines the shortest possible project duration. The resulting early and late start and finish dates are not necessarily the project schedule, rather they indicate the time periods within which activity could be executed, using parameters entered in the schedule model for activity durations, logical relationships, leads, lags and other known constraints. The critical path method is used to calculate the amount of scheduling flexibility on the logical network paths within the schedule model.
Resource Optimization
Resource Optimization
Resource optimization techniques can be used to adjust the schedule model due to demand and supply of resources.
What-If Scenario Analysis
What-If Scenario Analysis
What-if scenario analysis is the process of evaluating scenarios in order to predict their effect on project objectives.
Simulation
Simulation
Simulation is an analytical technique that models the combined effect of uncertainties to evaluate their potential impact on objectives.
Schedule Compression
Schedule Compression
Schedule compression techniques are used to shorten the schedule duration without reducing the project scope, in order to meet schedule constraints, imposed dates, or other schedule objectives.
Agile Release Planning
Agile Release Planning
Agile release planning provides a high-level summary time-line of the release schedule (typically 3 to 6 months) based on the product roadmap and the product vision for the product’s evolution. It also determines the number of iterations or sprints in the release, and allows the product owner and team to decide how much needs to be developed and how long it will take to have a releasable product based on business goals, dependencies, and impediments.
Schedule Data
Schedule Data
The schedule data for the project schedule model is the collection of information for describing and controlling the schedule. The schedule data includes at least the schedule milestones, schedule activities, activity attributes, and documentation of all identified assumptions and constraints. The amount of additional data varies by application area.
Project Calendars
Project Calendars
A project calendar identifies working days and shifts that are available for scheduled activities. It distinguishes time periods in days or parts of days that are available to complete scheduled activities from time periods that are not available. A schedule model may require more than one project calendar to allow for different work periods for some activities to calculate the project schedule. The project calendars may be updated.
Iteration Burndown Chart
Iteration Burndown Chart
This chart tracks the work that remains to be completed in the iteration backlog. It is used to analyze the variance with respect to an ideal burndown based on the work committed from iteration planning. A forecast trend line can be used to predict the likely variance at iteration completion and take appropriate actions during the course of the iteration. A diagonal line representing the ideal burndown and daily actual remaining work is then plotted. A trend line is then calculated to forecast completion based on remaining work.
Performance Reviews
Performance Reviews
Performance reviews measure, compare, and analyze schedule performance such as actual start and finish dates, percent complete, and remaining duration for work in progress. Performance reviews compare cost performance over time, schedule activities or work packages overrunning and under-running the budget, and estimated funds needed to complete work in progress.
Cost Management Plan
Cost Management Plan
The cost management plan is a component of the project management plan and describes how the project costs will be planned, structured, and controlled. The cost management processes and their associated tools and techniques are documented in the cost management plan.
Cost of Quality
Cost of Quality
Cost of quality includes all costs incurred over the life of the product by investment in preventing non-conformance to requirements, appraising the product or service for conformance to requirements, and failing to meet requirements (rework). Failure costs are often categorized into internal (found by the project) and external (found by the customer). Failure costs are also called cost of poor quality.
Cost Estimates
Cost Estimates
Cost estimates are quantitative assessments of the likely costs for resources required to complete the activity. They include the identification and consideration of costing alternatives to initiate and complete the project.
Resource Management Plan
Resource Management Plan
The resource management plan, a part of the project management plan, provides guidance on how project resources should be defined, obtained, assigned, managed, and eventually released. The resource management plan and any subsequent revisions are also inputs into the Develop Project Management Plan process.
Benefits Management Plan
Benefits Management Plan
The benefits management plan is the documented explanation defining the processes for creating, maximizing, and sustaining the benefits provided by a project.
Cost Aggregation
Cost Aggregation
Cost estimates are aggregated by work packages in accordance with the WBS. The work package cost estimates are then aggregated for the higher component levels of the WBS (such as control accounts) and ultimately for the entire project.
Historical Information Review
Historical Information Review
Reviewing historical information can assist in developing parametric estimates or analogous estimates. Historical information may include project characteristics (parameters) to develop mathematical models to predict total project costs.
Funding Limit Reconciliation
Funding Limit Reconciliation
The expenditure of funds should be reconciled with any funding limits on the commitment of funds for the project. A variance between the funding limits and the planned expenditures will sometimes necessitate the rescheduling of work to level out the rate of expenditures. This is accomplished by placing imposed date constraints for work into the project schedule.
Financing
Financing
Financing entails acquiring funding for projects. It is common for long-term infrastructure, industrial, and public services projects to seek external sources of funds. If a project is funded externally, the funding entity may have certain requirements that are required to be met.
Project Funding Requirements
Project Funding Requirements
Total funding requirements and periodic funding requirements (e.g., quarterly, annually) are derived from the cost baseline. The cost baseline will include projected expenditures plus anticipated liabilities. Funding often occurs in incremental amounts that are not continuous. The total funds required are those included in the cost baseline, plus management reserves, if any.
To-Complete Performance Index
To-Complete Performance Index
The to-complete performance index (TCPI) is a measure of the cost performance that is required to be achieved with the remaining resources in order to meet a specified management goal, expressed as the ratio of the cost to finish the outstanding work to the remaining budget. TCPI is the calculated cost performance index that is achieved on the remaining work to meet a specified management goal, such as the BAC or the EAC. If it becomes obvious that the BAC is no longer viable, the project manager should consider the forecasted EAC. Once approved, the EAC may replace the BAC in the TCPI calculation. The equation for the TCPI based on the BAC: (BAC-EV) / (BAC-AC).
Risk Management Plan
Risk Management Plan
The risk management plan is a component of the project management plan and describes how risk management activities will be structured and performed. Key elements of the risk management plan that contribute to the Identify Risks process are the assignments of roles and responsibilities, provision for risk management activities in the budget and schedule, and categories of risk, which are sometimes expressed as a risk breakdown structure.
Stakeholder Engagement Plan
Stakeholder Engagement Plan
The stakeholder engagement plan is a component of the project management plan and identifies the management strategies required to effectively engage stakeholders. The stakeholder engagement plan can be formal or informal, highly detailed or broadly framed, based on the needs of the project. This plan is used to determine the level of interactions of various stakeholders and together with other documents helps define a strategy for identifying and managing stakeholders throughout the project life cycle.
Flowcharts
Flowcharts
Flowcharts are also referred to as process maps because they display the sequence of steps and the branching possibilities that exist for a process that transforms one or more inputs into one or more outputs. Flowcharts show the activities, decision points, branching loops, parallel paths, and the overall order of processing by mapping the operational details of procedures that exist within a horizontal value chain. Flowcharts may prove useful in understanding and estimating the cost of quality for a process. Information is obtained by using the workflow branching logic and associated relative frequencies to estimate the expected monetary value for the conformance and non-conformance work required to deliver the expected conforming output. When flowcharts are used to represent the steps in a process, they are sometimes called process flows or process flow diagrams and they can be used for process improvement as well as identifying where quality defects can occur or where to incorporate quality checks.
Logical Data Model
Logical Data Model
Logical data models are a visual representation of an organization’s data, described in business language and independent of any specific technology. The logical data model can be used to identify where data integrity or other quality issues can arise.
Matrix Diagrams
Matrix Diagrams
A quality management and control tool used to perform data analysis within the organizational structure created in the matrix. The matrix diagram seeks to show the strengths of relationships between factors, causes, and objectives that exist between the rows and columns that form the matrix.
Test and Inspection Planning
Test and Inspection Planning
During the planning phase, the project manager and the project team determine how to test or inspect the product, deliverable, or service to meet the stakeholders’ needs and expectations, as well as how to meet the goal for the product’s performance and reliability. The tests and inspections are industry dependent and can include, for example, alpha and beta tests in software projects, strength tests in construction projects, inspection in manufacturing, and field tests and non-destructive tests in engineering.
Quality Metrics
Quality Metrics
A quality metric specifically describes a project or product attribute and how the control quality process will measure it. A measurement is an actual value. The tolerance defines the allowable variations to the metric. For example, if the quality objective is to stay within the approved budget by ± 10%, the specific quality metric is used to measure the cost of every deliverable and determine the percent variance from the approved budget for that deliverable. Quality metrics are used in the perform quality assurance and control quality processes. Some examples of quality metrics include on-time performance, cost control, defect frequency, failure rate, availability, reliability, and test coverage.
Cause and Effect Diagrams
Cause and Effect Diagrams
Cause-and-effect diagrams are also known as fishbone diagrams, why-why diagrams, or Ishikawa diagrams. This type of diagram breaks down the causes of the problem statement identified into discrete branches, helping to identify the main or root cause of the problem.
Histograms
Histograms
Histograms show a graphical representation of numerical data. Histograms can show the number of defects per deliverable, a ranking of the cause of defects, the number of times each process is non-compliant, or other representations of project or product defects.
Scatter Diagrams
Scatter Diagrams
A scatter diagram is a graph that shows the relationship between two variables. Scatter diagrams can demonstrate a relationship between any element of a process, environment, or activity on one axis and a quality defect on the other axis.
Audits
Audits
An audit is a structured, independent process used to determine if project activities comply with organizational and project policies, processes, and procedures.
Design for X
Design for X
Design for X (DfX) is a set of technical guidelines that may be applied during the design of a product for the optimization of a specific aspect of the design. DfX can control or even improve the product’s final characteristics. The X in DfX can be different aspects of product development, such as reliability, deployment, assembly, manufacturing, cost, service, usability, safety, and quality. Using DfX may result in cost reduction, quality improvement, better performance, and customer satisfaction.
Problem Solving
Problem Solving
Problem solving is finding solutions for issues or challenges. It can include gathering additional information, critical thinking, creative, quantitative and/or logical approaches.
Quality Improvement Methods
Quality Improvement Methods
Quality improvements can occur based on findings and recommendations from quality control processes, the findings of the quality audits, or problem solving in the Manage Quality process. Plan-do-check-act and Six Sigma are two of the most common quality improvement tools used to analyze and evaluate opportunities for improvement.
Test and Evaluation Documents
Test and Evaluation Documents
Test and evaluation documents are project documents that describe the activities used to determine if the product meets the quality objectives stated in the quality management plan.
Check Sheets
Check Sheets
Check sheets are also known as tally sheets and are used to organize facts in a manner that will facilitate the effective collection of useful data about a potential quality problem. They are especially useful for gathering attributes data while performing inspections to identify defects; for example, data about the frequencies or consequences of defects collected.
Statistical Sampling
Statistical Sampling
Statistical sampling involves choosing part of a population of interest for inspection (for example, selecting ten engineering drawings at random from a list of seventy-five). Sample frequency and sizes should be determined during the Plan Quality Management process so the cost of quality will include the number of tests, expected scrap, etc. There is a substantial body of knowledge on statistical sampling. In some application areas, it may be necessary for the project management team to be familiar with a variety of sampling techniques to assure the sample represents the population of interest.
Testing and Product Evaluations
Testing and Product Evaluations
Testing is an organized and constructed investigation conducted to provide objective information about the quality of the product or service under test in accordance with the project requirements. The intent of testing is to find errors, defects, bugs, or other nonconformance problems in the product or service. The type, amount, and extent of tests needed to evaluate each requirement are part of the project quality plan and depend on the nature of the project, time, budget, and other constraints. Tests can be performed throughout the project, as different components of the project become available, and at the end of the project on the final deliverables. Early testing helps identify nonconformance problems and helps reduce the cost of fixing the nonconforming components.
Control Charts
Control Charts
Control charts are used to determine whether or not a process is stable or has predictable performance. Upper and lower specification limits are based on the requirements and reflect the maximum and minimum values allowed. Upper and lower control limits are different from specification limits. The control limits are determined using standard statistical calculations and principles to ultimately establish the natural capability for a stable process. The project manager and appropriate stakeholders may use the statistically calculated control limits to identify the points at which corrective action will be taken to prevent performance that remains outside the control limits. Control charts can be used to measure various types of output variables. Although most frequently used to track repetitive activities required for producing manufactured lots, control charts may also be used to monitor cost and schedule variances, volume, frequency of scope changes, or other management results to help determine if the project management processes are in control.
Hierarchical Charts
Hierarchical Charts
Hierarchical charts are traditional organizational chart structures that can be used to show positions and relationships in a graphical, top-down format.
Hierarchical Charts
Hierarchical Charts
Hierarchical charts are traditional organizational chart structures that can be used to show positions and relationships in a graphical, top-down format.
Text Oriented Formats
Text Oriented Formats
Text oriented formats are documents that provide information such as responsibilities, authority, competencies, and qualifications. The documents are known by various names including position descriptions and role-responsibility-authority forms. These documents can be used as templates for future projects, especially when the information is updated throughout the current project by applying lessons learned.
Organizational Theory
Organizational Theory
Organizational theory provides information regarding the way in which people, teams, and organizational units behave. Effective use of common themes identified in organizational theory can shorten the amount of time, cost, and effort needed to create the Plan Resource Management process outputs and improve planning efficiency. It is important to recognize that different organizational structures have different individual responses, individual performance, and personal relationship characteristics. Also, applicable organizational theories may recommend exercising a flexible leadership style that adapts to the changes in a team’s maturity level throughout the project life cycle.
Team Charter
Team Charter
Team charter is a document that records the team values, agreements, and operating guidelines, as well as establishing clear expectations regarding acceptable behavior by project team members.
Procurement Management Plan
Procurement Management Plan
The procurement management plan is a component of the project management plan that describes how a project team will acquire goods and services from outside the performing organization. It describes how the procurement processes will be managed from developing procurement documents through contract closure.
Negotiation
Negotiation
Negotiation is a strategy of conferring with parties of shared or opposed interests with a view toward compromise or reaching an agreement. Negotiation is an integral part of project management and done well, increases the probability of project success.
Pre-Assignment
Pre-Assignment
When project team members are selected in advance, they are considered pre-assigned. This situation can occur if the project is the result of specific people being identified as part of a competitive proposal, if the project is dependent upon the expertise of particular persons, or if some staff assignments are defined within the project charter.
Virtual Teams
Virtual Teams
The use of virtual teams creates new possibilities when acquiring project team members. Virtual teams can be defined as groups of people with a shared goal who fulfill their roles with little or no time spent meeting face to face. The availability of communication technology such as e-mail, audio conferencing, social media, web-based meetings and video conferencing has made virtual teams feasible.
Physical Resource Assignments
Physical Resource Assignments
Physical resource assignments describe the expected resource utilization along with details such as type, amount, location, and whether the resource is internal to the organization or outsourced. They are dynamic and subject to change due to availability, the project, organization, environment, or other factors.
Enterprise Environmental Factors Updates
Enterprise Environmental Factors Updates
The enterprise environmental factors that may be updated as a result of the Develop Team process include, but are not limited to, personnel administration, employee training records, and skill assessments.
Colocation
Colocation
Colocation, also referred to as tight matrix involves placing many or all of the most active project team members in the same physical location to enhance their ability to perform as a team. Colocation can be temporary, such as at strategically important times during the project, or for the entire project. Colocation strategies can include a team meeting room (sometimes called war rooms), places to post schedules, and other conveniences that enhance communication and a sense of community. While colocation is considered a good strategy, the use of virtual teams can bring benefits such as the use of more skilled resources, reduced costs, less travel, and relocation expenses and the proximity of team members to suppliers, customers, or other key stakeholders.
Communication Technology
Communication Technology
The methods used to transfer information among project stakeholders may vary significantly. For example, a project team may use techniques from brief conversations to extended meetings, or from simple written documents to extensive materials (e.g., schedules, databases, and websites), which are accessible online as methods of communication.
Influencing
Influencing
Influencing is a key skill for all project managers due to often having little or no direct authority over team members in a matrixed environment. Influencing skills include the ability to be persuasive and clearly articulate points and positions. Influencing also requires high levels of active and effective listening skills as well as keen awareness and observations of the professional environment within which they operate.
Motivation
Motivation
Motivation provides a reason for someone to act. Teams are motivated by empowering them to participate in decision making and encouraging them to work independently.
Team Building
Team Building
Team building is conducting activities that enhance the team’s social relations and build a collaborative and cooperative working environment. Activities can vary from a 5-minute agenda item in a status to review meeting to an offsite, professionally facilitated event designed to improve interpersonal relationships. The objective is to help individual team members work together effectively.
Recognition and Rewards
Recognition and Rewards
Part of the team development process involves recognizing and rewarding desirable behavior. The original plans concerning ways in which to reward people are developed during the Plan Resource Management process. It is important to recognize that a particular reward given to any individual will be effective only if it satisfies a need which is valued by that individual. Award decisions are made, formally or informally, during the process of managing the project team through project performance appraisals. Cultural differences should be considered when determining recognition and rewards. A good strategy for project managers is to give the team recognition throughout the life cycle of the project rather than waiting until the project is completed.
Individual and Team Assessments
Individual and Team Assessments
Individual and team assessments are tools that give the project manager and the project team insight into areas of strengths and weaknesses. These tools help project managers assess team members’ preferences, aspirations, how they process and organize information, how they make decisions, and how they interact with people.
Team Performance Assessments
Team Performance Assessments
As project team development efforts such as training, team building, and collocation are implemented, the project management team makes formal or informal assessments of the project team’s effectiveness. Effective team development strategies and activities are expected to increase the team’s performance, which increases the likelihood of meeting project objectives. Team performance assessment criteria should be determined by all appropriate parties and incorporated in the Develop Team inputs. The performance of a successful team is measured in terms of technical success according to agreed-upon project objectives (including quality levels), performance on project schedule (finished on time), and performance on budget (finished within financial constraints). High-performance teams are characterized by these task-oriented and results-oriented outcomes.
Emotional Intelligence
Emotional Intelligence
Emotional intelligence is the ability to identify, assess, and manage the personal emotions of oneself and other people, as well as the collective emotions of groups of people.
Communication Models
Communication Models
The communication models used to facilitate communications and the exchange of information may vary from project to project and also within different stages of the same project. A basic communication model consists of two parties, defined as the sender and receiver. Medium is the technology medium and includes the mode of communication while noise includes any interference or barriers that might compromise the delivery of the message.
Communication Methods
Communication Methods
There are several communication methods that are used to share information among project stakeholders. The choices of communication methods that are used for a project may need to be discussed and agreed upon by the project stakeholders based on communication requirements; cost and time constraints; and familiarity and availability of the required tools and resources that may be applicable to the communications process.
Communication Styles Assessment
Communication Styles Assessment
Communication styles assessment is a technique used to identify the preferred communication method, format, and content for stakeholders for planned communication activities.
Cultural Awareness
Cultural Awareness
Cultural awareness is an understanding of the differences between individuals, groups, and organizations and adapting the project’s communication strategy in the contexts of these differences. This awareness and any consequent actions minimize misunderstandings and miscommunication that may result from cultural differences within the project’s stakeholder community. Cultural awareness and cultural sensitivity help the project manager to plan communications based on the cultural differences and requirements of stakeholders and team members.
Stakeholder Engagement Assessment Matrix
Stakeholder Engagement Assessment Matrix
The stakeholder engagement assessment matrix is a matrix that compares current and desired stakeholder engagement levels.
Communications Management Plan
Communications Management Plan
The communications management plan is a component of the project management plan that describes how project communications will be planned, structured, monitored, and controlled. The communications management plan can include guidelines and templates for project status meetings, project team meetings, e-meetings, and e-mail messages. The use of a project website and project management software can also be included if these are to be used in the project.
Communication Skills
Communication Skills
Communication skills are used to transfer information between stakeholders. There are two communication skills tools and techniques (feedback and presentations).
Communication Competence
Communication Competence
Communication competence is a combination of tailored communication skills that considers factors such as clarity of purpose in key messages, effective relationships and information sharing, and leadership behaviors.
Feedback
Feedback
Feedback is information about reactions to communications, a deliverable, or a situation. Feedback supports interactive communication between the project manager, team and all other project stakeholders. Examples include coaching, mentoring, and negotiating.
Nonverbal
Nonverbal
Examples of nonverbal communication include appropriate body language to transmit meaning through gestures, tone of voice, and facial expressions. Mirroring and eye contact are also important techniques. The team members should be aware of how they are expressing themselves both through what they say and what they don’t say.
Presentations
Presentations
A presentation is the formal delivery of information and/or documentation.
Project Reporting
Project Reporting
Project reporting is the act of collecting and distributing project information. Project information is distributed to many groups of stakeholders and should be adapted to provide information at an appropriate level, format, and detail for each type of stakeholder. The format may range from a simple communication to more elaborate custom reports and presentations. Information may be prepared regularly or on an exception basis. While work performance reports are the output of the Monitor and Control Project Work process, this process develops ad hoc reports, project presentations, blogs, and other types of communication about the project.
Assumption and Constraint Analysis
Assumption and Constraint Analysis
Every project and its project management plan are conceived and developed based on a set of assumptions and within a series of constraints. These are often already incorporated in the scope baseline and project estimates. Assumption and constraint analysis explores the validity of assumptions and constraints to determine which pose a risk to the project. Threats may be identified from the inaccuracy, instability, inconsistency, or incompleteness of assumptions. Constraints may give rise to opportunities through removing or relaxing a limiting factor that affects the execution of a project or process.
SWOT Analysis
SWOT Analysis
SWOT Analysis examines the project from each of the strengths, weaknesses, opportunities, and threats (SWOT) perspectives to increase the breadth of identified risks by including internally generated risks. The technique starts with the identification of strengths and weaknesses of the organization, focusing on either the project, organization or the business area in general. SWOT analysis then identifies any opportunities for the project that arise from organizational strengths, and any threats arising from organizational weaknesses. The analysis also examines the degree to which organizational strengths offset threats, as well as identifying opportunities that may serve to overcome weaknesses.
Prompt Lists
Prompt Lists
A prompt list is a predetermined list of risk categories that might give rise to individual project risks and that could also act as sources of overall project risk. The prompt list can be used as a framework to aid the project team in idea generation when using risk identification techniques. The risk categories in the lowest level of the risk breakdown structure can be used as a prompt list individual project risks. Some common strategic frameworks are more suitable for identifying sources of overall project risk, for example PESTLE (political, economic, social, technological, legal, environmental, TECOP (technical, environmental, commercial, operational, political) or VUCA (volatility, uncertainty, complexity, ambiguity).
Risk Data Quality Assessment
Risk Data Quality Assessment
Risk data quality assessment is a technique used to evaluate the degree to which the data about risks is useful for risk management.
Risk Probability and Impact Assessment
Risk Probability and Impact Assessment
Risk probability assessment investigates the likelihood that each specific risk will occur. Risk impact assessment investigates the potential effect on a project objective such as schedule, cost, quality, or performance, including both negative effects for threats and positive effects for opportunities. Probability and impact are assessed for each identified risk. Risks can be assessed in interviews or meetings with participants selected for their familiarity with the risk categories on the agenda. Project team members and knowledgeable persons external to the project are included. The level of probability for each risk and its impact on each objective is evaluated during the interview or meeting. Explanatory detail, including assumptions justifying the levels assigned, are also recorded. Risk probabilities and impacts are rated according to the definitions given in the risk management plan. Risks with low ratings of probability and impact will be included within the risk register as part of the watch list for future monitoring.
Assessment of Other Risk Parameters
Assessment of Other Risk Parameters
The project team may consider other characteristics of risk (in addition to probability and impact) when prioritizing individual project risks for further analysis and action. These characteristics may include but are not limited to: Urgency, proximity, dormancy, manageability, controlability, detectability, connectivity, strategic impact, and propinquity. The consideration of some of these characteristics can provide a more robust prioritization of risks than is possible by only assessing probability and impact.
Risk Categorization
Risk Categorization
Risks to the project can be categorized by sources of risk (e.g., using the RBS), the area of the project affected (e.g., using the WBS), or other useful categories (e.g., project phase) to determine the areas of the project most exposed to the effects of uncertainty. Risks can also be categorized by common root causes. This technique helps determine work packages, activities, project phases or even roles in the project, which can lead to the development of effective risk responses.
Probability and Impact Matrix
Probability and Impact Matrix
Risks can be prioritized for further quantitative analysis and planning risk responses based on their risk rating. Ratings are assigned to risks based on their assessed probability and impact. Evaluation of each risk’s importance and priority for attention is typically conducted using a look-up table or a probability and impact matrix. Such a matrix specifies combinations of probability and impact that lead to rating the risks as low, moderate, or high priority. Descriptive terms or numeric values can be used depending on organizational preference.
Representations of Uncertainty
Representations of Uncertainty
Quantitative risk analysis requires inputs to a quantitative risk analysis model that reflect individual project risks and other sources of uncertainty.
Simulations
Simulation
Simulation is an analytical technique that models the combined effect of uncertainties to evaluate their potential impact on objectives.
Sensitivity Analysis
Sensitivity Analysis
Sensitivity analysis is an analysis technique used to determine which individual project risks or other sources of uncertainty have the most potential impact on project outcomes, by correlating variations in project outcomes with variations in elements of a quantitative risk analysis model.
Decision Tree Analysis
Decision Tree Analysis
Decision tree analysis is a diagramming and calculation technique for evaluating the implications of a chain of multiple options in the presence of uncertainty.
Influence Diagrams
Influence Diagrams
Influence diagrams are graphical aids to decision making under uncertainty. An influence diagram represents a project or situation within the project as a set of entities, outcomes, and influences, together with the relationships and effects between them. Where an element in the influence diagram is uncertain as a result of the existence of individual project risks or other sources of uncertainty, this can be represented in the influence diagram using ranges or probability distributions. The influence diagram is then evaluated using a simulation technique, such as Monte Carlo analysis, to indicate which elements have the greatest influence on key outcomes. Outputs from an influence diagram are similar to other quantitative risk analysis methods, including S-curves and tornado diagrams.
Strategies for Threats
Strategies for Threats
Five alternative strategies may be considered for dealing with threats (Escalate, Avoid, Transfer, Mitigate, and Accept).
Strategies for Opportunities
Strategies for Opportunities
Five alternative strategies may be considered for dealing with opportunities (Escalate, Exploit, Share, Enhance, and Accept).
Contingent Response Strategies
Contingent Response Strategies
Some responses are designed for use only if certain events occur. For some risks, it is appropriate for the project team to make a response plan that will only be executed under certain predefined conditions, if it is believed that there will be sufficient warning to implement the plan. Events that trigger the contingency response, such as missing intermediate milestones or gaining higher priority with a supplier, should be defined and tracked. Risk responses identified using this technique are often called contingency plans or fallback plans and include identified triggering events that set the plans in effect.
Strategies for Overall Project Risk
Strategies for Overall Project Risk
Risk responses should be planned and implemented not only for individual project risks but also to address overall project risk. The same risk response strategies that are used to deal with individual project risks can also be applied to overall project risk (Avoid, Exploit, Transfer/Share, Mitigate/Enhance, and Accept).
Technical Performance Analysis
Technical Performance Analysis
Technical performance analysis compares technical accomplishments during project execution to the schedule of technical achievement. It requires the definition of objective, quantifiable measures of technical performance, which can be used to compare actual results against targets. Such technical performance measures may include weight, transaction times, number of delivered defects, storage capacity, etc. Deviation can indicate the potential impact of threats or opportunities.
Market Research
Market Research
Market research includes examination of industry and specific vendor capabilities. Procurement teams may leverage information gained at conferences, online reviews and a variety of sources to identify market capabilities. The team may also refine particular procurement objectives to leverage maturing technologies while balancing risks associated with the breadth of vendors who can provide the materials or services desired.
Make-Or-Buy Analysis
Make-Or-Buy Analysis
A make-or-buy analysis is a general management technique used to determine whether particular work can best be accomplished by the project team or should be purchased from outside sources. Sometimes a capability may exist within the project organization, but may be committed to working on other projects, in which case, the project may need to source such effort from outside the organization in order to meet its schedule commitments. Budget constraints may influence make-or-buy decisions. If a buy decision is to be made, then a further decision of whether to purchase or lease is also made. A make-or-buy analysis should consider all related costs both direct costs as well as indirect support costs. For example, the buy-side of the analysis includes both the actual out-of-pocket costs to purchase the product, as well as the indirect costs of supporting the purchasing process and purchased item.
Source Selection Analysis
Source Selection Analysis
It is necessary to review the prioritization of the competing demands for the project before deciding on the selection method. Since competitive selection methods may require sellers to invest a large amount of time and resources upfront, it is a good practice to include the evaluation method in the procurement documents so bidders know how they will be evaluated. Commonly used selection methods include the following: least cost, qualifications only, quantity-based/highest technical proposal score, quality and cost-based, sole-source, and fixed budget.
Procurement Strategy
Procurement Strategy
Procurement strategy is the approach by the buyer to determine the project delivery method and the type of legally binding agreement(s) that should be used to deliver the desired results.
Bid Documents
Bid Documents
Bid documents are used to solicit information, quotations, or proposals from prospective sellers.
Procurement Statement of Work
Procurement Statement of Work
The statement of work (SOW) for each procurement is developed from the project scope baseline and defines only that portion of the project scope that is to be included within the related contract. The procurement SOW describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products, services, or results. Sufficient detail can vary based on the nature of the item, the needs of the buyer, or the expected contract form. Information included in a SOW can include specifications, quantity desired, quality levels, performance data, period of performance, work location, and other requirements.
Source Selection Criteria
Source Selection Criteria
Source selection criteria are often included as a part of the procurement documents. Such criteria are developed and used to rate or score seller proposals, and can be objective or subjective. Selection criteria may be limited to only the purchase price if the procurement item is readily available from a number of acceptable sellers. Purchase price in this context includes both the cost of the item and all ancillary expenses such as delivery.
Make-Or-Buy Decisions
Make-Or-Buy Decisions
A make-or-buy analysis results in a decision of whether particular work can best be accomplished by the project team or needs to be purchased from outside sources. If the decision is to make the item, then the procurement plan may define processes and agreements internal to the organization. A buy decision drives a similar process of reaching an agreement with a supplier for the product or services.
Independent Cost Estimates
Independent Cost Estimates
For large procurements, the procuring organization may elect to either prepare its own independent estimate or have a cost estimate prepared by an outside professional estimator to serve as a benchmark on proposed responses. Significant differences in cost estimates can be an indication that the procurement SOW was deficient or ambiguous, or that the prospective sellers either misunderstood or failed to respond fully to the procurement SOW.
Seller Proposals
Seller Proposals
Seller proposals are formal responses from sellers to request a proposal or other procurement document specifying the price, commercial terms of sale, and technical specifications or capabilities the seller will do for the requesting organization. If accepted, it would bind the seller to perform the resulting agreement.
Advertising
Advertising
Existing lists of potential sellers often can be expanded by placing advertisements in general circulation publications such as selected newspapers or in specialty trade publications. Some organizations use online resources to communicate solicitations to the vendor community. Some government jurisdictions require public advertising of certain types of procurement items, and most government jurisdiction require public advertising or online posting of pending government contracts.
Bidder Conferences
Bidder Conferences
Bidder conferences (sometimes called contractor conferences, vendor conferences, and pre-bid conferences) are meetings between the buyer and all prospective sellers prior to submittal of a bid or proposal. They are used to ensure that all prospective sellers have a clear and common understanding of the procurement requirements, and that no bidders receive preferential treatment. To be fair, buyers should take great care to ensure that all prospective sellers hear every question from any individual prospective seller and every answer from the buyer. Typically fairness is addressed by techniques such as collecting questions from bidders or arranging field visits in advance of the bidder conference. Responses to questions can be incorporated into the procurement documents as amendments.
Proposal Evaluation
Proposal Evaluation
Proposal evaluation is the process of reviewing proposals provided by suppliers to support contract award decisions.
documents as amendments.
Selected Sellers
Selected Sellers
The selected sellers are those who have been judged to be in a competitive range based upon the outcome of the proposal or bid evaluation, and who have negotiated a draft contract that will become the actual contract when an award is made. Final approval of all complex, high-value, high-risk procurements will generally require organizational senior management approval prior to award.
Claims Administration
Claims Administration
Contested changes and potential constructive changes are those requested changes where the buyer and seller cannot reach an agreement on compensation for the change or cannot agree that a change has occurred. These contested changes are variously called claims, disputes, or appeals. Claims are documented, processed, monitored, and managed throughout the contract life cycle, usually in accordance with the terms of the contract. If the parties themselves do not resolve a claim, it may have to be handled in accordance with alternative dispute resolution (ADR) typically following procedures established in the contract. Settlement of all claims and disputes through negotiation is the preferred method.
Closed Procurements
Closed Procurements
The buyer, usually through its authorized procurement administrator, provides the seller with formal written notice that the contract has been completed. Requirements for formal procurement closure are usually defined in the terms and conditions of the contract and are included in the procurement management plan.
Procurement Documentation Updates
Procurement Documentation Updates
Procurement documentation that may be updated includes the contract with all supporting schedules, requested unapproved contract changes, and approved change requests. Procurement documentation also includes any seller-developed technical documentation and other work performance information such as deliverables, seller performance reports and warranties, financial documents including invoices and payment records, and the results of contract-related inspections.
Stakeholder Mapping and Representation
Stakeholder Mapping and Representation
Stakeholder mapping and representation is a method of categorizing stakeholders using various methods. Categorizing stakeholders assists the team in building relationships with the identified project stakeholders.