[Part-1]
(A) Some Key Terms/Definitions are Changed:
This is massive, some of the key definitions that did not change in last 30 years, changed in this version. Even the definition of Project, Project Management and Portfolio are changed significantly. Have a close look on the image to understand the difference. Everything is now value and outcome focus. For me these are great changes for the project professionals to re-adjust, re-align their main focus while managing projects.
(B) PMI Talent Triangle:
The second most notable thing is the change in the talent triangle. The Project Manager and Project Management Team should possess not only these three competencies –
- Power Skills
- Business Acumen and
- Ways of working, but also
- Social Responsibilities (This competency refers to the acknowledgment that the project management team makes decisions that are aligned to the common good.) and
- Results (This competency refers to the actual work and execution of ideas and projects to add value. The ability to accomplish tasks is a central competency that helps ensure the expected value is delivered.)
[Part-2]
Ah! Project Management Mindset.
What is lacking most in the world of project management?
Is the mindset – the project management mindset.
The project manager and the project management team should have the right mindset otherwise the project will struggle in every step. The project manager and the team should be value-driven, proactive, and take ownership to make the project successful.
The six principles of the PMBOK 8th edition are beauty.
- To be proactive “Adopt a holistic view” and “Embed Quality in Processes and Deliverable”
- To be value-driven “Focus on Value” and “Integrate Sustainability within all Project Areas”
- Take the ownership by “being an accountable leader” and “building an empowered culture” in the team
A principle is a fundamental norm, truth, or value that remains agnostically true for every culture, generations and time and gives guidance for the project manager and project team to build the right mindset, behaviour, and attitude.
Note: In recent time, I had published the second edition (Published on 02 January 2025) of my book “অল্পে গল্পে প্রকল্প পরিচালনা – A Project Management Fable”, and the major change was inclusion of a new chapter titled “Project Mindset” and see how surprisingly it aligned with PMI.
In my book, I spelled out that every project manager and project management team should have four senses (4S): Sense of purpose (value-driven), Sense of ownership (ownership), Sense of urgency (proactive) and Sense of caring (for People, Planet and Prosperity).
[Part-3]
🟢 The Arts and Science of Project Management:
🔸 For me, the most important figure in PMBOK 8th Edition is this. This figure summarizes the arts and science of Project Management. The six principles shown in the middle circle will help you (PM and the Project Management Team) build your inner ‘You’ to be a proactive, value-driven, ownership assumed project leader – the center circle – the mindset (the arts).
🔸 This mindset, behavior, and attitude influence and shape the performance domains (the outer circle) to produce the intended outcomes. The new 7 performance domains are aligned with the earlier version of knowledge areas, though the performance domains are outcome focus, and the knowledge areas were output focused. I have drawn another outer circle around the performance domain, the non-prescriptive 40 processes which will guide you to deliver the project efficiently and effectively (the science).
🔸 The performance domains and non-prescriptive processes you can use in any approach, whether it is predictive, agile, or hybrid.
✪ Points to Note ✪
✔︎ 5 Process Groups are now 5 Focus Areas
✔︎ 10 Knowledge Areas are now 7 Performance Domains (In contrast with PMBOK 7th Edition: 8 Performance Domains –> 7 Performance Domains)
✔︎ Name Changed: Integration is now ‘Governance’ and Cost is now ‘Finance’
✔︎ 2 Knowledge Areas are merged (Stakeholders = Communication + Stakeholder)
✔︎ Quality is merged with Scope and Governance Performance domains
✔︎ Procurement is merged with Governance (Plan Sourcing Strategy) and shift to Appendix X4 (Conduct Procurement & Control Procurement)
✔︎ 49 Processes downsized to 40 Processes
Video: PMBOK 8th Edition Processes
✔︎ Schedule (Define Activities + Sequence Activities + Estimate Activity Durations = Develop Schedule) – 3
✔︎ Resources (Develop Team + Management Team = Lead the Team) – 1
✔︎ Risk (Perform Risk Analysis = Perform Qualitative Risk Analysis + Perform Quantitative Risk Analysis) – 1
✔︎ Quality (Plan Quality & Control Quality are merged with Scope and Manage Quality Assurance is merged with Governance) – 2
✔︎ Procurement (Plan Sourcing Strategy is merged with Governance and Conduct Procurement & Control Procurement are shifted to Appendix X4) – 2
✔︎ Ultimately, the 49 processes are there with different name and shape
✪ Focus Area wise 40 processes: Initiating (2), Planning (19), Execution (8), Monitoring and Controlling (10), Closing (1)
❇️ [Part-4] PMBOK Guide Structure and Where is ITTOs
PMBOK Guide (8th Edition) is divided into two parts:
- (A) The Standard for Project Management [ANSI part] and
- (B) A Guide to the Project Management Body of Knowledge (PMBOK). The attached infographic (Fig 2) indicates which part contains ‘What’.
Oh! This is big news; ITTOs are back along with the 40 processes in the PMBOK 8th Edition. Those who do not know what ITTO is, to accomplish processes right each process is having Inputs, Tools and Techniques and Outputs (ITTO). Classically, this is known as ITTOs.
✔︎ The process inputs are those documents or documentable things upon which or using which different tools and techniques (Generally, management techniques, theories, power skills, different models, methods etc.) are applied to produce the targeted outputs (Documents or documentable things) [FIG 1]. Earlier in the PMBOK 7th edition this Tools and Techniques were named as Model and Method and Inputs and Outputs were known as Artifacts. The same process tables or charts of ITTOs are reintroduced using modern looking graphics.
✔︎ Like the Process Group: A Practice Guide, two (02) chapters are introduced in the ‘A Guide to the PMBOK’ part of the PMBOK 8th Edition one is Inputs and Outputs (Chapter 4) and the other one is Tools and Techniques (Chapter 5). All the #ITTOs are described in ascending order for all the 40 processes in these two chapters. Some new tools and techniques like Design Thinking, Six Thinking Hats, AI, AR, VR, COCOMO, TOC, Critical Chain Method, CCPM, Project Canvas, Storytelling, etc. are included in this version of PMBOK 8th Edition.
✔︎ Context counts, based on your project, organization, country and culture you may need to customize Project Life Cycle, Development Approach, Processes (along with ITTOs, Models, Methods and Artifacts), Engagement. This has been discussed in detail in a dedicated chapter titled “Tailoring”. How to tailor the performance domains is also discussed in each performance domain separately in the Performance Domain Chapter (Chapter 2).#pmi #pmbok8 #ITTO
💢 [End Notes] The “Magical Numbers” of PMBOK Guide – Eighth Edition and My End Notes:
Let me conclude this series of posts on the PMBOK Guide – Eighth Edition by highlighting the “magical numbers” that define its structure: 5, 6, 7, and 8.
The new Eighth Edition comes to life through the integration of:
- ✔︎ 5 Focus Areas
- ✔︎ 6 Principles
- ✔︎ 7 Performance Domains
And if you multiple first number (5) with the last number (8), you will come up with 40, which is number of processes in the 8th Edition.
🟠 While this edition is considered the most evidence-based version to date, developed using thousands of data points, I have several critical observations regarding its content and focus:
❇️ Monitoring vs. Evaluation:
The Outcome GapFor the first time, PMI explicitly discusses short-, mid-, and long-term project outcomes. This is a positive step. However, the core text remains heavily skewed toward Monitoring and Controlling—processes that prioritize immediate outputs and activities.There is still insufficient guidance on Project Evaluation, the practice of measuring achievement against broader strategic outcomes. This is a glareing omission for the Development and Public sectors, where success is rarely defined by short-term deliverables. I remain hopeful that future updates will address “Evaluation” with the weight it deserves.
❇️ The Missing Plans: Sustainability & Compliance
This edition dedicates significant narrative space to sustainability and compliance, yet fails to formalize them in the planning structure. Despite detailing 40 processes and numerous artifacts, specific Sustainability Management Plans and Compliance Management Plans are notably absent. If these concepts are critical enough to discuss, they should be critical enough to plan for formally.
❇️ Where is Quality?
The decision to remove Quality as a standalone Performance Domain is a major concern. Quality is not just a sub-component of other activities; it demands a dedicated domain covering Plan Quality, Quality Assurance (QA), and Quality Control (QC). I expect this omission will be a hot topic of debate in the community.
❇️ The Disappearance of Models
I was disappointed to see the removal of the Models section from the Seventh Edition. Those models—covering change, complexity, and leadership—were “eye-openers” for many professionals. Removing them feels like a loss of valuable context for the modern practitioner.
❇️ The Disciplined Agile (DA) Retreat
Finally, looking at the visuals (specifically Figure 4-7), Disciplined Agile (DA) has been removed. What does this signal? It seems PMI is taking one step forward and two steps back regarding their Agile portfolio. It raises valid questions about their strategy for DA, the PMI-ACP, and their partnership with the Agile Alliance.
#PMBOK8 #ProjectManagement #PMP #PMI #Agile #shahidreza #PublicSector