A customer has requested a new feature be included in the next iterative release. The customer has agreed to move a previously planned feature to a subsequent release and increase the budget. Which…

Question

Options

• AAnalyze the critical path and update the WBS with the new feature
• BAdd the new feature and reprioritize the product backlog
• CAdd the new feature to the next sprint and move the old feature to the following sprint
• DConduct a retrospective with the team to discuss the change and introduce the feature

• A
  5% (2)
• B
  2% (1)
• C
  82% (36)
• D
  11% (5)

Explanation

The key word here is 'iterative release,' which signals an Agile/Scrum context. In Scrum, work is organized into sprints. When a customer requests a feature swap between releases, the correct action is to place the new feature in the next sprint and move the deferred feature to a future sprint. Option A (critical path/WBS) is a predictive/waterfall technique, not iterative. Option B (reprioritizing the product backlog) is partially correct but incomplete - the backlog update follows naturally, and the specific sprint-level action is adding to the next sprint. Option D (retrospective) is the wrong ceremony - retrospectives are for process improvement, not for introducing scope changes.

No community discussion yet for this question.