Fate of a user story when it isn't completed in a sprint due to sudden capacity reduction

 When a user story isn't completed in a sprint due to sudden capacity reduction, here are the typical approaches teams take:

Immediate Sprint Actions:

• The story remains in "In Progress" or gets moved back to the sprint backlog
• During the sprint retrospective, the team discusses what happened and captures lessons learned
• The story's remaining work gets estimated based on what's left to do

Post-Sprint Options:

• Roll over to next sprint - Most common approach if the story is partially complete and still high priority
• Return to product backlog - If priorities have shifted or the story needs re-evaluation
• Split the story - Break it into smaller pieces, potentially accepting the completed portions and creating new stories for remaining work

Capacity Management:

• Update team velocity calculations to reflect the actual capacity reduction
• Reassess upcoming sprint commitments based on the new reality
• Consider whether the capacity reduction is temporary or permanent

Stakeholder Communication:

• Inform stakeholders about the delay and revised timeline
• Discuss priority adjustments if needed
• Be transparent about capacity constraints