SkarpChapter 15 of 21
Scrum Theory in Action: Empiricism Across All Events and Artifacts
Walk through a full Sprint and pinpoint how transparency, inspection, and adaptation appear in each event and artifact, strengthening your ability to reason through tricky theory questions.
Empiricism and Lean Thinking: Setting the Stage
Scrum's Foundation
Scrum today is still based on one key idea: Scrum is founded on empiricism and lean thinking. Every event and artifact is designed to support this.
Empirical Process Control
Empiricism means we base decisions on evidence and observation, not guesswork. The three pillars are: transparency, inspection, and adaptation.
Lean Thinking
Lean thinking adds focus on reducing waste and improving flow of value: small batches, limited work in progress, and continuous improvement.
Exam Shortcut
Options that increase visibility, shorten feedback loops, or encourage small experiments usually align with Scrum. Options that lock in rigid plans or hide problems usually do not.
Whole Sprint as an Empirical Container
Sprint as Container
The Sprint is the container for all Scrum events. Sprints are the heartbeat of Scrum, where ideas are turned into value. Each Sprint is a short experiment.
Sprint-Level Transparency
Transparency across the Sprint comes from a clear Product Goal, Sprint Goal, and Definition of Done, plus visible Product Backlog, Sprint Backlog, and Increment.
Sprint-Level Inspection
Progress toward the Sprint Goal is inspected daily; the Increment and Product Goal progress are inspected at Sprint Review; ways of working at Sprint Retrospective.
Sprint-Level Adaptation
The Sprint Backlog evolves as Developers learn. The Product Backlog and working practices are adapted based on feedback from Increment and Retrospective.
Exam Signal
In questions, adapting the plan within a Sprint is good empiricism; frequently changing the Sprint Goal itself usually signals a problem.
Sprint Planning: Starting the Empirical Experiment
Purpose of Sprint Planning
Sprint Planning shapes the next experiment: Why is the Sprint valuable? What can be done? How will the work get done within the timebox?
Key Artifacts and Commitments
Sprint Planning uses the Product Backlog and produces a Sprint Backlog, anchored by a Sprint Goal, the single objective for the Sprint.
Transparency in Planning
PO shares Product Goal and ordering; Developers share capacity and constraints; Definition of Done and acceptance criteria are clarified.
Inspection in Planning
The team inspects Product Backlog, constraints, risks, and assumptions about effort and value to decide what is realistic and worthwhile.
Adaptation in Planning
They adapt by choosing the most valuable PBIs, crafting a focused Sprint Goal, and creating an initial but flexible plan for achieving it.
Exam Trap
Sprint Planning does not produce a fixed, unchangeable plan. The Sprint Goal should be stable; the plan is expected to evolve.
Example: Planning a Sprint in a Complex Environment
Scenario Overview
A team builds a recommendation engine. Product Goal: increase weekly watch time by 20% through personalized recommendations.
Transparency at Planning
PO shares analytics and ordered Product Backlog items. Developers share reduced capacity due to support work.
Inspection at Planning
The team inspects backlog items against the Product Goal and analytics, realizing data quality is a bigger issue than algorithm complexity.
Adaptation at Planning
They adapt by choosing a Sprint Goal: validate whether explicit ratings improve relevance, and select PBIs aligned with this experiment.
Lean Slice of Work
Instead of a full algorithm overhaul, they build a lightweight ratings feature and simple metrics, minimizing waste and maximizing learning.
Exam Takeaway
Look for answers that emphasize learning through a small, valuable Increment rather than big-bang, speculative builds.
Daily Scrum: Micro-Inspection and Adaptation
Purpose of Daily Scrum
Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours.
Transparency at Daily Scrum
The Sprint Backlog state is visible: what is in progress, done, or blocked; progress toward the Sprint Goal is clear to all Developers.
Inspection at Daily Scrum
Developers inspect what moved toward Done, new risks, and bottlenecks, comparing actual progress with their plan.
Adaptation at Daily Scrum
They adapt by re-ordering work, swarming on critical items, and adjusting scope of lower-value work to protect the Sprint Goal.
Lean Aspect
Daily Scrum reduces waiting and misalignment, encouraging small batches and finishing work instead of just starting more.
Exam Traps
Daily Scrum is not a status report to managers or PO, not optional, and not locked to a specific question format.
Sprint Review: Inspecting the Increment and Product Direction
Purpose of Sprint Review
Sprint Review brings the Scrum Team and stakeholders together to inspect the Increment and adapt the Product Backlog and product direction.
Key Artifacts
The Review centers on the Increment, a concrete stepping stone toward the Product Goal, and the Product Backlog, an emergent, ordered list.
Transparency at Review
A usable Increment that meets the Definition of Done is shown. Progress toward the Product Goal and the Product Backlog ordering are visible.
Inspection at Review
Participants inspect what was completed, how it performs, and any market, user, or technical changes that affect the product.
Adaptation at Review
The Product Owner adapts the Product Backlog; the team adjusts expectations and next steps based on real feedback and data.
Exam Trap
Sprint Review is not just a demo or acceptance ceremony; it is a collaborative working session to inspect and adapt product direction.
Sprint Retrospective: Inspecting and Adapting the System of Work
Purpose of Retrospective
The Sprint Retrospective focuses on the Scrum Team and its system of work, aiming to improve how they work in future Sprints.
Transparency at Retro
Team members openly share observations about collaboration, quality, tools, and impediments, often supported by simple metrics.
Inspection at Retro
The team inspects how well they worked toward the Sprint Goal and how effectively they applied empiricism and lean thinking.
Adaptation at Retro
They adapt by updating working agreements, refining Definition of Done, and planning concrete experiments for the next Sprint.
Lean and Exam Angle
Retrospectives drive continuous improvement and waste reduction. On exams, skipping or deferring improvements usually conflicts with Scrum.
Artifacts and Commitments: Making Empiricism Possible
Artifacts and Commitments
Each Scrum artifact has a commitment: Product Backlog–Product Goal, Sprint Backlog–Sprint Goal, Increment–Definition of Done.
Product Backlog & Product Goal
Product Backlog is an emergent, ordered list to improve the product. Product Goal describes a future state to plan against.
Sprint Backlog & Sprint Goal
Sprint Backlog holds the Sprint Goal (why), selected PBIs (what), and plan (how). The Sprint Goal is the single objective for the Sprint.
Increment & Definition of Done
An Increment is a concrete stepping stone toward the Product Goal. Definition of Done describes the quality state required for the Increment.
Empiricism and Lean
These commitments make progress visible, enable honest inspection, and reduce waste by clarifying direction, focus, and quality.
Thought Exercise: Predictive vs Empirical Responses
How to Use This Exercise
Read each scenario, pick an option in your head, then compare with the empirical answer. Focus on the reasoning, not memorizing letters.
Scenario 1: Mid-Sprint Change
A big customer asks for a new feature mid-Sprint. Which option best fits Scrum: cancel, negotiate around the Sprint Goal, or refuse all change?
Scenario 1: Empirical Answer
Option B is empirical: keep the Sprint Goal stable, adapt the plan if possible, otherwise place the new request into the Product Backlog.
Scenario 2: Estimation Accuracy
Estimates have been off. Should the team add heavy analysis, reject estimates, or accept uncertainty and improve feedback loops?
Scenario 2: Empirical Answer
Option B again: acknowledge complexity, keep estimating but focus on faster learning and adaptation, not illusion of perfect prediction.
Quiz 1: Mapping Empiricism to Events
Check your understanding of how empiricism shows up in Scrum events.
Which option best describes the main empirical purpose of the Daily Scrum?
- To allow the Product Owner to accept or reject completed Product Backlog items.
- To inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours.
- To report individual status updates to the Scrum Master so they can update management.
- To re-estimate all remaining Product Backlog items and update the release plan.
Show Answer
Answer: B) To inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours.
The Daily Scrum is for Developers to inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours. It is not about acceptance (Sprint Review), status reporting to management, or re-estimating the entire Product Backlog.
Quiz 2: Artifacts, Commitments, and Transparency
Test how well you connect artifacts and their commitments to transparency and lean thinking.
Which statement best explains how the Definition of Done supports empiricism?
- It fixes the Sprint scope so the Product Owner cannot change requirements.
- It allows the Scrum Team to hide unfinished work until they are ready to show it.
- It ensures that each Increment is in a known, usable state, making inspection and comparison across Sprints reliable.
- It defines the exact technical design the Developers must follow for every Product Backlog item.
Show Answer
Answer: C) It ensures that each Increment is in a known, usable state, making inspection and comparison across Sprints reliable.
The Definition of Done makes the state of the Increment transparent and consistent. This allows stakeholders to reliably inspect Increments and compare progress across Sprints. It does not freeze scope, hide work, or prescribe a fixed design.
Flashcards: Empiricism Across Scrum
Flip through these cards to reinforce key concepts and definitions.
- Empiricism in Scrum
- Scrum is founded on empiricism and lean thinking. Empiricism means decisions are based on observation, experience, and evidence, supported by transparency, inspection, and adaptation.
- Three Pillars of Empirical Process Control
- Transparency (true state is visible), Inspection (frequent checks of artifacts and progress), Adaptation (changes made when inspection shows deviation from goals or expectations).
- Sprint (definition)
- Sprints are the heartbeat of Scrum, where ideas are turned into value.
- Product Backlog (definition)
- The Product Backlog is an emergent, ordered list of what is needed to improve the product.
- Sprint Backlog (definition)
- The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
- Increment (definition)
- An Increment is a concrete stepping stone toward the Product Goal.
- Product Goal (definition)
- The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
- Sprint Goal (definition)
- The Sprint Goal is the single objective for the Sprint.
- Definition of Done (definition)
- The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
- Daily Scrum: Empirical Focus
- Inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours, based on the current state of the Sprint Backlog.
- Sprint Review vs Retrospective
- Sprint Review: inspect the Increment and adapt the Product Backlog (product focus). Sprint Retrospective: inspect and adapt how the team works (process and people focus).
Key Terms
- Scrum
- Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
- Sprint
- Sprints are the heartbeat of Scrum, where ideas are turned into value.
- Increment
- An Increment is a concrete stepping stone toward the Product Goal.
- Developers
- Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
- Empiricism
- Scrum is founded on empiricism and lean thinking.
- Scrum Team
- The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
- Sprint Goal
- The Sprint Goal is the single objective for the Sprint.
- Product Goal
- The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
- Scrum Master
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
- Product Owner
- The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
- Sprint Backlog
- The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
- Product Backlog
- The Product Backlog is an emergent, ordered list of what is needed to improve the product.
- Definition of Done
- The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.