Sprints

A sprint is a time-boxed run of work with a start, a finish and a commitment. Ithura records what you committed to at the moment you started, what arrived afterwards, and why each unfinished task did not land. That record is the point: a sprint that quietly changes shape teaches you nothing.

Creating a sprint needs the Pro plan. Reading them does not.

Sprints are off by default on a new project. Turn them on in Settings, then Features. See Projects.

The lifecycle

A sprint moves through four states, and dates alone never move it. Nothing starts or finishes on a schedule; you say when.

StateWhat it means
DraftCreated, not started. Tasks can be added freely
CurrentStarted. The commitment is frozen and changes are recorded
CompletedReviewed and closed
ArchivedOut of the way, still readable

Only one sprint in a project can be current at a time. Starting a second one is refused and tells you which sprint is in the way. Dates may overlap, but running two live sprints in one project is not allowed, because then "the commitment" has no meaning.

Planning one

The Sprints tab opens straight onto the running sprint if there is one. To see the list instead, use the Sprints tab and the list view.

  • Plan Sprint N creates a draft named for the next number, using the project's default length. It is the two-click path.
  • New Sprint gives you a name, a description and dates.
  • Default length sets how long a planned sprint runs. It starts at 14 days and accepts 1 to 180.

Starting a sprint

Start Sprint does three things, and the confirmation says so: the commitment is frozen at this moment, and anything added later is tracked as a scope change.

  1. It records the commitment: how many tasks, and how many points. Numeric estimates are counted; a t-shirt scale contributes nothing to the points total, since there is no number to add up.
  2. It moves any task still sitting in a Backlog state into the project's Todo state, so a started sprint does not contain work nobody has picked up.
  3. It marks the sprint current and stamps the start time.

From that moment the sprint has a baseline to compare against.

Scope changes

Once a sprint is current, every task added or removed is recorded as a scope event, including a sub-task created inside the sprint. Adding back a task that was in the original commitment is not recorded, because it never really left.

The sprint keeps the newest 200 scope events, newest first, with the counts alongside. This is what turns "we did not finish" into "we committed to eleven and took on five more on the Wednesday".

Adding a task mid-sprint also lifts it out of Backlog into Todo, the same as starting does. A task can sit in more than one sprint.

Completing a sprint: the review

Complete is a review step, not a button that closes something. For every unfinished task it asks for a reason, with an optional note, plus a retro note for the sprint as a whole.

The reasons are deliberately specific:

  • Under-estimated
  • Blocked (internal)
  • External dependency
  • Urgent interrupt
  • Prod bug ate the time
  • Re-prioritised
  • Rolling over
  • Cancelled
  • Carry-over from last sprint
  • Not really planned

A generic "did not finish" tells you nothing next time. "Urgent interrupt" four sprints in a row tells you something you can act on.

Completing does not move any task. The sprint closes with the record of what happened; the work stays where it is.

A completed sprint stays readable: committed against delivered, in tasks and in points, the retro note, every scope event, the reason on each unfinished task, and its analytics.

Reopen puts a completed sprint back to current, clearing the completion and the retro while keeping the original start. The one-current-sprint rule still applies.

Rolling over what did not land

Roll over is how unfinished work moves on. It runs the review first, if the sprint has not been reviewed, then asks for the next sprint's name and dates.

  • The new sprint is a draft. It does not start itself unless you ask it to.
  • Its start date is the day after the old sprint's end, if that is still in the future, and otherwise now.
  • Every task whose state is not completed or cancelled transfers across.

Tasks that transfer are not recorded as scope changes on the new sprint, so a rollover does not read as scope creep on the sprint receiving it.

Active sprints across the workspace

Active sprints, under Insights, lists every running sprint across your projects on one page, with its date range and progress, instead of making you open each project in turn.

It only covers projects you are an active member of.

One honest caveat. This page lists sprints whose status is current, meaning somebody pressed Start. Home's sprint section works from dates instead, listing sprints whose window covers today. The two can disagree:

  • A sprint started and left running past its end date appears here, but not on Home.
  • A sprint whose dates cover today but which was never started appears on Home, but not here.

If a sprint is missing from one of the two, that is almost always why.

Sprint insights

A running sprint has its own burndown, velocity across the last six sprints, and a cycle-time histogram. Those live with the rest of the reporting, described in Analytics.

Who can do what

ActionNeeds
Read sprints, scope events and outcomesAny project member, guests included
Create, edit, start, reopen, complete, roll over, add or remove tasks, archiveMember or above
Delete a sprintAdmin
Create a sprint at allThe Pro plan

Only creating is gated by the plan. A workspace that drops below Pro keeps its sprints: nothing is deleted, and nothing is purged. The Sprints tab offers an upgrade instead of opening, so plan to finish or roll over a live sprint before you downgrade.

Troubleshooting

What you seeWhat it means
Another sprint is already activeOne current sprint per project. Complete or roll over the running one first. The message names it.
An upgrade screen on the Sprints tabThe workspace is below Pro. Existing sprints are intact and come back on upgrade.
"Member access required"Guests can read a sprint but not change one.
"Admin access required"Deleting a sprint needs admin. Archiving only needs Member.
"Both start_date and end_date are required, or neither"Give a sprint both dates or leave both empty.
"Start date must be before end date"The dates are the wrong way round.
The sprint is completed and refuses a taskReopen it, or put the task in the next sprint.
"No active sprint"Nothing is started in this project. Dates do not start a sprint; Start does.
Points stay at zero with estimates setThe estimate scale is not numeric. T-shirt sizes have no number to total.
A rollover failedNothing is half-moved. The new sprint may exist as a draft; check it before retrying.