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. When finance wants a city water-quality alerts Product Owner to commit to a fixed iron triangle for the whole Product Goal, a valid commitment is to the Product Goal and to empirical ordering decisions as evidence arrives—not to an impossible locked triangle.
Signing the iron triangle so Commitment means guaranteeing all three constraints invents a promise Scrum cannot keep and pressures later sacrifice of Done or transparency. Committing only to a story-point velocity number substitutes an internal forecast metric for product commitment. Transferring the commitment to the Scrum Master so product promises sit with facilitation misplaces accountability away from the Product Owner.
Exam caveat: PSPO II Commitment is not an iron-triangle guarantee; invalid date/scope/budget locks are a recurring distractor under municipal finance pressure.
Operational check: restate the water-alert Product Goal as the commitment, refuse the locked triangle in writing, and offer inspectable Intermediate Goals and forecast ranges instead of a fake fixed delivery contract.