Twelve minutes into the daily scrum, a sales director interrupts to demand a new report "by Friday." The developers look at the project manager. On the 2026 PMP exam, that pause is the question. Not "define a sprint." Not "list the Scrum events." The exam wants to know what you do next — and whether you route the decision to the right person, in the right event, for the right reason.
Roughly 60% of the 2026 exam covers agile and hybrid approaches, and Scrum is the costume most of those questions wear. The definitions are the entry fee. The points are awarded for judgment. If you're still deciding when agile applies at all, start with our agile vs. predictive breakdown, then come back here.
Roles: the exam tests ownership, not job titles
Every Scrum role question is secretly an ownership question. Learn the boundaries and most distractors dissolve.
- Product owner — owns what and in what order. Backlog content, backlog sequence, value decisions. Any option where the project manager, sponsor, or PMO reprioritizes the backlog is almost always wrong.
- Developers — own how and how much. They build the sprint backlog, estimate the work, and decide how to reach the sprint goal. Options where a leader assigns tasks or overrides estimates fail the ownership test.
- Scrum master / servant leader — owns process health. Removes impediments, coaches, protects the team's way of working. Not a task cop, not a status collector.
The reliable heuristic: the stem tempts you to bypass an owner; the correct answer restores the owner. A sponsor pressuring a developer gets redirected to the product owner. A project manager itching to assign work steps back and facilitates.
75 free questions, scored against the new domain weights. No card required.
Events: each one has exactly one job
Scrum's events are feedback loops, and exam questions punish you for using the wrong loop.
- Sprint planning answers "what can we deliver, and how?" The team pulls work; nobody pushes it.
- Daily scrum is the developers replanning their next 24 hours. The moment it becomes a status report to a manager, it's broken — and the exam loves testing whether you notice.
- Sprint review is where stakeholders inspect the increment and the backlog adapts. Feedback belongs here, not in a slide deck emailed later.
- Retrospective is where the team inspects itself. Process problems, quality standards, working agreements — this is their venue.
Wrong-event distractors are everywhere: resolving a team conflict during the review, gathering customer feedback through status reports, fixing a quality escape by adding a sign-off meeting instead of raising it in the retrospective.
Artifacts: one list, one plan, one standard
The product backlog is a single, ordered, living list — never frozen, never duplicated into side lists. The sprint backlog is the developers' plan for the sprint, and they alone adapt it as they learn. The increment must meet the definition of done, which is a quality standard, not a suggestion. We unpack DoD, DoR, and the review/retro split in more depth in our agile artifacts and events guide.
Two exam-style scenarios
Scenario 1. Halfway through a two-week sprint, the sponsor of a retail analytics project asks the project manager to slip a "small" dashboard change into the current sprint because a board meeting moved up. What should the project manager do first?
- A. Add the item to the sprint backlog and inform the developers
- B. Refer the request to the product owner to assess its value against the backlog
- C. Ask the developers to work extra hours so the sprint goal is unaffected
- D. Reject the request because scope cannot change during a sprint
Answer: B. The product owner owns backlog content and order — urgency doesn't change ownership. A bypasses both the product owner and the developers' authority over the sprint backlog. C treats people as schedule buffer. D overstates the rule: the sprint goal is protected, but the product owner can negotiate scope with the developers, and the backlog can always be reordered for the next sprint.
Scenario 2. A project manager new to an agile software team notices the daily scrum has become fifteen minutes of developers reporting progress to her, one at a time. Delivery has been slipping. What should she do?
- A. Shorten the meeting to ten minutes but keep the format
- B. Replace the meeting with written status updates
- C. Re-establish the event as the developers' own planning session and step out of the center
- D. Suspend the daily scrum for a sprint to see whether delivery recovers
Answer: C. The daily scrum exists so developers can inspect progress toward the sprint goal and adapt their plan. Reporting upward is a symptom of lost ownership, and the servant-leader move is to hand the event back. A and B keep the dysfunction in a different shape. D removes the feedback loop instead of repairing it.
How to make this automatic
You can't reason your way through 180 questions in 240 minutes; the ownership and event patterns have to be reflexes. That takes reps against scenarios, not flashcards. ExamElephant's question bank is built for exactly this — start with the 75 free questions, and the retest engine will bring back everything you miss at 3 and 7 days until you've mastered it. For what the questions themselves look like — multiple response, matching, hotspot — see our 2026 question types guide.
Paid passes are coming soon
The full 2,100-question bank, timed 180-question mock exams and unlimited tutoring. Leave your email and we'll tell you the day they open. Unsubscribe anytime. Privacy
FAQ
Do I need to memorize the Scrum Guide to pass the PMP exam?
No. You need to apply roles, events, and artifacts under pressure. If you can predict who acts and in which event for any scenario, you know enough Scrum for the exam.
Do questions say "Scrum master" or "project manager"?
Both. Many stems put a "project manager" inside an agile team. Treat that person as a servant leader: facilitate, remove impediments, and respect the product owner's and developers' ownership.
What if a Scrum scenario mentions a change control board or baselines?
That's a hybrid signal — governance from the predictive world wrapped around agile delivery. The answer usually respects both: backlog decisions stay with the product owner, baseline changes follow change control.
How many Scrum questions will I actually see?
PMI doesn't publish counts per framework. The 2026 ECO puts agile and hybrid at roughly 60% of the exam, and Scrum vocabulary dominates those items, so expect it constantly.