Scrum Theory and Principles
Core idea
Scrum is a lightweight framework for complex products; it relies on empiricism rather than predictive planning. The three pillars are transparency, inspection, and adaptation. Transparency means the work and its state are visible and understood in the same way by those accountable for it. Inspection means artifacts and progress are examined frequently enough to detect problems. Adaptation means adjusting promptly when inspection reveals deviation. Inspection without transparency is unreliable; adaptation without inspection is guesswork. The Sprint provides the container that makes all three practical.
Principles and values
Candidates must distinguish Scrum values - commitment, focus, openness, respect, and courage - from mechanics. Values shape behavior: openness enables transparency, and courage enables adaptation. Also understand iterative and incremental delivery, self-management, and the idea that Scrum provides boundaries and accountabilities rather than a prescriptive lifecycle.
Traps
Common exam traps include treating Scrum as a fixed process, equating transparency with status reporting, assuming adaptation means changing scope constantly, treating values as optional, and confusing empirical control with no planning. Another trap is fixing a symptom, such as adding reports, when the real issue is a weak Definition of Done or an unclear artifact.
Worked example
Stakeholders say they cannot tell whether the Increment is complete. Do not start with a new dashboard. First inspect transparency: is the Definition of Done explicit and applied? If not, make the artifact state visible. Then inspect and adapt. Rule of thumb: when something goes wrong, ask which pillar failed first - transparency, inspection, or adaptation.