Scrum Empiricism, Lean Thinking, and the Five Scrum Values
Introduction
Scrum empiricism means using what the team observes to decide what to do next. If customers abandon a new payment flow, a working Increment and reliable usage data give the Scrum Team something concrete to inspect. The team can adjust its plan and see whether the change helps.
This PSM I lesson covers Empiricism and Scrum Values in Scrum.org’s Understanding and Applying the Scrum Framework focus area. Scrum.org lists the focus areas without publishing their weights. The November 2020 Scrum Guide by Ken Schwaber and Jeff Sutherland is the reference for the framework. You will apply its three empirical pillars and five values to decisions about quality, scope, and stakeholder feedback.
Learning objectives
- Explain the purpose of Scrum and the elements the framework defines.
- Explain how empirical process control lets teams plan and adjust when they face uncertainty.
- Describe transparency, inspection and adaptation and give a concrete example of each.
- Describe the five Scrum Values and how they show up in daily behaviour.
- Explain what lean thinking contributes to Scrum (reducing waste, focusing on the essentials).
- Recognise "Scrum-but" and other situations that break the framework's feedback loops.
1. Scrum as a framework for complex work
Scrum gives a team a small set of rules for delivering value and adjusting its work as it learns. Its three accountabilities, five events, three artifacts, and artifact commitments define the framework. Teams choose practices such as estimation, testing, and how to visualize their work based on their context.
Complex work involves uncertainty about the problem, the solution, or both. Scrum uses repeated cycles of planning, delivery, and inspection so teams can test assumptions in manageable steps. Empiricism guides those decisions through observation and experience. Lean thinking helps the team focus its effort on what contributes to value.
Use the framework as a whole. Skipping a Retrospective, for example, removes the event dedicated to improving quality and effectiveness. A team may change how it runs the event while preserving its purpose.
Example: a complex problem
A regional bank wants a mobile application that lets customers dispute card transactions. Nobody knows precisely which dispute categories customers will actually use, how the fraud-detection back end will respond under load, or how customers will react to a photo-upload step. A fixed 12-month plan would lock in guesses. Scrum lets the bank release a first Increment after four weeks that supports a single dispute category, observe real usage, and adapt the next four weeks accordingly. The complexity is the reason Scrum is appropriate.
2. The three pillars of Scrum empiricism
Empirical process control is a process control approach in which decisions are based on observation, experience and experimentation. The guide names three pillars. All three are needed; each depends on the others.
| Pillar | Meaning | Typical Scrum mechanism |
|---|---|---|
| Transparency | The significant aspects of the process and the work must be visible to those responsible for the outcome. Readers need a common understanding of what the visible information means. | Product Backlog, Sprint Backlog, Increment, Definition of Done, a shared board |
| Inspection | Review the artifacts and progress toward goals often enough to identify problems early. | Daily Scrum (progress toward the Sprint Goal), Sprint Review (outcome and changes in the environment), Retrospective (quality and effectiveness) |
| Adaptation | Change the plan, product, or way of working promptly when inspection reveals a material gap. | Updating the Sprint Backlog, reordering the Product Backlog, or acting on a Retrospective improvement |
Two details are frequently tested.
- Transparency is about shared understanding, not just visibility. A burndown chart that nobody reads the same way, or a Definition of Done that Developers interpret differently, is not transparent. When the board and the quality checks tell different stories, people can make costly decisions on incomplete information. Inspection and adaptation built on opaque or misleading information lead to poor decisions.
- Use the evidence to decide what to change. The formal Scrum events for inspection and adaptation provide a regular cadence. If a defect threatens the Sprint Goal today, the team can act today.
Example: the three pillars on one team
A team building a ticketing platform notices in the Sprint Backlog that three items are tagged "almost done". The Definition of Done requires automated tests and a security scan, but two of the three have only manual tests.
- Transparency: the team makes the gap visible by showing the Definition of Done next to the board and by counting an item as done only if it fully meets it.
- Inspection: at the Daily Scrum, the Developers inspect progress toward the Sprint Goal and see that the real remaining work is larger than the board suggested.
- Adaptation: they swarm on the security scans, re-plan the rest of the Sprint Backlog and tell the Product Owner that one lower-priority item will not fit.
The Developers can change their plan as soon as they understand the impact. They collaborate with the Product Owner if the selected scope needs to change.
3. Why Scrum uses timeboxed iterations
Because inspection and adaptation need fresh information, Scrum organises work into Sprints of one month or less. The guide explains that a Sprint is the heartbeat of Scrum where ideas are turned into value, and that shorter Sprints can generate more learning cycles and limit risk of cost and effort to a smaller time frame. A shorter cycle can give the team evidence sooner. Its length stays fixed so people can inspect results at a predictable cadence.
Scrum also uses an incremental approach: the Scrum Team is accountable for creating a valuable, usable Increment each Sprint. Several Increments may be created during a Sprint and delivered before the Sprint Review. Work that misses the Definition of Done returns to the Product Backlog and cannot be released or presented at the Sprint Review. See Scrum artifacts and their commitments for how the Definition of Done makes quality visible.
4. Lean thinking
Lean thinking, which originates from lean manufacturing, focuses on delivering value and eliminating waste. In Scrum it appears in several places, even though the Scrum Guide does not use lean jargon heavily.
- Select work based on capacity. Developers select Product Backlog items through discussion with the Product Owner. They can renegotiate the selected scope as they learn, while protecting the Sprint Goal.
- Limit work in progress where useful. A team can choose a work-in-progress limit to finish and validate work sooner. Scrum supplies the Sprint Goal and leaves the choice of a numerical limit to the team.
- Eliminating waste. Features that nobody uses, handoffs between specialist groups, long waiting times for approvals and unfinished work are all forms of waste. The Product Owner orders the Product Backlog to maximize value and can weigh dependencies, uncertainty, and risk alongside expected benefits. Completing the quality checks as part of each Increment makes unfinished work visible.
- Continuous improvement. The Sprint Retrospective exists so the Scrum Team plans ways to increase quality and effectiveness each Sprint.
- Respect for people. Self-managing, cross-functional teams, rather than command and control, reflect the lean idea that the people doing the work know best how to improve it.
Comparison: predictive vs. empirical approaches
| Aspect | Predictive (plan-driven) | Empirical (Scrum) |
|---|---|---|
| Starting assumption | Requirements can be known up front | Requirements emerge as people learn |
| Planning | Detailed plan for the whole project | Plan the next Sprint in detail; keep the Product Backlog adaptable |
| Feedback | May be organized around milestones | At least every Sprint, with inspection of the outcome and what changed |
| Change | Handled through formal change control | Welcomed through Product Backlog ordering |
| Risk | Concentrated at the end | Spread across Sprints and reduced early |
| Progress measure | Often milestones or delivery against a baseline | Inspect progress toward the Product and Sprint Goals using the usable Increment and other evidence |
5. The five Scrum Values in practice
Commitment, Focus, Openness, Respect, and Courage guide the way a Scrum Team works. When the team shares a missed quality check openly, stakeholders can inspect the same evidence and help decide what needs to change. The values reinforce the empirical pillars by making honest discussion and timely action possible.
| Value | What it looks like in practice | What undermines it |
|---|---|---|
| Commitment | The Scrum Team commits to the Sprint Goal, the Definition of Done and the Product Goal (the commitments attached to the artifacts) | Treating the Sprint Backlog as a list a manager can change; quietly lowering quality to hit a date |
| Focus | Developers concentrate on the Sprint Goal and discuss changes with the Product Owner | Multitasking across several projects; adding new work to the Sprint without negotiation |
| Openness | Developers show real progress and impediments at the Daily Scrum; the Product Owner shares uncertainty about the market | Hiding delays; reporting "green" status while the Increment is unusable |
| Respect | Team members assume competence and good intent; stakeholders respect the Developers' choice of how to do the work | Assigning tasks to individuals from outside; blaming a person for a failed Sprint |
| Courage | Saying that the Sprint Goal is at risk; challenging an unrealistic deadline; refusing to release work that is not Done | Staying silent in the Sprint Review about known quality problems |
An exam tip: when a question asks which Scrum Value is demonstrated, look at the action described, not at the vocabulary. A Developer who announces at the Daily Scrum that an integration is much harder than expected is showing openness and courage; a team that says "we will not take on that extra story, so we can finish the Sprint Goal" is showing focus.
6. Worked example: choosing the empirical response
Scenario. A Scrum Team is in the third week of a four-week Sprint. The Sprint Goal is "Customers can pay with a saved card". At the Daily Scrum the Developers realise that the payment provider's sandbox is returning errors, so the forecast Sprint Backlog items cannot all be finished. The department head, who is not part of the Scrum Team, says that the team must commit to the original scope and work extra hours to show everything in the Sprint Review. What should the Scrum Team do?
Step 1: Identify what is at stake. The Sprint Goal is the single objective for the Sprint, and the Developers are accountable for creating and adapting the Sprint Backlog. The scope may be clarified and renegotiated with the Product Owner as more is learned, as long as the Sprint Goal is not endangered.
Step 2: Apply the pillars. Transparency: tell the Product Owner and the department head openly about the sandbox issue and its impact. Inspection: examine which Sprint Backlog items still serve the Sprint Goal. Adaptation: the Developers, with the Product Owner, renegotiate the scope. For example, they could drop the "remove a saved card" item while keeping the key payment path.
Step 3: Apply the values. Openness (say it now, not at the Sprint Review), courage (decline the unsustainable extra-hours demand), and focus (protect the Sprint Goal).
Step 4: Decide. The Developers adjust the Sprint Backlog. The Product Owner can update the Product Backlog as soon as the evidence warrants it. The Scrum Master can help address the provider issue and coach the organization on protecting the team’s ability to adapt.
Why the other options are weaker. Silently working overtime hides the delivery constraint and makes future forecasts less reliable. Cancelling the Sprint is overkill because the Sprint Goal is still achievable; only the Product Owner has the authority to cancel a Sprint, and only when the Sprint Goal becomes obsolete. Letting the department head re-plan the work violates the self-management of the Developers.
7. Common pitfalls and exam tips
- "Scrum is a process with steps." The guide calls it a framework. If an option says "Scrum prescribes how Developers must implement features", it is wrong.
- "Empiricism means no planning." Scrum has Sprint Planning, a Product Backlog and a Product Goal. Empiricism means plans are adapted with evidence.
- Confusing the pillars. The Daily Scrum is mainly inspection of progress toward the Sprint Goal with adaptation of the Sprint Backlog; a status report to management is not its purpose.
- Treating the Scrum Values as posters. Exam questions describe behaviours; choose the answer that reinforces the values.
- Partial Scrum. If you read "the team drops the Retrospective because it is time-consuming", the right answer addresses the lost opportunity to adapt, not an alternative meeting.
- Wording traps. Words such as "must", "only" and "always" in options deserve careful reading. The Scrum Guide is explicit about what is required (for example, the Sprint length of one month or less) and silent about many things (for example, estimation technique).
- The Scrum Master is not a project manager. Empiricism requires the people who do the work to decide; this is developed in the lessons on accountabilities and self-management.
Exam tip. First check that the action respects the Scrum Guide’s accountabilities and commitments. Then ask which action helps the team inspect reliable evidence and adapt in time.
8. Mini case study
Context. Northwind Logistics has a Scrum Team of seven Developers, a Product Owner and a Scrum Master building a fleet-tracking dashboard. Over three Sprints the Sprint Review has been attended only by the Product Owner. Stakeholders say they are "too busy" and prefer a monthly email. The Developers have started marking items as done when the code is merged, although the Definition of Done also includes performance tests that rarely run. Last week a customer reported that the dashboard freezes for fleets above 500 vehicles. The Retrospective was skipped twice because "the release was urgent". The Product Owner reports to management that velocity is stable.
Question. Identify which parts of empiricism and which Scrum Values are being weakened, and propose actions.
Commented solution.
- Transparency is weakened. "Done" means different things for different people: the board says Done, the Definition of Done says otherwise. A velocity figure built on items that are not really Done is misleading. Action: only count an item as Done when it meets the whole Definition of Done; make undone work visible, and return incomplete items to the Product Backlog for consideration.
- Inspection is weakened. Stakeholders no longer inspect the Sprint outcome with the team, so market feedback is missing; the team lost a chance to discuss the observed performance problem and its impact with stakeholders. Action: the Product Owner and Scrum Master invite stakeholders to a hands-on Sprint Review and show the working Increment, not slides.
- Adaptation is weakened. Skipping the Retrospective removes the formal opportunity to change the way of working. Action: reinstate the Retrospective and use it first to address the Definition of Done and the late performance testing, for example by automating performance tests in the pipeline.
- Values. Openness calls for making the failed checks visible. Courage supports raising the release risk. Commitment means maintaining the quality checks. Respect means listening to stakeholders’ time constraints while agreeing on a way to inspect the outcome together.
The Scrum Master helps the team and stakeholders agree on a workable Sprint Review and addresses barriers to attendance. The Developers adhere to the Definition of Done, including the performance checks.
Key terms
- Scrum: a framework for teams to deliver value and adapt as they learn about complex problems.
- Empiricism: knowledge comes from experience; decisions are based on what is observed.
- Transparency: significant aspects of the process and work are visible and commonly understood.
- Inspection: frequent, diligent checking of artifacts and progress toward goals.
- Adaptation: adjusting the process or the product as soon as possible when deviations appear.
- Lean thinking: reducing waste and focusing on the essentials.
- Sprint: a fixed-length event of one month or less; the container of all other events.
- Increment: a concrete stepping stone toward the Product Goal.
- Scrum Values: Commitment, Focus, Openness, Respect and Courage.
- Scrum-but: using only part of Scrum while still calling it Scrum.
Summary checklist
- I can explain how a lightweight framework helps a team deliver value in complex work.
- I can explain that Scrum is founded on empiricism and lean thinking.
- I can define transparency, inspection and adaptation and match each to Scrum events and artifacts.
- I know that the Sprint is one month or less to keep feedback loops short.
- I can describe the five Scrum Values and recognise them (or their absence) in a scenario.
- I understand that Scrum is only Scrum when implemented in its entirety.
- I can resolve a scenario by choosing the answer that increases transparency and enables earlier adaptation.
Sources
- The Scrum Guide (November 2020), Ken Schwaber and Jeff Sutherland, CC BY-SA 4.0: https://scrumguides.org/scrum-guide.html (opens in a new tab)
- Scrum.org, Professional Scrum Master I assessment: https://www.scrum.org/assessments/professional-scrum-master-i-certification (opens in a new tab)
- Scrum.org, suggested reading for the Professional Scrum Master: https://www.scrum.org/resources/suggested-reading-professional-scrum-master (opens in a new tab)
