At the end of a Sprint, a 311 resident-request product still has an undone routing rule. A deputy wants it labeled Done so the board report looks complete. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Calling leftover work Done is putting a closed sign on a counter that is still messy. The board is better off knowing the 311 routing rule is unfinished than getting a surprise in production. Transparency now is cheaper than a fake green report.
Full Explanation
Undone work must remain visible so the Scrum Team and stakeholders can adapt the Product Backlog honestly. At the end of a Sprint, when a 311 resident-request product still has an undone routing rule and a deputy wants it labeled Done so the board report looks complete, the Product Owner should make the undone work transparent and keep it off the Increment rather than labeling it Done. Transparency now is cheaper than a fake green civic report.
Marking it Done and opening a warranty ticket so the report stays green conceals unfinished work as a future repair. Hiding the gap until the next Sprint Review so stakeholders are not alarmed delays inspection. Counting it as Done if the code compiled, then refining the rule later, invents a Done based on compile success alone.
Board reports that paint 311 green while routing rules remain unfinished trade political comfort for operational surprise. Civic transparency demands the incomplete rule stay visible until it truly meets Done.
Exam caveat: PSPO II Definition of Done forbids labeling undone work Done to protect board optics.
Operational check: leave the routing rule off the Increment, show it as incomplete on the Product Backlog, and report the honest 311 state to the board with the adaptation plan.