The city’s 311 request product funds a separate innovation lab that prototypes citizen-request ideas but has no path to production systems and no Definition of Done. What should the Product Owner challenge?
Select an answer to reveal the explanation.
Short Explanation
A lab that never ships is a dress rehearsal with no opening night. Citizens do not get value from a prototype trapped on a demo laptop. Challenge any “innovation” design that cannot produce a Done 311 Increment in the real service.
Full Explanation
Innovation structures only create product value when they can release a Done Increment into the environment residents actually use. A city 311 innovation lab that prototypes citizen-request ideas with no path to production systems and no Definition of Done produces demos, not empiricism about 311 outcomes. Discovery and prototyping remain useful, but they must connect to the Scrum Team’s ability to inspect real results in the live service. The Product Owner should challenge an innovation structure that cannot deliver Done, releasable Increments of real 311 value.
Challenging the lab’s sketches because Product Owners must forbid discovery fails—discovery is valid; disconnected demos are the problem. Challenging any experiment smaller than a full annual rewrite fails by confusing ambition with learning. Forbidding Developers on the lab so innovation stays in a stage-gate committee fails by restoring predictive theater instead of empirical product work.
Exam caveat: Innovation without a path to Done production value is demo theater, not product progress. Operational check: Require every lab prototype intended to become 311 value to name its production path, Done standard, and owning Scrum Team before it consumes further portfolio capacity.