Step 4
Process Groups & Performance Domains — Illustrated Study Guide
The 5 Process Groups, the 7 Performance Domains — Governance, Scope, Schedule, Finance, Stakeholders, Resources, and Risk — full notes, an illustration for every topic, 3 accurate reference diagrams, and a 100-question practice quiz.
Focus Areas The 5 Process Groups
- Refer to the mindmap for all 40 processes, grouped by focus area.
- There are 5 focus areas — the 5 Process Groups — and they apply to all application areas.
- They apply to all development approaches — predictive, adaptive, and hybrid.
- Focus areas are not project phases. A project creates the phases of a project; each phase involves all 40 processes.
- Focus areas are not sequential — they often overlap.
- The level of effort for each focus area is not always sequential either; it can vary depending on the project phase, the project life cycle, and the development approach.
The 5 Process Groups
1Initiating — "Authorize"
- New project or a new phase; formal authorization.
- Aligns stakeholder expectations, project purpose, scope, and objectives.
- Produces the Project Charter and the Stakeholder Register.
2Planning — "Project Management Plan"
- Defines the scope, refines the objectives.
- Creates the project management plan or the product backlog.
- Not done once — happens throughout the project; predictive projects do more planning up front.
3Executing — "Do the Work"
- Complete the work according to the current plan.
- Coordinating resources, managing stakeholders, performing project activities.
- Keeps the team focused.
4Monitoring & Controlling — "Track the Work"
- Track, measure, review, and regulate progress and performance.
- Compares actual performance to planned performance and reports the information.
- Happens throughout the project, in parallel with the other groups — not a separate phase.
5Closing — "Complete the Work / Shut Down"
- Formally complete or close a project or a phase; terminate early when it no longer makes sense to continue.
- Verifies that project actions are completed. Close and transition; document lessons learned.
- Produces the final project report.
Process Groups Interaction Diagram
How the 5 process groups interact
- A vertical double-headed Project Boundaries arrow spans the full height of the diagram, marking where the project starts and ends.
- A dashed horizontal line splits the diagram into an upper and lower half.
- Above the line: Planning and Executing sit side by side, connected by a circular two-way arrow — they repeatedly cycle with each other.
- Below the line: Initiating and Closing sit side by side.
- Monitoring & Controlling overlaps both halves on the left, reaching toward all four of the other process boxes — it oversees Planning, Executing, Initiating, and Closing throughout.
- At the top: Deliverables feed up into the End User; Charter/Records feed up into Organizational Process Assets.
- At the bottom: the Sponsor and Business Documents feed into Initiating.
Visual recap
Reference diagram
Performance Domains
Overview The 7 Performance Domains
1. Governance
2. Scope
3. Schedule
4. Finance
5. Stakeholders
6. Resources
7. Risk
- Not every project will use all 40 processes — but every project uses all 7 performance domains. They are common practices.
- They are a group of related processes that help deliver value.
- They are interactive — related to and dependent on each other — and work together as one integrated system to achieve project results.
- They do not have a specific order or weighting.
- Successful project delivery depends on how well these domains work together.
- These domains are illustrative, not prescriptive — they explain common practices but are not a required step-by-step methodology.
Domain 1 Governance
- Governance = how the project is managed. It is a combination of the other 6 domains.
- It is a framework — functions and processes used to guide project decisions and activities.
- Governance helps optimize project value delivery, and helps integrate all the other domains.
Tailored by development approach
Lightweight
- For adaptive/agile projects.
Moderate
- For hybrid projects.
Comprehensive
- For large predictive projects.
Types of governance
Structured
- Sponsor, PMO leader, governance board, and project manager hold the decision-making roles.
Self-governance
- Gives more decision-making responsibility to the project team and the PM.
Predictive projects tend to need stronger governance tools, such as an escalation path and investment control.
Leading vs. Lagging Indicators
- Leading indicators — show early warning signs or trends before problems happen.
- Lagging indicators — show what has already happened on the project.
- Both help the project team identify possible issues early and take corrective action before the project goes off track.
- Example indicators: completed deliverables, schedule variance, cost variance, and resources used.
Visual recap
Domain 2 Scope
- Scope defines what the project will actually accomplish.
- It should include all required work — and only the required work.
- It also includes quality — the project must meet both scope and quality requirements. Quality is now treated as part of scope.
Product Scope
- Describes the features, functions, and requirements of the product, service, or result.
- Explains what the product is, not the work needed to create it.
Project Scope
- Describes the work needed to deliver the product, service, or result.
- Explains what the project team must do to create and deliver the product.
Value Breakdown Structure (VBS) — organizes deliverables by the value they provide, helping the team prioritize and deliver the most valuable work first.
Visual recap
Domain 3 Schedule
- Includes the work needed to plan, develop, monitor, and control the project schedule.
- Schedules can be created at different levels of detail depending on the project approach, the organization, and its needs.
- A project schedule includes linked activities, planned dates, durations, milestones, dependencies, and resources.
- Develop your schedule right, monitor your schedule, and control your schedule to have a successful project.
Rolling wave planning — plan the high-level work first, then add more detail as the project progresses.
Visual recap
Domain 4 Finance
- Focuses on how project money and financial resources are planned and used, managed and controlled.
- Covers project cost, funding, budgeting, financing, and value.
- Financial information helps the team compare actual performance against the plan.
- Value maximization — not only controlling cost, but also delivering the greatest possible value.
- Funding explains where the money comes from — internal budget, customer contracts, grants, or crowdfunding.
- Financial constraints — limits on how project money can be used, such as budget limits, funding rules, or time restrictions.
CapEx — Capital Expenditure
- Money used for long-term assets.
OpEx — Operational Expenditure
- Money used for ongoing business operations.
Visual recap
Domain 5 Stakeholders
- Identifying, analyzing, engaging, and monitoring stakeholders throughout the project.
- Stakeholders include the sponsor, team members, customers, users, and anyone impacted by the project — internal or external.
- Their power, interest, influence, and support may change as the project progresses.
- This domain closely connects to Communication Management.
- Stakeholder engagement — identifying stakeholders, understanding their needs, managing expectations, and keeping them involved.
- Sponsor engagement — critical; the sponsor supports the project, provides resources, approves key documents, and helps align the project with strategy.
- Stakeholder satisfaction — built into project objectives through continuous communication and issue resolution.
- Team engagement — important, as the team does the project work and provides recommendations.
Stakeholder Circles
Outer Ring
- Suppliers & vendors, customers, end users, regulatory bodies, local communities, family.
→ "Affected by project."
Middle Ring
- Sponsor, government bodies, Project Management Office (PMO), steering committee.
→ "Determines the direction."
Inner Ring
- Project Manager, Project Management Team, Project Team.
→ "Project Team."
Visual recap
Reference diagram
Domain 6 Resources
- Focuses on how the project team plans, uses, and manages resources.
- Resources include both people and non-human resources.
- The project manager is responsible for building, managing, motivating, and empowering the project team.
- A resource manager has authority over one or more resources and may help assign internal resources to the project.
Human Resources
- Project team members who have roles and responsibilities to complete project work.
- Team members may be directed by leadership or may self-organize, depending on the project approach.
Physical / Material / Virtual Resources
- Equipment, materials, facilities, software, licenses, testing environments, services, and other non-human resources.
Visual recap
Domain 7 Risk
- Focuses on managing uncertainty and protecting the project from disruption.
- The goal is to anticipate, prepare for, respond to, and adapt to risks.
- Risk management should be proactive, not reactive.
- The team should plan for known risks before they happen, and stay flexible and ready to adjust when unexpected risks occur.
Key risk definitions
1Risk Appetite
- How much uncertainty an organization or person is willing to accept for a possible reward.
2Risk Threshold
- The acceptable amount of variation around a project objective, such as allowing cost to vary by ±5% or ±10%.
3Risk Exposure
- The total potential impact of all risks on the project at a specific point in time.
4Risk Response
- An action taken to handle threats or opportunities.
5Project Resilience
- The project's ability to absorb disruptions, recover quickly, and continue delivering value.
The Known/Unknown Risk Matrix
Not a Risk
Known – Known
A fact / requirement — already part of scope.
Classic Risk
Known – Unknown
Probability and impact can be identified.
Hidden Fact
Unknown – Known
Knowledge exists in the community, but not with the project team.
Emergent Risk
Unknown – Unknown
Knowledge does not exist within the sphere of influence.
Visual recap
Reference diagram
Practice Time
Recall Recall Quiz
Straight recall — Focus Areas, the 5 Process Groups, the Process Groups Interaction Diagram, and the 7 Performance Domains, straight from the notes above.
Scenario Case Study Quiz
Short, standalone situational questions — apply the concepts above to one scenario at a time.
New Format Long Case Studies
Matches the newer PMI exam format: one longer scenario, several linked questions. 6 case studies, 5 questions each — one per Step 4 topic cluster.
Advanced Step 1 + Step 2 + Step 3 + Step 4 Mix
The toughest round — integration questions blending Step 1 (PMP Mindset & Fundamentals), Step 2 (Principles & Leadership), Step 3 (Development Approaches & Project Lifecycles), and Step 4 (Process Groups & Performance Domains).