The team is in the middle of an iteration and there is an urgent request for a small change to be introduced to the committed scope. Unless this change is accepted, there is no value to the…

Question

Options

• AAdd the new change request as a new user story in the product backlog for the upcoming
• BEvaluate the impact of the change request and let the team and product owner decide and re-
• CRecommend cancelling the current iteration and plan the change request into the next iteration
• DRecommend that the product owner add this change request as a user story to the backlog for

• A
  9% (2)
• B
  82% (18)
• C
  5% (1)
• D
  5% (1)

Explanation

When a change request is urgent and value-critical, the agile approach is to evaluate its impact transparently and then empower the right people - the team (capacity/feasibility) and the product owner (value/priority) - to decide together whether to accept, defer, or re-plan. This preserves both agility and discipline. Options A and D (add to backlog for a future iteration) ignore the stated urgency and the consequence that the current iteration would deliver zero value - an unacceptable outcome. Option C (cancel the iteration) is drastic and wasteful when a re-planning adjustment may be all that's needed. The key is collaborative decision-making, not unilateral action.

No community discussion yet for this question.