Scrum Theory and Empiricism
Knowledge comes from experience
Scrum rests on empiricism: knowledge comes from experience and decisions are made on what is observed. Lean thinking supports it by stripping out waste and keeping only what is essential. Three pillars carry the framework.
Transparency means the emergent process and the work are visible to the people doing the work and to the people receiving it. It is a precondition, not a nice-to-have. Inspection means artifacts and progress toward agreed goals are checked frequently and diligently to detect undesirable variance. Adaptation means adjusting the process or the materials as soon as a deviation, or an unacceptable product, is found.
Traps
- Treating empiricism as "we'll figure it out later". It still requires a clear goal, a Definition of Done and honest visibility.
- Believing inspection only happens in events. Every event is an opportunity, but inspection without adaptation is pointless, and adaptation without transparency is guesswork.
- Assuming the Sprint Goal is untouchable. Its scope may be clarified and renegotiated with the Product Owner as more is learned; the goal itself is abandoned only when it becomes obsolete.
- Ignoring the five values (commitment, focus, openness, respect, courage), which questions sometimes treat as separate from empiricism rather than as the behaviours that make it possible.
Worked example
A board still shows three tasks "in progress" that were finished yesterday. The Daily Scrum inspects a false picture, so any plan built on it is wrong. Restore transparency first, then change the process.
Rule of thumb: before asking "how do we improve?", ask "can everyone see reality accurately?" If not, that is the first impediment.