Developers on the clinic-immunization portal propose a full rewrite for value with no named resident or health-department outcome. What should the Product Owner ask next?
Select an answer to reveal the explanation.
Short Explanation
"Rewrite for value" is a slogan until someone names the scoreboard. If nobody can say whether more parents will finish shot appointments or nurses will spend less time on callbacks, it is a tech wish, not a value bet.
Full Explanation
Technical rewrites on a clinic-immunization portal can be valuable when they improve a stated resident or health-department outcome or a Key Value Area such as Time-to-Market or Ability to Innovate—but that claim needs a hypothesis and a measure. The Product Owner should ask which outcome the rewrite is hypothesized to improve and how change will be measured before ordering it. Asking how many story points the rewrite adds to burn-up measures output, not value. Funding it as a separate project so the Product Backlog stays untouched hides the work from product ordering. Choosing the trendiest vendor framework treats fashion as strategy. Exam caveat: no outcome hypothesis, no rewrite priority. Operational check: require a one-page hypothesis with measures such as appointment completion time or deploy frequency, place the rewrite on the Product Backlog only if that hypothesis beats other value options, and inspect measures after thin slices—not after a big-bang rewrite. Clinic portal rewrites without a named measurable outcome are engineering preference, not Product Backlog value. Require a hypothesis and measures, compare against other value options, and inspect thin slices before any big-bang rewrite.