Empiricism and Scrum foundations

Review questions

Integrated summary: Empiricism and Scrum foundations

Product ownership begins by separating observation, assumption and the decision that evidence must inform. Scrum empiricism uses transparency, inspection and adaptation; the first number does not explain its own cause. If booking completion falls, check metric definitions, customer mix and change timing before attributing the movement to a feature. The Product Owner is accountable for maximizing product value and effective Product Backlog management; Developers choose how to create a Done Increment, and the Scrum Master serves Scrum effectiveness. Deadline pressure does not transfer those accountabilities to a task manager. Distinguish an output such as released feature count from the user outcome it might enable. State a testable value hypothesis, a success signal and a trigger for adaptation instead of treating delivery itself as proof of success.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1Booking completion falls from 62% to 49% after a screen change, while the visitor channel also changes in the same week. What is the first responsible empirical decision?
  2. Question 2A product team observes more trial signups after a pricing change, but paid conversion has not moved. Which conclusion is justified now?
  3. Question 3Two dashboards report different cancellation rates for the same Sprint. What should the Product Owner do before reordering work?
  4. Question 4A team runs a small checkout experiment. The outcome improves for new visitors but worsens for returning customers. Which response best uses the evidence?
  5. Question 5In a second period, 330 of 600 bookings complete: 280 of 400 returning users and 50 of 200 newcomers. The earlier aggregate was 300 of 500 without segment detail. Which conclusion is soundest?
  6. Question 6At Sprint Review, users reveal that a planned integration solves only half their workflow. What should happen to the remaining Product Backlog plan?
  7. Question 7A usage report arrives late and contradicts an assumption used at Sprint Planning. What is the most useful response?
  8. Question 8A team inspected a recurring support complaint but took no action for four Sprints. Which missing element most directly explains the weak learning loop?
  9. Question 9A Product Owner delegates writing Product Backlog items to a business analyst, then says the analyst alone is now accountable for their clarity and ordering. What corrects this?
  10. Question 10A Product Owner orders a security repair first; a manager instructs Developers exactly how to implement it. Which boundary is crossed?
  11. Question 11A stakeholder wants two people to be joint Product Owners so each department can veto ordering. What is the Scrum-compatible response?
  12. Question 12During a Sprint, Developers identify a better technical route to the Sprint Goal. Who decides their revised plan?
  13. Question 13A team releases two features. Task completion without help rises from 150/300 to 198/360, while average task time rises from four to six minutes. Which description fits the evidence?
  14. Question 14The Product Goal is to help first-time applicants submit a request without assistance. The team ships ten features used mainly by expert customers, while first-time completion remains unchanged. Which next product choice fits the goal?
  15. Question 15A release drives page views upward, but fewer people finish the service request. Which measure should govern the next product decision?
  16. Question 16A feature is widely used but increases costly support contacts. What is the sound next value question?