Scrum Theory and Empiricism
Why Scrum works the way it does
Scrum is founded on empiricism - knowledge comes from experience and decisions are made on what is observed - and on lean thinking, which removes what does not add value and keeps focus on the essentials. Work proceeds in iterations and increments so the product is inspected and adapted frequently.
The three pillars
Transparency means the process and the work are visible to those performing and receiving it, using a shared Definition of Done as the standard. Inspection must be frequent enough to detect undesirable variance but not so frequent that it gets in the way of the work. Adaptation follows: if any aspect deviates outside acceptable limits, or the resulting product is unacceptable, adjust as soon as possible - which requires empowered, self-managing people.
The pillars form a chain. Without transparency, inspection is misleading; without inspection, adaptation is guesswork; without adaptation, inspection is theatre. When a question describes something going wrong, trace the failure back to the earliest broken link.
Values
The five Scrum Values - commitment, focus, openness, respect and courage - give direction to behaviour and build the trust empiricism needs. Note that in current Scrum, commitment means dedication to the team's goals (the Sprint Goal, the Product Goal), not a promise to deliver a fixed scope.
Traps
- Treating empiricism as "no planning" - Scrum plans, but plans are revised as evidence arrives.
- Confusing transparency with status reporting to management; more reports do not equal more transparency.
- Assuming inspection must be frequent documentation reviews rather than empirical checkpoints.
- Believing the values are optional sentiment rather than the behavioural basis of trust.
Rule of thumb
When something feels wrong, ask: what is not visible, what inspection is missing, and who can adapt? Fix transparency first.