Scrum Framework and Theory
The empirical core
Scrum is a lightweight framework built on empiricism and lean thinking. Empiricism says knowledge comes from experience and decisions are made on what is observed. Three pillars support it: transparency (the work and process are visible to those accountable for the outcome), inspection (artifacts and progress are checked frequently), and adaptation (adjustment happens quickly when results deviate). Each pillar only works if the one before it does - inspection without transparency is theater, adaptation without inspection is guesswork.
The five values - commitment, focus, openness, respect, courage - are not decoration; questions often test whether a behavior supports or undermines them.
Traps to watch
- Confusing the framework (fixed: accountabilities, events, artifacts and their rules) with practices (tailorable: estimation technique, tooling, definition of ready).
- Treating Scrum as a methodology or a process with prescribed technical practices. Scrum deliberately leaves how to the team.
- Believing transparency means "anyone can see the board." It means a shared, common understanding of what is being done and why.
- Forgetting that the Definition of Done is the primary instrument of transparency about the increment.
Rule of thumb
When a question asks what to do about a problem, prefer the answer that makes information visible to the people who own the decision over the answer that fixes it for them. Empiricism favors exposing the issue to the accountable role, then adapting the plan at the next suitable event.
Worked example
A stakeholder asks the Scrum Master to add a defect-tracking column to the board so they can see quality. Better answer: ensure the Definition of Done makes quality criteria explicit and that the increment meets it - transparency about the increment, not a new artifact outside the framework.