Facilitated By TJ Badru.

Part 3 of the Beyond Agile series. TJ picks up from Tox’s Part 2, moving into the structural shift behind the vocabulary: how the global project management standard itself changed.

Past editions of the PMBOK were a “process engine” — predictive phases, rigid deliverables, and knowledge areas, where success meant meeting project requirements. PMBOK 7 replaced that with a “principles engine”: 12 guiding principles, 8 performance domains, and outcomes, designed for the full value delivery landscape. This session also covers the Value Delivery System — how projects sit inside programs, portfolios, and ultimately operations, and why a project succeeding in isolation doesn’t guarantee the enterprise strategy it was meant to serve actually gets realized.

Learning Objectives

Understand the shift from the Process Engine (PMBOK 6 and earlier) to the Principles Engine (PMBOK 7).
Learn the structure of the Value Delivery System: enterprise strategy → portfolios → programs → projects → operations.
Recognize why a feedback loop from operations back to strategy is essential — without it, teams optimize for delivery speed, not business impact.
Connect this structural view back to the outcomes vocabulary from Part 2.

Who Should Attend?

Scrum Masters, Product Owners, Agile Coaches, and Project/Program Managers who want to understand how the broader PM profession has evolved — and why it matters even for Scrum-based teams.

Key Takeaways

A clear picture of what changed in PMBOK 7 and why.
Understanding of how individual projects connect to enterprise strategy through the Value Delivery System.
Groundwork for Part 4: how organizations are restructuring around this shift.