Scrum is the most heavily represented agile framework on the PMP exam. It is not the only one tested, but it is the one most likely to appear in scenario-based questions, and the one where candidates make the most avoidable mistakes.
The challenge for experienced project managers is that Scrum does not map neatly onto traditional PM roles and processes. There is no project manager role in Scrum. There is no formal change control board. There is no detailed requirements document created upfront. If you approach PMP exam questions about Scrum using a predictive project management mindset, you will select wrong answers that feel right.
This guide covers what PMI actually expects you to understand about Scrum for the 2026 PMP exam: the framework structure, the accountability boundaries, every event and artefact, how Scrum questions are constructed, where Scrum and Kanban differ, and the specific mistakes that cost candidates marks.
The Scrum Framework at a Glance
Scrum is a lightweight framework for developing, delivering, and sustaining complex products. It was created by Ken Schwaber and Jeff Sutherland, and its definitive reference is the Scrum Guide (last updated in 2020).
Scrum works in fixed-length iterations called sprints. Each sprint is typically two weeks long, though the Scrum Guide allows anything from one week to one month. During a sprint, the team takes a subset of work from a prioritised backlog, builds it, tests it, and delivers a potentially releasable increment of the product.
The framework is intentionally minimal. It defines three accountabilities (roles), five events (ceremonies), and three artefacts. Everything else, the specific engineering practices, the tools, the reporting formats, is left for the team to decide. This deliberate simplicity is part of what makes Scrum powerful, but it is also what makes it easy to misunderstand. PMI tests whether you understand the framework as defined, not as it is commonly misapplied in organisations.
Three pillars underpin Scrum: transparency (everyone can see the work and its status), inspection (the team regularly examines its progress and process), and adaptation (the team adjusts based on what inspection reveals). Every Scrum event exists to serve one or more of these pillars. If an exam question asks why a particular event matters, the answer almost always connects back to transparency, inspection, or adaptation.
Roles and the Project Manager’s Place in Them
The 2020 Scrum Guide replaced the word “roles” with “accountabilities,” but for PMP exam purposes the concept is the same. Scrum defines three, and only three.
The Product Owner is responsible for maximising the value of the product. They own the product backlog: deciding what goes into it, how items are ordered, and ensuring the backlog is transparent and understood by the team. The product owner is one person, not a committee. They may delegate backlog management tasks, but the accountability stays with them.
For PMP candidates, the product owner is the closest analogue to a project sponsor in terms of value decisions, and the closest analogue to a business analyst in terms of requirements ownership. But the product owner is neither of those roles. They sit inside the Scrum team, not outside it.
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They serve the team by removing impediments, facilitating events, and coaching the organisation on Scrum practices. The Scrum Master is not a project manager with a different title. They have no authority over the team’s work, no control over scope or schedule, and no reporting line to senior management on project status.
The Developers are the people who do the work of creating the increment each sprint. “Developers” in Scrum does not mean software developers exclusively. It means everyone on the team who contributes to building the product, whether that involves coding, testing, design, analysis, or any other discipline.
So where does the project manager fit? In a pure Scrum implementation, the PM role does not exist as a separate position. The responsibilities that a traditional PM would hold are distributed: scope prioritisation goes to the product owner, process facilitation goes to the Scrum Master, and execution decisions go to the self-managing development team.
In practice, and this is relevant for both the exam and real life, many organisations run hybrid models where a project manager coordinates across multiple Scrum teams, manages external dependencies, handles governance reporting, or bridges between agile delivery teams and a predictive portfolio management layer. PMI acknowledges this reality. Exam questions about the PM’s role in agile environments will test whether you understand that the PM should serve, facilitate, and enable rather than direct, assign, and control.
The Five Scrum Events
Scrum defines five events, each with a specific purpose. All five are time-boxed, meaning they have a maximum allowed duration. The PMP exam frequently tests whether candidates understand the purpose of each event and who participates.
The Sprint is the container event. Every other event happens within a sprint. Sprints are fixed in length and run consecutively with no gaps between them. Once a sprint starts, its duration does not change. The sprint goal, agreed upon during sprint planning, gives the team a coherent objective rather than just a list of tasks.
A critical exam point: only the product owner can cancel a sprint, and only if the sprint goal becomes obsolete. This is rare. If the exam presents a scenario where a stakeholder or manager wants to cancel or extend a sprint, the correct answer is almost always that sprints are not cancelled or extended at the request of someone outside the product owner role.
Sprint Planning kicks off each sprint. The team answers three questions: why is this sprint valuable (the sprint goal), what can be delivered (selecting items from the product backlog), and how will the work be done (breaking selected items into tasks). Sprint planning is time-boxed to a maximum of eight hours for a one-month sprint, scaled proportionally for shorter sprints.
The Daily Scrum is a 15-minute daily event for the developers to inspect progress toward the sprint goal and adapt the plan for the day. It is not a status meeting for managers. The Scrum Master ensures it happens but does not run it. The product owner attends only if they are also doing development work. If the exam describes a scenario where a project manager is using the daily Scrum to collect status updates from team members, the correct answer will redirect toward the developers using the event to self-manage.
Sprint Review happens at the end of each sprint. The Scrum team presents the increment to stakeholders, demonstrates what was built, discusses what changed in the environment, and collaborates on what to work on next. The sprint review is not a demo or a sign-off gate. It is a working session where the product backlog is likely to be adjusted based on feedback. Time-box: four hours maximum for a one-month sprint.
Sprint Retrospective closes the sprint. The team inspects how the last sprint went with regard to people, relationships, process, and tools. They identify improvements and commit to at least one actionable change for the next sprint. The retrospective is how Scrum builds continuous improvement into every cycle. Time-box: three hours maximum for a one-month sprint.
Exam questions about Scrum events typically present a situation and ask what the team should do. If the scenario involves stakeholder feedback on the product, the answer points to the sprint review. If it involves team process improvement, the answer points to the retrospective. If it involves day-to-day coordination, the answer points to the daily Scrum. Matching the right event to the right situation is a reliable source of marks.
Scrum Artefacts
Each artefact in Scrum represents work or value, and each has a corresponding commitment that ensures transparency.
The Product Backlog is an ordered list of everything that might be needed in the product. It is never complete. It evolves as the product and the environment evolve. The product owner is accountable for the product backlog, and its commitment is the product goal, which describes the future state of the product and gives the team a long-term objective to plan against.
The Sprint Backlog is the set of product backlog items selected for the sprint, plus the sprint goal and the plan for delivering the increment. It is owned by the developers and updated throughout the sprint as the team learns more about the work. Its commitment is the sprint goal, the single objective that gives coherence to the sprint.
The Increment is the sum of all product backlog items completed during a sprint, combined with the value of all previous increments. Each increment must meet the definition of done, which is the shared standard that describes when work is considered complete. If the definition of done is not met, the item cannot be released or presented at the sprint review.
For PMP exam purposes, pay attention to who owns what. The product owner owns the product backlog. The developers own the sprint backlog. The entire Scrum team shares accountability for the definition of done. Questions that test artefact ownership are common and straightforward if you know these boundaries.
How Scrum Appears in PMP Exam Questions
The PMP exam does not test Scrum theory in isolation. You will not be asked to recite the time-box for sprint planning or list the Scrum values from memory. Instead, Scrum concepts are embedded in situational questions that test judgment.
A typical question pattern: you are given a project scenario where something has gone wrong or a decision needs to be made, and you must choose the best response from four options. The scenario will describe an agile or hybrid environment, and the correct answer depends on understanding how Scrum is supposed to work.
Common themes include: a stakeholder wanting to add scope mid-sprint (correct response: add it to the product backlog for the product owner to prioritise, not interrupt the current sprint). A team struggling with quality (correct response: revisit the definition of done in the retrospective). A project manager trying to assign tasks to developers (correct response: the team self-manages and chooses how to do the work). A conflict between the product owner and stakeholders about priorities (correct response: the product owner has final say on backlog ordering).
The exam rewards candidates who default to the Scrum Guide’s intended design rather than what happens in messy real-world implementations. When in doubt, choose the answer that respects self-management, supports the product owner’s authority over the backlog, and uses Scrum events for their intended purpose.
If you want to test your ability to handle these situational questions under exam conditions, targeted practice with PMP-style scenario questions is one of the most effective preparation methods. The PMP practice exam package includes questions across all three domains, with detailed explanations that show why each answer is or is not correct.
Scrum vs Kanban
Both Scrum and Kanban are tested on the PMP exam, and candidates are expected to understand when each is more appropriate. The differences are structural, not philosophical.
Scrum works in fixed-length sprints with defined start and end points. Work is planned at the beginning of each sprint, and the sprint backlog is generally stable once the sprint begins. Roles and events are prescribed. Scrum is well suited to product development where the team can meaningfully plan and deliver increments of value in regular cycles.
Kanban is a flow-based system with no sprints and no prescribed roles. Work items enter a queue, move through stages (typically visualised on a board), and exit when done. The primary control mechanism is work-in-progress (WIP) limits, which cap how many items can be in any given stage at once. Kanban is well suited to support and maintenance work, operations, and any context where work arrives unpredictably and batching it into sprints would create unnecessary delays.
Hybrid approaches are common and PMI-endorsed. Many teams use Scrum’s sprint structure and ceremonies but add Kanban-style WIP limits and flow metrics to improve visibility. The exam does not insist on purist implementations. It tests whether you can recognise which approach fits a given scenario.
The key distinction for exam questions: if the scenario describes iterative product development with a stable team, Scrum is likely the right framework. If the scenario describes continuous flow work with variable demand, Kanban is likely the better fit. If the scenario describes both, a hybrid approach is the expected answer.
Common Mistakes PMP Candidates Make
These errors appear consistently in practice exams and post-exam feedback from candidates.
Treating the Scrum Master as a project manager. The Scrum Master does not assign work, report project status to management, or make scope decisions. If an exam question presents a Scrum Master doing any of these things, the correct answer will involve redirecting that responsibility to the appropriate accountability (developers for work assignments, product owner for scope).
Assuming the PM assigns tasks in agile. In Scrum, the development team is self-managing. They decide who does what and how. The project manager (where one exists in a hybrid setup) facilitates, removes impediments, and coordinates external dependencies. Answers that involve the PM directing individual task assignments in a Scrum context are almost always wrong.
Confusing the sprint review with a demo. The sprint review is a collaborative working session, not a presentation. Stakeholders provide feedback. The product backlog may be adjusted as a result. If an exam answer frames the review as a one-way demonstration or a formal sign-off checkpoint, it misunderstands the event’s purpose.
Thinking the daily Scrum is a status report. The daily Scrum exists for the developers to coordinate their own work. It is not a reporting mechanism for management. If a scenario describes a manager using the daily Scrum to track progress, the correct response involves re-establishing the event’s self-management purpose.
Ignoring the retrospective. When the exam presents a team struggling with process issues, quality problems, or collaboration breakdowns, the sprint retrospective is almost always part of the correct answer. Candidates who skip past the retrospective and jump to corrective actions like training, staffing changes, or process mandates miss the Scrum-aligned response.
Mixing up who cancels sprints. Only the product owner can cancel a sprint. Not the Scrum Master, not the developers, not a senior manager. This is a specific, testable fact.
Frequently Asked Questions
Does the PMP exam test the Scrum Guide specifically? The PMP exam does not test the Scrum Guide as a standalone reference the way a Professional Scrum Master (PSM) exam would. However, Scrum is the most frequently referenced agile framework in PMP exam content, and PMI’s treatment of Scrum aligns closely with the Scrum Guide. Understanding the framework as the Scrum Guide defines it will prepare you for the agile and hybrid questions on the PMP exam.
Is there a project manager role in Scrum? No. Scrum defines three accountabilities: product owner, Scrum Master, and developers. There is no project manager role. In practice, many organisations retain a PM role alongside Scrum teams, particularly in hybrid environments or scaled implementations. The PMP exam tests whether you understand the formal framework and can identify when PM-like behaviours (assigning tasks, controlling scope) conflict with Scrum principles.
How many Scrum questions are on the PMP exam? PMI does not publish a breakdown by framework. The exam is structured around three domains: People (42%), Process (50%), and Business Environment (8%). Agile and hybrid delivery concepts appear across all three domains rather than in a separate agile section. Expect roughly half the exam to involve agile or hybrid scenarios, with Scrum as the most common framework in those questions. The 2026 Exam Content Outline details exactly which tasks and enablers are tested.
What is the difference between Scrum and agile? Agile is a set of values and principles defined in the Agile Manifesto. Scrum is a specific framework that implements those values through defined roles, events, and artefacts. Agile is the philosophy; Scrum is one way of putting it into practice. Other agile approaches include Kanban, XP (Extreme Programming), and Lean. The PMP exam expects you to understand agile broadly and Scrum specifically.
Should I get a Scrum certification before taking the PMP? It is not required. The PMP exam tests Scrum knowledge at a level that can be covered through PMP study materials without a separate certification. However, if your project experience is entirely in predictive environments, supplementing your PMP preparation with a focused study of the Scrum Guide will strengthen your confidence on agile questions. The 35 contact hours training covers agile and Scrum concepts as part of the People and Process domains.
Scrum is not complicated. It is three accountabilities, five events, and three artefacts. What makes it challenging on the PMP exam is resisting the instinct to apply traditional PM thinking to agile scenarios. Learn the framework as designed, understand why each element exists, and let the principles guide your answers.