Handling incomplete items from Sprint to Sprint

A low-touch way to carry unfinished work into the next sprint without losing the record of what each sprint actually delivered: split the story, close part 1, estimate part 2.

An item that is not finished when a sprint ends is the most common reporting problem in sprint-based teams. If you simply drag it into the next sprint, the first sprint loses the effort it absorbed and velocity for both sprints is wrong. If you leave it where it is, the board is cluttered with work nobody is doing.

The DevStride approach is to split the item so each sprint keeps an honest record. It takes under a minute.

Steps

  1. On the unfinished item (call it Story 1), make sure the time spent and any completed subtasks reflect what was actually done this sprint.
  2. Duplicate it from the item's menu to create Story 2. The copy keeps the parent, type, team, and description.
  3. Rename them so they are easy to spot in lists: append (Part 1) and (Part 2) to the titles.
  4. Optionally tag Story 1 Incomplete, and in Relationships make Story 1 a dependency of Story 2 (or mark them Related) so the link survives in reports.
  5. Mark Story 1 Done. It now closes in the sprint that did the work, and reports show Done plus the Incomplete tag, which is a pattern worth watching.
  6. On Story 2, enter the remaining estimate (points or time), move it to the next sprint's board, and carry on working there.