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.
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.
Inspection
Scrum artifacts and progress toward agreed goals are inspected frequently and diligently, to detect variances or problems early. Inspection is not continuous supervision; it happens at the events, which is why each event has a fixed cadence. 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 more difficult when the people involved are not empowered or self-managing, which is where this domain connects to the next.
How the events enact them
Each of the four events inside the Sprint inspects one thing and adapts another. Reading the pairs together is the quickest way to see 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 |