Sprint workflow
The statuses an item moves through, who is allowed to move it, what the Monday rollover does, and how unattended implementation works.
Last reviewed · maintained by Founder
The statuses
| Status | Where it shows | What it means |
|---|---|---|
| Backlog | Backlog column | Not on this week's sprint. Ordered by hand. |
| Ready | Ready / Active column | On the sprint, available to pull. This is what a connected agent reads. |
| In Review | In Review column | Claimed to be done, waiting for a human verdict. |
| Done | Done column | A person accepted it. |
| Archived | Archive view | Retired, or swept off the board at rollover. Recoverable. |
Who can move what?
| Transition | A person | A connected agent |
|---|---|---|
| Backlog → Ready | Yes | Yes |
| Ready → In Review | Yes | Yes |
| In Review → Done | Yes | No |
| Anything → Backlog | Yes | Yes, off the sprint |
| Done → reopened | Yes | Yes, with a reason |
| Anything → Archived | Yes | Yes, when not Ready or In Review on a sprint |
The one closed door is the one that matters: nothing an agent can call marks an item Done. A commit can carry an item as far as In Review; a person takes it the rest of the way. That is not a permission setting — there is no such tool.
What happens at the end of a week?
On Monday, in your project's timezone, the previous sprint closes:
- Unfinished items carry forward into the new sprint, keeping their column.
- Items in Done are archived, stamped with their completion date.
- The closed sprint keeps its delivered points, which is what velocity is computed from.
Nothing is lost by archiving. An archived item with a completion date still counts towards its epic and its milestone, still appears in the Archive view, and still shows a green tick on the roadmap. Statuses get overwritten by the rollover; completion dates survive it, which is why the product leans on dates rather than on status for anything historical.
Velocity
Velocity is the delivered points of completed sprints, carried in the top bar. Points carried into a sprint from the previous week are subtracted from that week's total, so finishing last week's work does not inflate this week's figure.
It is not decoration: the average of the last three completed sprints becomes the capacity Laimon plans the next sprint against. A project with no completed sprints has no signal yet, so it starts from an assumption and corrects itself once real weeks exist.
Treat it as a trend line, not a target. It becomes useful after three or four weeks and means very little before that.
Reopening something closed by mistake
An item marked Done in error can be reopened — back to the backlog, or onto the current sprint as Ready. It requires a reason, clears the closure markers, and deliberately does not rewrite the delivery record of a sprint that has already closed. A past week's velocity is a historical fact; correcting today's board should not edit it.
Reopening does not un-archive. An item swept off the board at rollover is restored from the Archive view instead.
Where credits are consumed
Grooming an item, planning a sprint, writing a work order, producing a digest and checking producing a digest all consume credits. Moving cards, reading the board, inviting colleagues and every MCP tool call do not. See pricing.