PMP agile and hybrid questions: think like a servant leader
About six in ten PMP items are agile or hybrid, and they appear in all three domains. They are rarely about definitions. They test whether you act like a servant leader, respect the team's events and roles, and tailor the approach to the work.
Why these questions feel hard
PMI's July 2026 outline says approximately 40% of items represent predictive approaches and the remaining 60% are divided between adaptive/agile and hybrid. It also says the approaches are found throughout all three domains, not isolated in one. So an agile scenario can test conflict management (People), backlog prioritization (Process) or how to handle an impediment (Business Environment).
The difficulty is that most wrong options are good actions in a predictive project. Assigning tasks, escalating to a manager, raising a change request or holding a status meeting are all reasonable somewhere. In an agile scenario they are often the wrong move, because the team owns how the work gets done and change flows through the backlog. Read the scenario for its environment first: sprints, a product owner, a backlog or a Kanban board mean agile rules apply.
The servant-leader mindset
Roles: who decides what
| Role | Owns | Common exam trap |
|---|---|---|
| Product owner | The product backlog, its order and the value it delivers; accepts work against acceptance criteria | The project manager reprioritizing the backlog or accepting stories on the product owner's behalf |
| Development team | How the work is done, its estimates, and the sprint backlog it commits to | A manager assigning individual tasks or overriding the team's estimates |
| Scrum master or team facilitator | The process, coaching, removing impediments, keeping events effective | Acting as a task manager or making technical decisions for the team |
| Project manager in a hybrid setting | Integrating plans, governance, stakeholders, risk and budget across predictive and adaptive parts | Imposing a single approach on all the work instead of tailoring it |
Ceremonies and their purpose
| Event | Purpose | What the right answer usually protects |
|---|---|---|
| Sprint or iteration planning | The team selects work from the ordered backlog and plans how to deliver it | The team's own commitment, based on its capacity |
| Daily standup | A short coordination meeting on progress toward the goal and blockers | The timebox; detailed problem-solving happens afterwards |
| Sprint review or demo | Inspect the increment with stakeholders and gather feedback | Real feedback on working product, not slides |
| Retrospective | The team inspects how it works and picks improvements | Holding it every iteration, especially when things are going badly |
| Backlog refinement | Clarify, split and estimate upcoming items | Ready items before planning, refined with the product owner |
Artifacts you must recognize
Hybrid: tailoring is the skill being tested
The July 2026 outline asks project managers to recommend a development approach, predictive, adaptive/agile or hybrid, based on project needs, complexity and magnitude, and to prepare the schedule based on the selected approach. Hybrid questions test that judgment. The right answer usually matches each part of the work to the approach that fits it:
Watch for answers that force one approach onto everything, such as putting regulated hardware into sprints or making a software team produce a fully detailed upfront design. Tailoring is almost always the better choice.
Typical traps on agile and hybrid questions
- 1
Escalating first
In agile scenarios the project manager or team should try to solve the issue first. Escalation is right only when it is beyond the team's authority or efforts have failed.
- 2
Assigning tasks
Self-organizing teams pull work. An option where the project manager assigns stories to individuals is almost always wrong.
- 3
Change control boards for backlog changes
In agile work, change goes to the product owner and the backlog. Formal change control is for baselined, predictive parts of the work.
- 4
Cancelling the retrospective
Being behind is a reason to hold the retrospective, not skip it. Improvement is how the team recovers.
- 5
Extending the sprint or adding work mid-sprint
Timeboxes are fixed. Unfinished work returns to the backlog; new work is prioritized for a later sprint.
- 6
Comparing velocities
Velocity is relative to each team's own estimates, so ranking teams by it is meaningless and harmful.
3 original agile and hybrid examples
Written for this guide, not taken from the course. Click an option; the explanation under every option appears as soon as you do.
During the daily standup, two developers on a Scrum team start a long argument about how to implement a feature, and the meeting runs well over its timebox. Other team members look frustrated. What should the project manager, acting as a servant leader, do FIRST?
- Deciding for the team takes ownership of a technical choice away from a self-organizing team, and it does nothing about the meeting format.
- Correct. The standup is a short coordination event. Moving the detailed discussion to a follow-up keeps it on purpose and lets the people involved solve it themselves.
- Escalation before the project manager or the team has tried to resolve it skips the servant leader's own role.
- Removing a key transparency event punishes the whole team for one overrun and is far out of proportion.
A medical-device project follows a phase-gate plan for the hardware, with regulatory approval milestones, while the companion app team works in two-week sprints. The sponsor asks for one date when the complete product will be ready. What is the BEST approach?
- Regulated hardware with approval gates is a good fit for predictive planning; forcing sprints ignores those constraints.
- The app forecast alone ignores the hardware path, which likely drives the overall date.
- Correct. Hybrid delivery means tailoring: use the schedule for the predictive part, velocity forecasts for the adaptive part, and integrate them with honest uncertainty.
- Agile teams forecast all the time. Refusing to give a date fails the sponsor's legitimate need.
Midway through a sprint, an influential stakeholder asks a developer directly to add a new reporting feature to the current sprint. The developer tells you about it. What should you do NEXT?
- Adding work mid-sprint without the product owner bypasses prioritization and puts the sprint goal at risk.
- Correct. In agile, change is welcome but flows through the product backlog, where the product owner prioritizes it against everything else.
- A change control board is the predictive mechanism; in an agile team the backlog and the product owner manage change.
- Agile does not freeze scope. Rejecting the request outright ignores a possibly valuable idea and damages the stakeholder relationship.
Putting it together
For any agile or hybrid question, run the same three checks. First, identify the environment: predictive, agile or a hybrid mix, and which part of the work the question is about. Second, identify who owns the decision: the product owner, the team, the project manager, or governance. Third, prefer the option that facilitates, protects the team's events and routes change through the right channel before anything that escalates or overrides.
Then practice. Read the PMP exam changes for 2026 for the full picture, schedule your weeks with the PMP study plan, and try 10 free PMP practice questions from the course.
Six in ten items are agile or hybrid
Six full-length PMP mock exams with agile, hybrid and predictive scenarios in all three domains, every option explained.
PMP agile and hybrid FAQ
How many PMP questions are agile or hybrid?
PMI's July 2026 outline says about 40% of items represent predictive approaches and the remaining 60% are divided between adaptive/agile and hybrid. PMI does not publish the split between agile and hybrid within that 60%.
Do I need a Scrum certification for the PMP?
No. You need to understand agile values, roles, events and artifacts well enough to judge scenarios. PMI names the Agile Practice Guide among the texts its item writers cite most often.
Is agile a separate section of the exam?
No. PMI states that predictive, agile and hybrid approaches appear throughout all three domains and are not isolated to any domain or task.
What is the most common mistake on agile PMP questions?
Answering like a traditional manager: assigning tasks, deciding for the team, sending a change to a change control board or escalating before the team has tried to solve the problem.
What does hybrid mean on the PMP?
A deliberate mix of predictive and adaptive practices tailored to the work, such as a phase-gate plan for regulated hardware alongside sprints for software, integrated into one plan.
More guides: PMP exam changes 2026 · PMP formulas cheat sheet · PMP study plan · Free PMP practice questions · all guides