Question 150
In a discussion with the delivery team on an adaptive/agile initiative, a customer accepted an iteration plan but is surprised when a low-priority feature misses the public preview. Which assignment establishes appropriate accountability for the affected decision?
Explanation
Correct Answer
Make the product owner accountable for approved preview scope and customer communication. The selected owner has authority over the specific business decision instead of transferring responsibility to an unrelated function. In this case, expectations must be managed continuously as value priorities change. The stated constraint is: A customer accepted an iteration plan but is surprised when a low-priority feature misses the public preview. The chosen accountability is the most direct response under these conditions.
Incorrect Answers
Ask the customer sponsor to approve priority decisions and document rejected tradeoffs. This response addresses another situation in the same task area: A consulting project team reports every stakeholder request as urgent, leaving promised high-value outputs unfinished. There, satisfaction improves through reliable commitments rather than treating all requests as equal. For the current situation—A customer accepted an iteration plan but is surprised when a low-priority feature misses the public preview—this option would leave the specific need unresolved: expectations must be managed continuously as value priorities change.
Have the citizen-service owner approve device coverage and inclusion tradeoffs. This response addresses another situation in the same task area: A municipal app's help desk receives complaints that citizens cannot complete identity verification on older phones. There, expectation management requires measuring who receives the promised service. For the current situation—A customer accepted an iteration plan but is surprised when a low-priority feature misses the public preview—this option would leave the specific need unresolved: expectations must be managed continuously as value priorities change.
Have the customer sponsor approve the proposed scope and price adjustment. This response addresses another situation in the same task area: A mobile wallet client asks for a customization after its contract-defined acceptance window has closed. There, maintaining trust does not mean accepting unapproved scope without evaluating cost and value. For the current situation—A customer accepted an iteration plan but is surprised when a low-priority feature misses the public preview—this option would leave the specific need unresolved: expectations must be managed continuously as value priorities change.