Lesson 2.1 — Scrum as an empirical, purposefully incomplete framework

Scrum is a lightweight framework — not a methodology, not a recipe, and not a complete manual. A methodology tells you exactly what to do and how to do it at every step. A framework does the opposite: it defines only the minimum structure needed (a few roles, events, and artifacts) and deliberately leaves the choice of tools, techniques, and practices open. The Scrum Guide itself says Scrum is "purposefully incomplete" — that gap is intentional, not an oversight. Scrum is built on empiricism, the idea that knowledge comes from experience and that decisions should be based on what is actually observed — not on assumptions or up-front plans. Alongside empiricism, Scrum also draws on lean thinking: eliminate waste, focus on what delivers value. Empirical process control rests on three pillars: Transparency, Inspection, and Adaptation. Transparency means that the work, the progress, and the definition of 'done' must be visible to everyone who cares about the outcome. Inspection means that the team regularly examines the work and the process to detect undesirable variances. Adaptation means that if something is off, the team adjusts as quickly as possible. The three pillars are interdependent. Inspection without transparency is meaningless — you can't spot a problem in something you can't see. And inspection without the willingness to adapt is simply wasted effort. All three must work together for Scrum to deliver its value.