SkarpChapter 13 of 21
Scrum Deep Dive: Roles, Events, Artifacts, and the Product Backlog
Walk through a Scrum sprint from backlog refinement to review and retrospective, and master the terminology and responsibilities that show up again and again on CAPM agile questions.
Scrum in the Agile Landscape
Scrum and Agile
Scrum is a lightweight agile framework for managing complex work when requirements are uncertain and change is frequent. It is one type of adaptive life cycle used on the CAPM exam.
Adaptive Life Cycle Link
An adaptive life cycle is "A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration." Scrum fits this definition.
Empirical Process Control
Scrum is built on transparency, inspection, and adaptation. You make work visible, inspect product and process frequently, and adapt plans and behavior based on what you learn.
Do Not Confuse Scrum With...
Scrum is different from Kanban (continuous flow, WIP limits) and XP (pair programming, TDD, CI). Scrum may use Kanban boards or XP practices, but its core is roles, events, and artifacts.
Scrum Roles and Accountabilities
Product Owner
The Product Owner owns product value and the product backlog: "An ordered list of everything that is known to be needed in the product, managed by the product owner." The PO orders items to maximize value.
Developers
Developers are cross-functional professionals who build the product increment. They self-manage, decide how much work to take into the sprint, and ensure the increment meets the Definition of Done.
Scrum Master
The Scrum Master is a servant-leader who coaches the team in Scrum, facilitates events, and removes impediments. They do not assign tasks or own the schedule like a traditional project manager.
Common Exam Traps
Exam traps: a manager reorders the backlog (should be PO), a Scrum Master assigns tasks (violates self-management), or the team skips retrospectives (weakens inspection and adaptation).
Scrum Events Overview: The Sprint Container
The Sprint
A Sprint is a fixed-length iteration (1–4 weeks) in which the team creates at least one usable increment that meets the Definition of Done. It is the container for all other Scrum events.
Four Events Inside the Sprint
Inside each sprint: 1) Sprint Planning, 2) Daily Scrum, 3) Sprint Review, 4) Sprint Retrospective. These events support inspection and adaptation of work and process.
Timeboxing and Discipline
Scrum events are timeboxed to limit cost and drive focus. Skipping or extending them excessively reduces transparency and weakens empirical control.
Sprint Cancellation
Only the Product Owner can cancel a sprint, and only if the sprint goal becomes obsolete. This is rare but is a common CAPM exam detail.
Scrum Artifacts: Product Backlog, Sprint Backlog, Increment
Product Backlog
The product backlog is "An ordered list of everything that is known to be needed in the product, managed by the product owner." It is dynamic and ordered to maximize value.
Sprint Backlog
The sprint backlog is the set of product backlog items selected for the sprint plus a delivery plan. Developers own and update it as a real-time view of their work toward the sprint goal.
Increment
An increment is the sum of all completed product backlog items. It must be usable and meet the Definition of Done. Multiple increments can exist; all must be integrated by sprint end.
Common Confusion
Do not confuse the product backlog with a predictive requirements traceability matrix or a basic to-do list. It is value-ordered, evolving, and owned by the Product Owner.
Definition of Done vs Acceptance Criteria
Definition of Done
The Definition of Done is a shared quality bar for all work. It covers things like testing, integration, documentation, and security. If an item does not meet the DoD, it is not Done.
Acceptance Criteria
Acceptance criteria are "A set of conditions that is required to be met before deliverables are accepted." They are specific to a backlog item and describe expected behavior.
How They Interact
For a backlog item to be truly Done and part of the increment, it must satisfy its acceptance criteria and the team’s Definition of Done. Both must be met.
Exam Trap
If a story meets acceptance criteria but skips required integration tests in the DoD, it is not Done in Scrum and should not be counted in the increment.
Walking a Sprint: From Backlog Refinement to Increment
Backlog Refinement
Before the sprint, the Product Owner and Developers refine a high-level item like "Course Chat" into smaller items with clear acceptance criteria, estimates, and ordering in the product backlog.
Sprint Planning
The team sets a Sprint Goal, then Developers select top product backlog items they believe they can complete while meeting the Definition of Done. These items form the sprint backlog.
Executing the Sprint
Each day, Developers hold a Daily Scrum to inspect progress and adapt their plan. Items that satisfy both acceptance criteria and the Definition of Done are added to the increment.
Review and Retrospective
At Sprint Review, the team demos the increment and updates the product backlog based on feedback. At the Retrospective, they inspect their process and choose improvements for the next sprint.
Daily Scrum: Planning and Inspection, Not Status Reporting
Purpose of Daily Scrum
The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the sprint backlog and plan for the next 24 hours.
Who and What
Developers are required participants. Scrum Master and Product Owner may attend. The focus is on the work and plan, not on reporting status to a manager.
Format and Flow
Teams often use three questions (yesterday, today, impediments), but any structure is fine if it inspects progress toward the Sprint Goal and updates the plan.
Anti-Patterns and Fixes
If the Daily Scrum becomes a status report or long problem-solving session, the Scrum Master should coach the team to refocus on short, goal-centered inspection and planning.
Sprint Review and Retrospective: Inspect and Adapt
Sprint Review
The Sprint Review inspects the increment with stakeholders and adapts the product backlog. It is a collaborative working session, not just a demo.
Sprint Review Activities
In the review, the team shows Done work, discusses changes in context, gathers feedback, and adjusts upcoming backlog items and priorities.
Sprint Retrospective
The Sprint Retrospective inspects how the sprint went for people, process, and tools. Only the Scrum Team attends, and they decide concrete improvements.
Link to Empiricism
Review and Retrospective are core inspection and adaptation points: one for the product and backlog, one for the process and teamwork.
Thought Exercise: Ordering the Product Backlog for Value
Imagine you are the Product Owner for an online learning platform preparing students for CAPM. Your product backlog includes these high-level items:
- Add a discussion forum
- Improve video playback quality
- Implement spaced review reminders
- Add dark mode UI
Assume:
- Students complain that they forget to review material and fall behind.
- A few students mention video buffering issues, but most are okay.
- Dark mode is a frequent “nice to have” request.
- Instructors say they need a way to answer student questions.
Your task
- Order the items from top (most valuable now) to bottom. Write down your ordering.
- For each item, list one reason why it is higher or lower.
- Identify one exam-style trap where someone orders by technical convenience or individual utilization instead of value.
Then compare your reasoning to this guidance:
- A value-focused ordering might prioritize spaced review reminders first, because they directly improve learning outcomes and course completion.
- Next, discussion forum may come, enabling instructor-student interaction and clarifications, which can reduce support tickets and increase satisfaction.
- Improve video playback quality might follow, especially if analytics show many students drop off on slow networks.
- Dark mode may be last if it is mostly cosmetic and does not significantly affect outcomes right now.
Exam trap example: A developer says, “Let’s do dark mode first because it’s fun and I already know how to do it.” That is prioritizing by technical convenience, not by business value or outcomes.
Quiz 1: Scrum Roles, Events, and Artifacts
Test your understanding of core Scrum mechanics.
Which statement best describes the Product Owner’s accountability in Scrum?
- Assigning tasks to Developers and ensuring they meet their individual deadlines.
- Managing the product backlog as an ordered list of everything that is known to be needed in the product and ordering it to maximize value.
- Facilitating all Scrum events and removing impediments for the team.
- Conducting the Daily Scrum and collecting status reports from each team member.
Show Answer
Answer: B) Managing the product backlog as an ordered list of everything that is known to be needed in the product and ordering it to maximize value.
The Product Owner is accountable for the product backlog, which is "An ordered list of everything that is known to be needed in the product, managed by the product owner." They order it to maximize value. Assigning tasks and running Daily Scrums are not PO responsibilities; those conflict with Developers’ self-management and the Scrum Master’s servant-leader role.
Quiz 2: Daily Scrum and Definition of Done
Check how well you can spot common Scrum misconceptions.
During a Daily Scrum, a manager listens while each Developer reports what they did yesterday and what they will do today. The manager then reassigns tasks and extends the meeting to 45 minutes to solve design issues. What is the BEST Scrum-based response?
- This is fine because the manager is ensuring the team stays on schedule.
- The Scrum Master should coach the manager and team that the Daily Scrum is a short planning and inspection event for Developers, not a status or problem-solving meeting.
- The Product Owner should take over the Daily Scrum and prioritize tasks in real time.
- Developers should stop attending the Daily Scrum if the manager is present.
Show Answer
Answer: B) The Scrum Master should coach the manager and team that the Daily Scrum is a short planning and inspection event for Developers, not a status or problem-solving meeting.
The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan. It is not a status meeting or design workshop. The Scrum Master should coach everyone to refocus the event on Developers’ self-management and keep problem-solving in follow-up discussions.
Key Scrum Terms Review
Use these flashcards to reinforce the core Scrum vocabulary that appears frequently on CAPM agile questions.
- Product backlog (canonical definition)
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- Acceptance criteria (canonical definition)
- A set of conditions that is required to be met before deliverables are accepted.
- Definition of Done
- A shared, explicit quality standard for all work; an item that does not meet the Definition of Done is not considered Done and cannot be part of the increment.
- Increment
- The sum of all completed product backlog items; it must be usable and meet the Definition of Done at the end of each sprint.
- Sprint Backlog
- The set of product backlog items selected for the sprint, plus a plan for delivering them; owned and updated by Developers.
- Daily Scrum
- A 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours; it is not a status meeting.
- Sprint Review
- End-of-sprint event where the Scrum Team and stakeholders inspect the increment and adapt the product backlog based on feedback and changes.
- Sprint Retrospective
- End-of-sprint event where the Scrum Team inspects how they worked (people, process, tools) and plans improvements for the next sprint.
- Product Owner
- Scrum role accountable for maximizing product value and managing the product backlog, including ordering items.
- Scrum Master
- Servant-leader who coaches the Scrum Team and organization in Scrum, facilitates events as needed, and removes impediments without assigning tasks.
Key Terms
- Sprint
- A fixed-length iteration, usually 1–4 weeks, that contains all Scrum events and results in at least one usable increment.
- Increment
- The sum of all completed product backlog items that meets the Definition of Done at the end of a sprint.
- Developers
- Scrum Team members who are committed to creating any aspect of a usable increment each sprint.
- Daily Scrum
- A 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours.
- Scrum Master
- Scrum role that serves as a servant-leader, coaching the team and organization in Scrum and removing impediments.
- Product Owner
- Scrum role accountable for maximizing product value and managing and ordering the product backlog.
- Sprint Review
- An event at the end of the sprint to inspect the increment with stakeholders and adapt the product backlog.
- Sprint backlog
- The set of product backlog items selected for the sprint, plus a plan for delivering them; owned by Developers.
- Product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- Definition of Done
- A shared, explicit quality standard for all work that determines whether a product backlog item or increment is complete.
- Acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- Sprint Retrospective
- An event at the end of the sprint for the Scrum Team to inspect their process and plan improvements.