Empiricism and Scrum values
When a team works on a problem whose outcome cannot be known in advance, it separates what it observed from what it suspects and what it proposes to do. It states an inspectable hypothesis, creates a small usable Increment, compares the result with its expectation and adapts. Transparency is necessary: calling incomplete work Done gives everyone a false object to inspect, and more meetings do not repair the underlying information. Incremental delivery is not splitting a design document into fragments; an Increment is useful, integrated and meets the Definition of Done. The Scrum values guide difficult choices. Commitment serves the goal, focus resists side requests that do not help it, openness welcomes evidence, respect allows a defect to be discussed without blaming its author, and courage prevents an unsupported success claim.
Read the whole first subject without an account: its lessons, summary and review questions.
Subject lessons
- Lesson 1 Complex work and empirical control
- Lesson 2 Transparency, inspection and adaptation
- Lesson 3 Iterative and incremental delivery
- Lesson 4 Five Scrum values in a difficult decision
- Integrated subject summary Review questions
The remaining subjects unlock in sequence once you create a free account.