Scrum implements empirical process control, which means decisions are made from what has been observed rather than from a plan made in advance. Three pillars support it, and the framework's events exist to enact them.
Empiricism and lean thinking
Empiricism asserts that knowledge comes from experience and that decisions are made from what is observed. Lean thinking reduces waste and focuses on the essentials. The Guide names both because each one alone produces a recognisable failure.
Empiricism alone justifies inspecting everything, endlessly, and an organisation can fill a calendar with defensible review meetings that leave no time to change anything. Lean thinking is the constraint that keeps the loop cheap, which is why the events are timeboxed and why there are five of them rather than fifteen. Lean thinking alone strips waste from a process nobody has checked against reality, producing an efficient machine for building the wrong product.
Transparency
The process and the work must be visible to the people doing the work and to the people receiving it. Visibility alone is not enough. The parties need a shared standard for what they are seeing, which is why the Definition of Done matters here rather than only in delivery. Low transparency leads to decisions that lower value and increase risk.
What transparency requires is that an artifact be what it claims to be. A Product Backlog leaving out work everyone knows is coming is not transparent however neatly it is published, and neither is an Increment called Done that nobody could release. This is why each artifact carries a commitment, since the Product Goal, the Sprint Goal and the Definition of Done each give their artifact a standard it can be measured against.
Inspection
Scrum artifacts and progress toward agreed goals are inspected frequently and diligently, to detect variances or problems early. Inspection is not continuous supervision, and it happens at the events, which is why each event has a fixed cadence. That cadence gives one inspection point per artifact per Sprint, plus a daily one for the Developers, so a wrong turn costs at most one cycle. Inspection without transparency is misleading, because the thing being inspected does not reflect reality.
Adaptation
When inspection shows that something has deviated outside acceptable limits, the process or the material being worked on is adjusted, and the adjustment is made as soon as possible to minimise further deviation. Adaptation becomes harder when the people involved are not empowered or self-managing, which is why this pillar depends on how the organisation is arranged as much as on the team.
Inspection without adaptation is waste in the exact lean sense, because the cost of the meeting was paid, the problem was seen, and nothing downstream is any different. A Retrospective producing a list nobody acts on has bought none of the learning it paid for.
How the events enact them
Each of the four events inside the Sprint inspects one thing and adapts another, and reading the pairs together shows that the framework has no inspection without a corresponding adaptation.
| Event | Inspects | Adapts |
|---|---|---|
| Sprint Planning | The Product Backlog | Produces the Sprint Goal and Sprint Backlog |
| Daily Scrum | Progress toward the Sprint Goal | The Sprint Backlog |
| Sprint Review | The Increment | The Product Backlog |
| Sprint Retrospective | The last Sprint | How the team works |
The Sprint is absent from the table because it adapts nothing. It is the container the other four run inside.
When the organisation hides bad news
Where bad news is punished, what gets inspected stops being the work and becomes a version of the work that is safe to show. Progress is reported as on track, an Increment is called Done because saying otherwise is expensive, and impediments are described as under control. Transparency has gone at that point, so inspection is inspecting a fiction and every adaptation made from it rests on false information.
Nothing inside the framework detects this, because the artifacts still look right and the events still happen on time. It is why openness and courage are among the Scrum Values, and why the Scrum Master's work with the wider organisation is part of the accountability rather than an optional extra.