Sprints

Sprints

A sprint is a short, fixed period — usually one to four weeks — in which your team commits to a set of tickets. The Sprint Manager is where sprints are created and moved through their lifecycle.

Creating a sprint

Pick the project, then give the sprint its start and end dates, a sprint goal — one sentence on what this sprint is for — and any notes. Sprints are numbered automatically within their project, so they come out as KDV-5, KDV-6, and so on.

💡 Write the goal. A sprint with a goal can be judged ("did we ship the invoicing revamp?"); a sprint without one is just a fortnight with a board.

The lifecycle

A sprint is always in one of three states, and you move it forward by hand:

Upcoming → Active → Closed

  • Upcoming — being planned. Fill it with tickets from the backlog.
  • Active — the sprint being worked now. This is the one My Work and the board treat as "the current sprint".
  • Closed — finished, and feeding Insights history.

The calendar does not move sprints for you. If nobody activates the sprint, My Work says "no active sprint" all fortnight — starting and completing a sprint is a deliberate act, usually the first and last item of your sprint ritual.

Completing a sprint

When you complete a sprint, there are almost always open tickets left. The completion flow asks where they should go: choose a destination sprint and the open tickets transfer across, with completed ones staying put. It tells you how many tickets were affected.

That transfer step is the honest moment of sprint-running: what rolls over is your real velocity talking. If half the sprint transfers every time, the sprints are overpacked — Insights will show the same story as scope added after start and completion rates.

Deleting a sprint works the same way — its tickets are moved, not lost.

Rules and things to watch

  • One goal, dated, activated. The three habits that make sprints work: a written goal, real dates, and someone actually flipping Upcoming → Active on day one.
  • Adding tickets mid-sprint is visible. Insights counts tickets created this sprint and scope added after start — mid-sprint additions aren't forbidden, but they are on the record.

Related articles