Scrum
Introduction: Why This Matters
Scrum is the most widely used Agile framework, making it a cornerstone for both PMP exam preparation and real-world practice. It provides a structured yet flexible approach to delivering value through short, time-boxed iterations known as sprints.
On the PMP exam, Scrum is frequently referenced in situational questions, often testing whether you understand roles, events, and artifacts. In practice, Scrum helps teams deliver usable increments quickly, adapt to feedback, and build trust with stakeholders through transparency and inspection.
Purpose and Objectives
Primary Purpose: To provide a lightweight framework for delivering complex projects iteratively and incrementally.
Key Objectives:
- Define Scrum and its core characteristics.
- Identify the three Scrum roles, five Scrum events, and three Scrum artifacts.
- Explain the purpose of sprints and how value is delivered incrementally.
- Apply Scrum concepts to exam scenarios.
- Recognize common misunderstandings of Scrum in practice.
Overview
Scrum is a lightweight Agile framework that helps teams deliver value in small increments through structured roles, events, and artifacts.
- Iteration Model: Work is delivered in time-boxed sprints (typically 1–4 weeks).
- Value Delivery: Each sprint produces a usable increment that can be reviewed and improved.
Characteristics
- Iterative and incremental: Value is delivered in small, usable pieces over time.
- Time-boxed cadence: Events occur on a consistent rhythm, anchored by the sprint.
- Defined roles and accountability: Clear ownership for backlog, facilitation, and delivery.
- Transparency, inspection, adaptation: Work is visible, reviewed frequently, and adjusted based on feedback.
Practical Example
Context: A healthcare software company develops a patient portal using Scrum.
Activities:
- Product Owner: Works with doctors and patients to prioritize backlog items.
- Development Team: Selects features for a 2-week sprint.
- Daily Scrum: Surfaces a blocker with a third-party API, which the Scrum Master helps remove.
- Sprint Review: Demonstrates a working login feature to stakeholders and collects feedback.
- Sprint Retrospective: Identifies the need for better test automation.
Outcome: Stakeholders see tangible progress every two weeks, refining requirements early and reducing delivery risk.
Common Pitfalls
Pitfall Category One
- Pitfall: Treating the Scrum Master like a project manager who directs the team.
- Prevention: Keep the Scrum Master focused on facilitation, removing impediments, and coaching Scrum adoption.
Pitfall Category Two
- Pitfall: Skipping retrospectives or treating them as optional.
- Prevention: Use retrospectives to drive continuous improvement, even when the sprint was “successful.”
Pitfall Category Three
- Pitfall: Overloading sprints with more work than the team can realistically complete.
- Prevention: Base commitments on capacity and historical velocity, then adjust scope, not time.
Pitfall Category Four
- Pitfall: Confusing backlog ownership and allowing multiple people to reprioritize.
- Prevention: Protect single ownership: the Product Owner is the sole authority for prioritization.
Sensei Tip : When you are stuck between two answers, choose the one that preserves Scrum’s time-box and increases transparency. In Scrum, you adjust scope and expectations, not the sprint length.
Exam Alert : The exam loves to bait you into extending a sprint to “finish the work.” In Scrum, sprints are fixed. Unfinished work returns to the product backlog.
Exam Lens
Patterns on the PMP Exam:
- Situational role questions: Who owns backlog prioritization? The Product Owner.
- Event purpose questions: Which ceremony gathers stakeholder feedback on the increment? Sprint Review.
- Principle application: Adaptation happens through feedback loops and changes to future backlog and sprint plans.
Sample Question
Question: During a sprint, the team realizes it cannot complete all planned work. What should the Scrum Master do?
- Extend the sprint to complete the work.
- Remove incomplete work and return it to the product backlog.
- Ask the Product Owner to reassign the work to another team.
- Cancel the sprint and restart planning.
Correct Answer: B. Remove incomplete work and return it to the product backlog. Scrum sprints are never extended. Work not completed returns to the backlog for future prioritization.
Quick Recap Table
| Element | Purpose | Exam Watch Point |
|---|---|---|
| Product Owner | Prioritizes backlog | Sole backlog authority |
| Scrum Master | Facilitates Scrum | Not a project manager |
| Development Team | Builds increment | Self-organizing |
| Sprint Planning | Define sprint work | Team plus Product Owner collaborate |
| Daily Scrum | Sync work daily | 15 minutes max |
| Sprint Review | Gather feedback | Stakeholders present |
| Sprint Retrospective | Process improvement | Must not be skipped |
Key Takeaways
- Scrum is the most widely used Agile framework.
- It is built on roles, events, and artifacts that promote transparency, inspection, and adaptation.
- The Product Owner owns the backlog, the Scrum Master facilitates, and the Development Team delivers.
- Sprints are time-boxed and never extended.
- On the exam, expect questions that test accountability, event purpose, and feedback loops.
Next Step
With Scrum explained, we will now move into Kanban, another Agile framework that emphasizes visualizing work and managing flow.