An agile team is unable to complete all its planned sprint user stories, which results in a decrease of its planned sprint velocity. What should the team do?

Question

Options

• ARe-estimate the sprint's completed stories to increase and adjust the sprint's velocity.
• BIncrease the duration of the next sprint to accommodate the incomplete user stories and maintain
• CWork with the product owner to create a spike with another agile team.
• DRe-estimate the incomplete stories for the next sprint because its relative size has changed.

• A
  11% (5)
• B
  2% (1)
• C
  4% (2)
• D
  83% (38)

Explanation

In Scrum, sprints are time-boxed and fixed in duration - extending a sprint (B) violates the framework. Re-estimating completed stories (A) to inflate velocity is dishonest and defeats the purpose of velocity tracking. Creating a spike with another team (C) is for research/unknowns, not carrying over incomplete work. The correct action (D) is to move incomplete stories back to the product backlog and re-estimate them for the next sprint, because partial completion may have changed their relative complexity - for example, work already done might make the remainder smaller, or newly discovered complexity may make it larger. Velocity naturally adjusts over time and should reflect actual throughput, not be manipulated.

No community discussion yet for this question.