Acceptance criteria on a permit-status Product Backlog item specify exact pixel positions, hex colors, and a 12-pixel font. Developers say they cannot inspect value—only compliance with a mockup. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Telling the crew which brick sits on which millimeter is not the same as saying the resident can see permit status without calling. Capture the outcome and the test; let Developers use craft—and the Definition of Done—for the pixels. Specs that only describe mockups hide whether the work helped anyone.
Full Explanation
Product Backlog items should express user and value intent, not only pixel mandates. Outcome-oriented, testable acceptance criteria enable inspection of whether the Increment helped residents or clerks. Visual detail may inform implementation, but locking pixels up front substitutes output compliance for value. The Product Goal is not a brand guide, and deleting criteria altogether removes the test of done-enough for the item.