Finance wants the city water-quality alerts Product Owner to commit to a fixed date, fixed scope, and fixed budget for the whole Product Goal. What is a valid Product Owner commitment?
Select an answer to reveal the explanation.
Short Explanation
Locking date, scope, and budget on an unsolved water-alert Product Goal is like promising the river height, the rainfall, and the overtime bill on day one. Commitment in Scrum is to the goal and to making ordering decisions, not to a magic triangle. Keep the promises in the world empiricism can actually keep.
Full Explanation
The Scrum Value of Commitment is to the Product Goal and to the Scrum Team’s work, not to a simultaneous lock of date, scope, and budget that empiricism cannot support. The Product Owner should commit to pursuing the Product Goal and to ordering the Product Backlog as evidence arrives. Velocity numbers and transferring promises to the Scrum Master do not make an iron triangle valid. Invalid commitments create pressure to sacrifice Done or transparency when reality diverges.