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.
Question 1 Booking 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? Revert the screen immediately because timing proves causation Inspect measure integrity and completion within each channel before attributing the fall Announce improvement because booking starts increased Wait three Sprints without inspection to preserve the plan Question 2 A product team observes more trial signups after a pricing change, but paid conversion has not moved. Which conclusion is justified now? The price change has already increased product value The pricing change failed and must be reverted immediately Inspect conversion by cohort and allow enough time for paid outcomes Stop measuring conversion because signups are easier to count Question 3 Two dashboards report different cancellation rates for the same Sprint. What should the Product Owner do before reordering work? Use the larger number because it makes risk visible Reconcile event definitions and denominators with the team Average the two percentages without checking their populations Freeze the backlog until the next annual report Question 4 A team runs a small checkout experiment. The outcome improves for new visitors but worsens for returning customers. Which response best uses the evidence? Inspect segment needs and adapt the next experiment before a broad release Release to everyone because the aggregate is positive Discard every result because segments disagree Prioritize the returning-customer result alone because that segment has used the product longer Question 5 In 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? The interface change caused a five-point drop in returning-user completion Returning users complete at 70% and newcomers at 25%, but the change's effect within either segment is unknown without a baseline Newcomers complete at 50% because they are half as numerous as returning users Value certainly rose because completed bookings increased by thirty Question 6 At Sprint Review, users reveal that a planned integration solves only half their workflow. What should happen to the remaining Product Backlog plan? Keep it unchanged because the original plan was approved Ask Developers to implement the missing half without discussion Cancel the current Product Goal automatically Discuss the evidence and adapt upcoming backlog items toward the Product Goal Question 7 A usage report arrives late and contradicts an assumption used at Sprint Planning. What is the most useful response? Make the report and its limitations visible, then inspect whether the plan needs adaptation Hold the report until Sprint Review to avoid discussing a new scope risk mid-Sprint Treat the late report as automatically more accurate Change the Sprint Goal unilaterally to match the report Question 8 A team inspected a recurring support complaint but took no action for four Sprints. Which missing element most directly explains the weak learning loop? More detailed meeting minutes A longer Sprint to avoid interruption Adaptation based on the inspected evidence A larger list of complaints without prioritization Question 9 A 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? Writing may be delegated, while accountability for effective backlog management remains with the Product Owner Backlog ordering transfers to the Scrum Master because they facilitate collaboration Developers become accountable for product value as soon as they write items Scrum forbids any delegation of backlog management work Question 10 A Product Owner orders a security repair first; a manager instructs Developers exactly how to implement it. Which boundary is crossed? The Product Owner may never order technical repairs Developers decide how to turn selected work into a usable Increment The manager owns the Product Backlog once security is involved The Scrum Master alone chooses the implementation Question 11 A stakeholder wants two people to be joint Product Owners so each department can veto ordering. What is the Scrum-compatible response? Split one Product Backlog into departmental queues Give every stakeholder an equal final vote on each item Give each department final ordering authority for its own segment of the shared Product Backlog Keep one Product Owner accountable while making stakeholder input transparent Question 12 During a Sprint, Developers identify a better technical route to the Sprint Goal. Who decides their revised plan? Developers, collaborating with the Product Owner about scope and value as needed The Product Owner must approve every technical step The stakeholder who requested the feature No one may change a plan after Sprint Planning Question 13 A 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? Both features succeeded because output increased User experience certainly worsened because time rose Completion improved from 50% to 55% alongside an adverse time signal; inspect comparable cases before an overall value judgment The new completion rate is 66% because 198 exceeds 150 Question 14 The 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? Count the ten features as proof that the Product Goal advanced Expand the expert feature set because its users are already active Change the Product Goal retroactively to match what was shipped Inspect the first-time submission barrier and order a testable slice for that group Question 15 A release drives page views upward, but fewer people finish the service request. Which measure should govern the next product decision? Page views alone, because they grew Completion and its barriers, alongside page views as context Number of deployed code changes The most favorable metric in the executive slide Question 16 A feature is widely used but increases costly support contacts. What is the sound next value question? How many more features can we ship with the same team? Assume support contacts are a short onboarding cost without checking whether they persist Treat high usage as proof that the continuing support burden is acceptable Which users benefit, what support burden arises, and can the design reduce it? Create a free account to mark your answers and save your progress.