7.2 The Scrum Framework
Key Takeaways
- Scrum has three roles: Product Owner (prioritizes backlog), Scrum Master (facilitates and removes impediments), and Developers (self-organize to deliver work)
- Scrum has five events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective
- Scrum has three artifacts: Product Backlog, Sprint Backlog, and Increment — each with a transparency commitment
- Sprints are fixed-length iterations (typically 1-4 weeks) that produce a potentially shippable product increment
- Scrum is founded on empiricism (transparency, inspection, adaptation) and lean thinking
Last updated: March 2026
The Scrum Framework
Scrum is the most popular agile framework, used by approximately 87% of agile practitioners. It is lightweight, simple to understand, and intentionally incomplete — it defines just enough structure to enable teams to deliver value iteratively.
Scrum Foundations
Scrum is founded on empiricism and lean thinking:
Three Pillars of Empiricism
| Pillar | Description |
|---|---|
| Transparency | The process and work must be visible to those performing and receiving the work |
| Inspection | Scrum artifacts and progress must be inspected frequently to detect problems |
| Adaptation | If inspection reveals that aspects of the process deviate, adjustments must be made |
Scrum Roles (The Scrum Team)
The Scrum Team consists of exactly three accountability roles:
Product Owner
| Aspect | Details |
|---|---|
| Primary responsibility | Maximize the value of the product |
| Key activities | Manage the Product Backlog, define and prioritize items, ensure transparency |
| Authority | Final say on what goes into the Product Backlog and its priority |
| Accountability | One person (not a committee); can delegate but remains accountable |
Scrum Master
| Aspect | Details |
|---|---|
| Primary responsibility | Ensure Scrum is understood and enacted |
| Key activities | Coach the team, remove impediments, facilitate events, protect the team |
| Leadership style | Servant leader — serves the team, Product Owner, and organization |
| NOT | A project manager, task assigner, or team boss |
Developers
| Aspect | Details |
|---|---|
| Primary responsibility | Create the product Increment each Sprint |
| Key activities | Plan the Sprint, define the Definition of Done, adapt daily toward the Sprint Goal |
| Structure | Self-organizing — they decide HOW to do the work |
| Size | Typically 3-9 people (small enough for nimbleness, large enough for capability) |
Scrum Events
All events are time-boxed — they have a maximum duration that cannot be exceeded:
1. The Sprint
- Time-box: Fixed length, typically 1-4 weeks (most commonly 2 weeks)
- Purpose: Container for all other events; produce a potentially shippable Increment
- Rules: No changes that endanger the Sprint Goal; quality does not decrease; the Product Backlog is refined as needed
- Cancellation: Only the Product Owner can cancel a Sprint (rare, happens when Sprint Goal becomes obsolete)
2. Sprint Planning
- Time-box: Maximum 8 hours for a 1-month Sprint (proportionally less for shorter Sprints)
- Purpose: Define what can be delivered in the Sprint and how the work will be achieved
- Outputs: Sprint Goal and Sprint Backlog
- Three topics:
- Why is this Sprint valuable? (Sprint Goal)
- What can be done this Sprint? (Selected Product Backlog Items)
- How will the chosen work get done? (Plan for delivering the Increment)
3. Daily Scrum (Daily Standup)
- Time-box: 15 minutes maximum
- Purpose: Inspect progress toward the Sprint Goal and adapt the Sprint Backlog
- Who attends: Developers (Scrum Master and Product Owner attend if they are actively working on items)
- Common format: What did I do yesterday? What will I do today? What impediments do I face?
4. Sprint Review
- Time-box: Maximum 4 hours for a 1-month Sprint
- Purpose: Inspect the Increment and adapt the Product Backlog
- Activities: Demonstrate completed work, gather feedback, discuss what to do next
- Attendees: Scrum Team and invited stakeholders
- NOT: A status meeting or formal sign-off — it is a working session
5. Sprint Retrospective
- Time-box: Maximum 3 hours for a 1-month Sprint
- Purpose: Plan ways to improve quality and effectiveness
- Focus: What went well? What needs improvement? What will we commit to improve?
- Output: Actionable improvement items (may be added to the Sprint Backlog)
- Key principle: The team inspects how the last Sprint went regarding people, relationships, processes, and tools
Scrum Artifacts and Commitments
Each artifact has a commitment that provides transparency:
| Artifact | Description | Commitment |
|---|---|---|
| Product Backlog | Ordered list of everything needed in the product | Product Goal — the long-term objective |
| Sprint Backlog | Set of items selected for the Sprint plus the delivery plan | Sprint Goal — the single objective for the Sprint |
| Increment | The sum of all completed Product Backlog items | Definition of Done — quality standard for completion |
The Definition of Done (DoD)
- A formal description of the state of the Increment when it meets quality measures
- Created by the Scrum Team (or may be part of organizational standards)
- If an item does not meet the DoD, it cannot be released or presented at Sprint Review
- The DoD creates transparency by providing a shared understanding of what "complete" means
Test Your Knowledge
Who is responsible for maximizing the value of the product in Scrum?
A
B
C
D
Test Your Knowledge
What is the maximum time-box for the Daily Scrum?
A
B
C
D
Test Your Knowledge
Which Scrum event focuses on inspecting how the team worked together and planning improvements?
A
B
C
D
Test Your KnowledgeMatching
Match each Scrum artifact with its commitment:
Match each item on the left with the correct item on the right
1
Product Backlog
2
Sprint Backlog
3
Increment
Test Your Knowledge
Who can cancel a Sprint in Scrum?
A
B
C
D