Empiricism and Scrum values

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.

  1. Question 1A Scrum Team develops a booking service. Its usable Increment shows that 18 of 50 users who started changing an appointment did not finish. A manager suspects a long form, while support staff suspect appointment rules. Which next step best supports an empirical decision?
  2. Question 2A Sprint board marks cancellation Done, but testing shows that some accounts receive no cancellation confirmation, and the Definition of Done requires reliable confirmation. What is the most appropriate response?
  3. Question 3A room-booking product's main risk is that two customers reserve the same room at the same time. Which Sprint work gives the team the best opportunity to learn about that risk early?
  4. Question 4One day before a Sprint ends, Developers discover a defect that prevents a notification feature from meeting the Definition of Done. A stakeholder asks them to call it Done to protect an announcement date. Which response aligns with Scrum values and accountabilities?