Scrum Theory and Principles
This domain, Scrum Theory and Principles, tests whether you can explain why Scrum works, not just list its parts. Questions probe complexity, empiricism, the three pillars, the five Scrum values, and how iterative-incremental delivery supports inspection and adaptation.
Core rules and concepts
- Scrum is founded on empiricism and lean thinking. Empiricism means knowledge comes from experience and decisions are based on what is observed; lean thinking reduces waste and keeps only essentials.
- Complex work has emerging requirements and unknown technical outcomes, so defined-process prediction is insufficient. Short cycles generate feedback.
- The three pillars are transparency, inspection, and adaptation. Transparency requires a shared Definition of Done and visible artifact state. Inspection must be frequent enough to detect unacceptable variance. Adaptation follows inspection and should happen as soon as possible.
- The five values are commitment, focus, openness, respect, and courage. They shape behavior; they are not roles or events.
- Scrum uses iterative and incremental delivery: repeated Sprints produce usable Increments and feedback.
Worked example
A team reports an Increment as done, but acceptance tests were never executed. At the Sprint Review, stakeholders find broken workflows. The reasoning: the artifact was not transparent, so inspection gave a false picture and adaptation came too late. The Scrum Master facilitates a shared Definition of Done, makes test evidence visible, and the Developers adapt the Sprint Backlog. A status report alone would not repair transparency; the artifact and its evidence must be visible.
Traps that cost marks
- Treating adaptation as only an end-of-Sprint meeting; it can occur immediately after inspection.
- Confusing the pillars with the values, or listing values as accountabilities.
- Claiming Scrum means no documentation or no planning; it calls for just enough and empirical planning.
- Using “iterative” and “incremental” as synonyms.