An enterprise architecture review board must approve every Increment of the 311 request product before release, often adding weeks of wait time. What should the Product Owner seek?
Select an answer to reveal the explanation.
Short Explanation
A bouncer on every Sprint door turns “potentially releasable” into “please take a number.” You still want standards — just not a marble staircase between Done and citizens. Light guardrails beat a standing committee that eats Time-to-Market.
Full Explanation
Centralized gates on every Increment lengthen Time-to-Market and weaken empiricism because stakeholders cannot inspect value in production-like conditions. Architecture constraints can be expressed as lighter guardrails, shared Definition of Done elements, or embedded skills rather than a sequential approval board. The Product Owner should advocate for flow-preserving controls because delayed release is delayed learning. Expanding the gate or substituting slideware does not improve product value.