PMI Process Chart: PMBOK® 6th vs 8th Edition Synthesis
A complete reference chart synthesising the PMBOK® Guide legacy 49 processes with modern, principle-driven performance domains and adaptable delivery frameworks.
- The Evolution of PMBOK® Standards
- PMBOK® Guide 8th Edition Elements
- PMBOK® Guide 6th Edition: The 49 Processes
§1 The Evolution of PMBOK® Standards
The transition from the 6th to the 8th edition represents a fundamental shift in project management paradigms—from prescriptive processes to principle-driven delivery.
The 6th Edition was deeply rooted in a rigid, predictive process matrix: 49 discrete processes mapped across 10 Knowledge Areas and 5 Process Groups. It focused heavily on "how" to perform project management tasks step-by-step.
In contrast, the 8th Edition (and its predecessor, the 7th) pivots to a systems-thinking approach. It introduces Core Principles that guide behaviour and Performance Domains that focus on outcomes rather than rigid deliverables. This synthesis document bridges both worlds, providing practitioners with the modern outcome-focused framework while retaining the tactical process mapping of the 6th edition where adaptive tailoring is required.
§2 PMBOK® Guide 8th Edition Elements
A holistic view of the modern framework, encompassing principles, performance domains, and adaptable guidance.
| Component / Area | Purpose & Application |
|---|---|
| Core Principles (6) | |
| Stewardship | Act responsibly, ethically, and with accountability for project outcomes |
| Collaboration | Build effective relationships and teamwork |
| Value Focus | Prioritise outcomes, benefits, and stakeholder value |
| Systems Thinking | Understand project interactions within the wider organisation |
| Adaptability & Tailoring | Adjust methods, governance, and processes to suit the environment |
| Leadership & Change | Guide people, decisions, and organisational change |
| Performance Domains (7) | |
| Stakeholders | Identify, analyse, engage, and manage stakeholder relationships |
| Team | Develop capable teams, collaboration, leadership, and accountability |
| Planning | Establish approach, scope, schedule, resources, cost, and execution strategy |
| Project Work | Perform project activities, manage resources, communications, and knowledge |
| Delivery | Produce outputs, outcomes, quality, and benefits |
| Measurement | Monitor performance, metrics, forecasting, and decision support |
| Uncertainty | Manage risks, opportunities, complexity, and changing conditions |
| Adaptable Process Guidance (~40 Processes) | |
| Project Integration Processes | Coordinate project components, governance, decisions, changes, and alignment |
| Stakeholder Processes | Identify stakeholders, understand needs, communicate, and maintain engagement |
| Team Processes | Establish teams, develop capability, manage collaboration and performance |
| Planning Processes | Define delivery approach, objectives, requirements, schedules, resources, and budgets |
| Scope & Requirements Processes | Define desired outcomes, boundaries, requirements, and acceptance criteria |
| Schedule Processes | Develop timelines, sequencing, forecasting, and schedule control |
| Cost & Financial Processes | Estimate costs, establish budgets, monitor expenditure, and maintain financial alignment |
| Quality Processes | Plan quality, assure processes, verify deliverables, and improve outcomes |
| Resource Processes | Identify, acquire, optimise, and manage physical and human resources |
| Communication Processes | Create information flow, reporting, collaboration, and transparency |
| Risk & Uncertainty Processes | Identify uncertainty, analyse impacts, develop responses, and monitor conditions |
| Procurement Processes | Plan sourcing, select suppliers, manage contracts, and evaluate supplier performance |
| Change Processes | Assess changes, evaluate impacts, approve decisions, and maintain alignment |
| Measurement Processes | Track progress, analyse performance, forecast outcomes, and support decisions |
| Supporting Modern Guidance | |
| AI in Project Management | AI-assisted estimation, scheduling, reporting, analysis, automation, and decision support |
| PMO Guidance | Governance, standards, capability development, strategic alignment, value management |
| Procurement Evolution | Supplier collaboration, flexible contracting, digital procurement approaches |
| Tailoring | Select appropriate methods, processes, artifacts, and controls |
| Value Delivery System | Connect strategy → portfolios → programs → projects → products → benefits |
| Delivery Approaches | |
| Predictive | Sequential planning and controlled delivery |
| Agile | Incremental, adaptive, customer-focused delivery |
| Hybrid | Combination of predictive and adaptive approaches |
| Product-Oriented | Continuous value delivery through products and capabilities |
§3 PMBOK® Guide 6th Edition: The 49 Processes
The legacy process matrix mapping 10 Knowledge Areas across the 5 traditional Process Groups.
| Knowledge Area | Initiating | Planning | Executing | Monitoring & Controlling | Closing |
|---|---|---|---|---|---|
| Project Integration Management | 1. Develop Project Charter | 2. Develop Project Management Plan | 3. Direct & Manage Project Work 4. Manage Project Knowledge |
5. Monitor & Control Project Work 6. Perform Integrated Change Control |
7. Close Project or Phase |
| Project Scope Management | 8. Plan Scope Management 9. Collect Requirements 10. Define Scope11. Create WBS |
12. Validate Scope 13. Control Scope |
|||
| Project Schedule Management | 14. Plan Schedule Management 15. Define Activities 16. Sequence Activities 17. Estimate Activity Durations 18. Develop Schedule |
19. Control Schedule | |||
| Project Cost Management | 20. Plan Cost Management21. Estimate Costs 22. Determine Budget |
23. Control Costs | |||
| Project Quality Management | 24. Plan Quality Management | 25. Manage Quality | 26. Control Quality | ||
| Project Resource Management | 27. Plan Resource Management28. Estimate Activity Resources | 29. Acquire Resources 30. Develop Team 31. Manage Team |
32. Control Resources | ||
| Project Communications Management | 33. Plan Communications Management | 34. Manage Communications | 35. Monitor Communications | ||
| Project Risk Management | 36. Plan Risk Management 37. Identify Risks 38. Perform Qualitative Risk Analysis 39. Perform Quantitative Risk Analysis 40. Plan Risk Responses |
41. Implement Risk Responses | 42. Monitor Risks | ||
| Project Procurement Management | 43. Plan Procurement Management | 44. Conduct Procurements | 45. Control Procurements | ||
| Project Stakeholder Management | 46. Identify Stakeholders | 47. Plan Stakeholder Engagement | 48. Manage Stakeholder Engagement | 49. Monitor Stakeholder Engagement |
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review PMI Process Chart: PMBOK® 6th vs 8th Edition Synthesis. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Use PMI Process Chart: PMBOK® 6th vs 8th Edition Synthesis as a decision instrument rather than an administrative form. The subject terms—pmbok, edition, processes, chart, synthesis—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.
Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.
A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.
Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.
Step-by-step operating method
- Name the decision. Write the decision, approval, handover or control activity the completed template must support.
- Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
- Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
- Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
- Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.
Completion and governance protocol
Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.
| Information type | Minimum useful content | Review test |
|---|---|---|
| Outcome | Observable change and intended recipient | Not merely a deliverable or activity |
| Measure | Definition, baseline, target, frequency and source | Two reviewers would calculate it the same way |
| Ownership | One accountable role plus contributors and approver | Authority matches responsibility |
| Uncertainty | Assumption, risk or issue with response and trigger | Status reflects current reality |
| Control | Version, approval, review date and change rule | Current baseline is identifiable |
Common failure modes and recovery actions
1. Watch for
Filling every box even when a field is not applicable instead of recording why.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Writing vague statements without an owner, measure, date or evidence source.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Copying a previous project without revalidating assumptions and stakeholders.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Using the document as a private worksheet when it is meant to support a shared decision.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Creating an approved baseline but failing to define who maintains it and when.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- Is the purpose and intended decision clear to a reader outside the team?
- Are owners, dates, measures and sources complete and internally consistent?
- Which fields are assumptions and how will they be validated?
- What event, threshold or review date causes this document to change?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying PMI Process Chart: PMBOK® 6th vs 8th Edition Synthesis?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about pmbok would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- PMI Standards and Publications — Project Management Institute. Used for project, program, portfolio and organisational project management. Accessed 2026-08-13.
- ISO 31000 family — Risk management — International Organization for Standardization. Used for principles and guidance for enterprise risk management. Accessed 2026-08-13.