Review questions
Summary: 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. In the booking case, fewer support calls alone do not prove that self-service rescheduling worked if appointment volume and audience changed between periods. Check denominators and reasons for failure before choosing an interface or policy change. A common mistake is treating a senior person's interpretation as fact or allowing an initial plan to hide learning.
Review questions
Test your understanding with these questions. Marking and saved results are available with a free account.
Create a free account to mark your answers and save your progress.