Sprints

A sprint is a named window of time with a goal. Sprints are optional — plenty of teams run this board as a pure flow system — but they are the cheapest way to answer “what are we doing this fortnight?”.

The three states

State	What it means	Action available
Planned	Scoped but not started. Fill it while the current sprint runs.	Activate
Active	The sprint in flight. Shows a live time and task progress bar.	Complete
Completed	Closed. Kept as a record — the dashboard still counts its work.	—

Each card shows the date range, the length in days, and how many of its tasks are done. An active sprint adds two bars worth reading together:

• Time — how much of the window has elapsed.
• Tasks — how much of the work is finished.

When Time runs well ahead of Tasks, the sprint is behind. That is the entire report.

Running a sprint

1. New Sprint — name it, set start and end dates, and write a goal in one sentence. A goal like “Self-serve plan changes and a usage-based invoice preview” is worth more than a list of task keys.
2. Assign tasks — open a task and pick the sprint in its details rail, or set it from the list view.
3. Activate when the window opens.
4. Complete when it closes. Unfinished tasks stay on the board; move them to the next sprint or back to the backlog deliberately.

Focusing the board on a sprint

The board header carries a sprint scope next to the project description — All tasks by default. Switch it to a sprint and the board shows only that sprint’s work, which is the view you want in a standup.