Empiricism: Transparency, Inspection, Adaptation

Overview

• What you’ll learn: What empiricism means, why Scrum is built on it, and how the three pillars — Transparency, Inspection, and Adaptation — work in practice.
• Prerequisites: Lesson 3 — Overview of Agile Frameworks
• Estimated reading time: 13 minutes

Introduction

Empiricism means making decisions based on what is observed and experienced, not on what is predicted or assumed. Scrum is founded on empiricism because software development is complex — the outcome is unpredictable, and the only reliable way to make progress is to try something, observe the result, and adjust.

The alternative — the “predictive” approach — assumes you can plan everything upfront and execute the plan perfectly. This works for baking a cake (follow the recipe). It fails spectacularly for building software (the recipe keeps changing while you bake).

The Three Pillars

Transparency

The process and the work must be visible to those performing and receiving the work. Without transparency, inspection is meaningless — you cannot evaluate what you cannot see.

• The Product Backlog is visible to everyone.
• The Sprint Backlog shows what the team is working on right now.
• The Definition of Done is explicitly shared so everyone agrees on what “done” means.
• Problems, impediments, and risks are raised openly — not hidden.

Anti-pattern: A team reports “everything is on track” for three weeks, then reveals the project is six months behind. Transparency means making the uncomfortable truth visible early.

Inspection

Scrum artifacts and progress must be inspected frequently to detect problems early. But inspection without adaptation is waste — the point of looking is to decide whether to change course.

• Daily Scrum: Inspect progress toward the Sprint Goal every day.
• Sprint Review: Inspect the Increment with stakeholders.
• Sprint Retrospective: Inspect the team’s process and practices.

Anti-pattern: A team holds a Sprint Review where everyone claps and nobody gives feedback. That’s a demo, not an inspection.

Adaptation

When inspection reveals that the product or process is deviating from acceptable, adjustments must be made as soon as possible. Waiting makes things worse.

• Sprint Planning adapts the plan based on what was learned in the previous Sprint.
• The Sprint Backlog adapts daily based on the Daily Scrum.
• The product adapts based on stakeholder feedback in the Sprint Review.
• The process adapts based on improvements identified in the Sprint Retrospective.

The Pillars Work Together

Remove any one pillar and the system collapses:

• Without transparency: Inspection is based on false information. You “inspect” lies and adapt to fiction.
• Without inspection: Transparency is useless — the data is visible but nobody looks at it.
• Without adaptation: Inspection is theater — you see problems but do nothing about them.

Key Takeaways

• Empiricism makes decisions based on observation, not prediction.
• Transparency makes the work and process visible. Inspection detects deviations. Adaptation corrects course.
• All three pillars must be present — removing any one renders the others ineffective.
• Every Scrum event is designed to enable one or more of these pillars.

What’s Next

In Lesson 5, you will learn about the five Scrum values — Commitment, Focus, Openness, Respect, and Courage — that enable the three pillars to function.