PMI has announced the release of the 8th edition of the PMBOK® Guide, expected in fall 2025. A draft version of the standard was recently made available for public review and comments from the professional community. Oleksii Gromyko, Managing Partner at the Bureau, shared his thoughts on the upcoming changes.
When PMI introduced agile practices in the 6th edition of the PMBOK® Guide, it didn’t ease criticism of the standard. Rightfully, many pointed out that the process-heavy structure of the guide didn’t reflect the reality project managers face—uncertainty, shifting stakeholder expectations, and constantly changing priorities.
With the 7th edition, PMI shifted the focus from processes to principles and from knowledge areas to performance domains. In my opinion, this change felt too abrupt. The standard lost the familiar structure that project managers had relied on for years. PMI’s claim that the seventh edition was meant to complement the sixth came as a surprise. Even the later release of the Process Groups: A Practice Guide, intended to bring back process detail, didn’t fully address the issue.
The draft of PMBOK® Guide – Eighth Edition offers a glimpse into the future direction of the standard — and it seems PMI has been listening to the feedback:
Reintegration of Principles and Processes: The new draft brings principles back together with a defined set of processes, restoring a more familiar and practical structure for project managers.
Performance Domains Still Present: While PMI retains the concept of performance domains introduced in PMBOK® 7, these are now more closely aligned with traditional knowledge areas — indicating an evolution rather than revolution.
Clear Distinction Between Project and Product: One of the long-awaited updates is a clearer differentiation between a project and a product.
Definition of Project Success: PMBOK® 8 offers a clear, standardized definition of what constitutes a successful project — something I emphasize in both my trainings and my day-to-day practice.
Streamlined Domains: The total number of domains has been reduced. For a example, communications and stakeholders have been merged, as have quality and scope. Procurement, notably, has been removed altogether.
Outcome-Focused Process Names: The process names have become more results-oriented. For example, “Create Project Charter” is now “Authorize Project Initiation” reflecting a shift toward intent and outcomes rather than just activities.
It’s worth noting that PMBOK® 8 is still a draft and open to community feedback. The final version may still evolve. We’ll be following the updates closely and will share further insights as they emerge.
