A portfolio committee demands a detailed annual feature plan for the transit app, complete with month-by-month commitments. What should the Product Owner push instead?
Select an answer to reveal the explanation.
Short Explanation
A month-by-month transit feature contract is a weather forecast tattooed on the wall. The city can fund outcomes and keep an adaptive roadmap without pretending next November’s screen is already known. Push outcome funding, not a fake annual certainty show.
Full Explanation
Agile portfolios fund outcomes and capacity so Product Owners can order empirically as evidence arrives. Detailed annual feature commitments create false precision and turn the Product Backlog into a change-control archive. The Product Owner should push outcome funding and adaptive roadmaps that keep near-term order honest. Replacing the backlog with a predictive breakdown or pausing Reviews until the plan is complete abandons Scrum’s inspect-and-adapt loop.