Scrum Framework Explained for PMP Candidates: Roles, Events, and Artifacts

Why PMP Candidates Must Understand Scrum

Scrum is the most widely adopted agile framework in the world, and PMI expects PMP candidates to understand it thoroughly. While the PMP exam is framework-agnostic — it doesn't test Scrum certification material — it regularly presents scenarios set in Scrum environments. You need to recognize Scrum roles, events, and artifacts and understand how they relate to broader project management principles.

The Three Scrum Roles

Product Owner

The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. Key responsibilities include:

Managing and ordering the Product Backlog
Clearly expressing backlog items
Making sure the team understands items to the level needed
Representing stakeholder interests and making scope decisions

On the PMP exam, watch for questions about who decides what goes into the sprint (the team pulls work, but the Product Owner sets priorities) and who accepts completed work (the Product Owner, based on the Definition of Done and acceptance criteria).

Scrum Master

The Scrum Master serves the team by removing impediments, facilitating events, and coaching the organization in Scrum adoption. This is a servant-leader role, not a project manager role. The Scrum Master does not assign tasks or manage the team's workload.

PMP questions may test whether you understand the difference between a Scrum Master and a traditional project manager. When a question describes removing obstacles and coaching, think servant leadership.

Development Team

The Development Team (or Developers, in newer Scrum terminology) is self-organizing and cross-functional. They decide how to accomplish the work, while the Product Owner decides what to work on. Teams are typically 3-9 members.

The Five Scrum Events

The Sprint

A Sprint is a time-boxed iteration, typically 1-4 weeks, during which the team creates a potentially shippable product increment. Sprints are consistent in length throughout a project. No changes should be made that endanger the Sprint Goal.

Sprint Planning

The entire Scrum Team collaborates to plan the upcoming sprint. The team selects items from the Product Backlog and creates a Sprint Goal. For a one-month sprint, Sprint Planning is time-boxed to 8 hours.

Daily Scrum (Daily Standup)

A 15-minute time-boxed event for the Development Team to synchronize activities and plan the next 24 hours. The Scrum Master ensures it happens but the Development Team conducts it.

Sprint Review

At the end of the sprint, the team demonstrates the increment to stakeholders and gathers feedback. This is a collaborative working session, not a formal presentation. The Product Backlog may be adjusted based on feedback.

Sprint Retrospective

The team inspects how the last sprint went regarding people, relationships, processes, and tools. The team identifies improvements and creates a plan for implementing them. This event is about continuous improvement — one of agile's core principles.

The Three Scrum Artifacts

Product Backlog — An ordered list of everything needed in the product, maintained by the Product Owner
Sprint Backlog — The set of Product Backlog items selected for the Sprint, plus a plan for delivering them
Increment — The sum of all completed Product Backlog items during a Sprint, plus all prior increments

How PMI Tests Scrum on the PMP Exam

Expect scenario-based questions that test your understanding of Scrum principles, not just vocabulary. For example:

"A stakeholder wants to add an urgent feature mid-sprint. What should the project manager do?" (Protect the Sprint Goal; work with the Product Owner to prioritize it for the next sprint.)
"The team consistently fails to complete all sprint backlog items. What should happen?" (Discuss in the retrospective; the team may be overcommitting and should adjust velocity.)

Practice these scenario questions regularly with PMPprep's exam simulator to build your instincts for Scrum-based situations.