Search code examples
scrum

Scrum: obsolete backlog items and external impediments

How can I deal with sprint backlog items that somehow becomes obsolete or unnecessary mid-sprint? Do I mark them as solved?

What about tasks that are dependent on external factors outside the control of the team?

Solution

  • The Scrum Guide covers this eventuality:

    During the Sprint:

    • Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

    So, if you end up removing Sprint Backlog Items, your first action would be to return them to the Product Backlog. You don't mark them as "Done" because they're not, and to do so would reflect incorrectly on the Velocity.

    Having removed Sprint Backlog Items, the Development Team may feel that they have capacity to bring other Product Backlog Items in to the Sprint. That's their call.

    Later, perhaps during Product Backlog Refinement, you may decide that the removed Product Backlog Items are no longer useful. You could then remove them from the Product Backlog, updating any Product Roadmaps or Release Burndowns that had included those items.