Sprints and planning · Taskending editorial team
What to do when new work arrives mid-sprint
Adding a request does not create more capacity. A scope change should be an explicit decision with visible consequences.
Updated: · 1 min read
How to apply it
Establish why the need cannot wait. Create the Taskending issue and describe impact and urgency. Compare it with the sprint goal, then decide what will be delayed or how the goal changes. Record the decision on affected work.
A concrete example
A broken payment flow may outrank a visual improvement. Move the displaced improvement back to the backlog with a reason when admitting the urgent fix. The explanation will then exist at sprint review.
What to watch for
Treating every idea as urgent creates a constantly moving target. Evaluate impact rather than the requester’s seniority. Invisible unplanned work prevents the team from understanding real capacity.
How to check the outcome
Compare initial scope with additions at closure. Frequent changes may call for a larger support allowance or a different planning interval.
Try it in your own workflow.
Create a company workspace and your first issue. Taskending is currently free.
Start for free