The Single Biggest Surprise for PMP Candidates
If you have spent your career managing projects with Gantt charts, work breakdown structures, and change control boards, the current PMP exam will surprise you. Approximately half the exam — PMI's stated intent from the 2021 ECO — covers agile and hybrid project management.
This is not a minor adjustment. A project manager with fifteen years of waterfall experience can find themselves facing ninety questions on Scrum ceremonies, Kanban flow, servant leadership in agile teams, and hybrid delivery models. Candidates who prepare only for traditional project management are likely to score below target on a substantial portion of the exam.
This post covers what the agile content actually includes, how PMI frames agile questions, and the most effective preparation approach.
What the 2021 ECO Change Actually Means
Before the 2021 ECO update, the PMP was primarily a predictive project management exam. Agile content existed but was a modest proportion. The 2021 update reflected PMI's recognition that most real-world projects are delivered using hybrid or agile approaches, and that a project management credential that did not test those approaches was becoming increasingly irrelevant.
The result: agile and hybrid content is now distributed across all three exam domains (People, Process, Business Environment). There is no separate "agile section." An agile question is just as likely to appear as a People domain leadership question as it is as a Process domain question about sprint planning.
This distribution matters for your preparation. You cannot treat agile as a separate topic to cover in one block. You need to integrate agile thinking into your understanding of every domain.
Scrum: The Core Framework to Know
Scrum is the most heavily tested agile framework on the PMP exam. You do not need to be a certified Scrum Master, but you do need a thorough working knowledge of:
Roles
Product Owner: Accountable for maximising the value of the product. Owns and prioritises the Product Backlog. Represents stakeholder and customer needs. The PO makes decisions about what gets built and in what order.
Scrum Master: A servant-leader who facilitates the Scrum process, removes impediments, and helps the team and organisation apply Scrum effectively. The Scrum Master is not a project manager — they do not assign work or direct the team.
Development Team (Developers): The cross-functional team responsible for delivering the Increment. Self-organising — the team decides how to do the work, not the Scrum Master or Product Owner.
Events
Sprint: A time-boxed iteration of one to four weeks during which the team delivers a potentially releasable Increment of the product.
Sprint Planning: The Scrum event that kicks off each Sprint. The team selects items from the Product Backlog and creates a plan for the Sprint (the Sprint Backlog).
Daily Scrum: A 15-minute daily event for the Development Team to inspect progress toward the Sprint Goal and adapt the plan as needed. Not a status meeting for management — it is for the team.
Sprint Review: Held at the end of the Sprint. The team demonstrates the Increment to stakeholders and gathers feedback. The Product Backlog is updated based on this feedback.
Sprint Retrospective: Held after the Sprint Review. The team inspects its own process and identifies improvements for the next Sprint. This is about how the team works, not what they built.
Artefacts
Product Backlog: An ordered list of everything that might be needed in the product. Maintained and prioritised by the Product Owner.
Sprint Backlog: The set of Product Backlog items selected for the Sprint, plus a plan for delivering the Increment.
Increment: The sum of all completed Product Backlog items during a Sprint. Must meet the Definition of Done.
Definition of Done (DoD): A shared understanding of what it means for work to be complete. Ensures quality and consistency across Sprints.
Kanban: What PMI Tests
Kanban appears less frequently than Scrum on the PMP exam but is still testable. The core concepts:
WIP limits (Work in Progress limits): Kanban systems limit how many items can be in progress at once in each workflow stage. WIP limits prevent bottlenecks, reduce multitasking, and improve flow.
Visualisation: Kanban boards make work visible — what is to do, what is in progress, and what is done. This transparency enables the team and stakeholders to understand system state immediately.
Pull-based flow: Work items are pulled into a stage when capacity exists, rather than pushed by a manager. Teams take on new work when they have capacity for it.
Flow metrics: Cycle time (how long a single item takes from start to finish) and throughput (how many items are completed per time period) are the primary Kanban metrics.
On the PMP exam, Kanban questions typically involve scenarios where a team is struggling with overload, context-switching, or unpredictable delivery times. The correct answer often involves introducing WIP limits or improving flow visibility.
Hybrid Projects: The Reality PMI Tests
Most real projects are neither purely agile nor purely predictive. They combine elements of both — perhaps using agile for software development while managing hardware procurement, regulatory compliance, or vendor contracts with predictive methods.
PMI tests hybrid scenarios extensively because this is the reality of project management in large organisations. Common hybrid scenarios on the exam:
- A software project uses Scrum for development but needs a predictive approach for procurement and budget management.
- A construction project with a fixed-scope, fixed-price contract uses agile techniques for internal team coordination.
- A programme with multiple workstreams uses agile on some and predictive on others, with integration points managed at the programme level.
For hybrid questions, the key skill is recognising which approach is appropriate for which part of the work, and how to manage the interfaces between agile and predictive components.
How PMI Frames Agile Questions
PMI agile questions are almost always situational — they describe a scenario and ask what the project manager or team should do. Understanding PMI's preferred answer logic for agile scenarios is critical.
PMI's agile worldview: PMI assumes a servant-leader model for project managers in agile contexts. The PM facilitates, removes impediments, and enables the team — they do not direct work, assign tasks, or make decisions that belong to the team or Product Owner.
Common PMI-preferred answers in agile scenarios:
- When a team member is underperforming: facilitate a team conversation, not a performance review.
- When scope is requested mid-sprint: add it to the Product Backlog for consideration in the next Sprint, not directly to the current Sprint.
- When stakeholders want status updates: invite them to the Sprint Review, don't create a separate reporting mechanism.
- When the team is struggling with a process problem: facilitate a retrospective, don't impose a solution.
- When there is a conflict between a team member and the Product Owner: the Scrum Master facilitates resolution, the PM does not override the team.
The Agile Practice Guide
PMI's Agile Practice Guide is the definitive source for agile content on the PMP exam. It is co-authored by PMI and the Agile Alliance and is included free with your PMP exam application.
Read the Agile Practice Guide as a separate, standalone document — not as an appendix to the PMBOK Guide. It is where PMI's agile thinking is most directly expressed, and it is the source document for the agile questions on the exam.
Priority sections:
- Chapter 2: Introduction to agile (mindset, values, principles)
- Chapter 3: Life cycle selection (when to use predictive, agile, hybrid)
- Chapter 4: Implementing agile (team composition, servant leadership, building an agile environment)
- Chapter 5: Serving the agile team as a project manager
Preparing for Agile PMP Questions
The most effective preparation for agile content is active practice with situational questions — not reading, which can give a false sense of familiarity.
Aim to work through at least 200 agile and hybrid practice questions across all three domains. Pay particular attention to:
- Questions involving the Scrum Master role and what it does and does not include
- Questions about Product Backlog management and Sprint planning decisions
- Questions where a traditional PM instinct conflicts with an agile approach (e.g., wanting to add scope mid-sprint)
- Questions about hybrid scenarios and which approach fits which context
Practise PMP agile and people domain questions on Got PMP. The agile content in the question bank covers Scrum, Kanban, hybrid approaches, and the servant-leader mindset that PMI expects across all three domains.
One Mindset Shift That Matters
If your project management experience has been primarily predictive, the single most useful mindset shift for the agile portion of the exam is this: the project manager's job in agile is to create conditions, not to control outcomes.
On the PMP exam, this plays out consistently. The PM facilitates, the team decides. The PM removes obstacles, the team owns the work. The PM serves the team, not the other way around. When in doubt between an answer that puts the PM in charge and one that empowers the team, PMI's preferred answer is almost always the one that empowers the team.
Build this thinking through practice, not just reading. The pattern recognition that exam situational questions require only comes from encountering many scenarios and working out the PMI-preferred response.