Skip to content

Module 02

Boards and sprints

A board is a view over work items, not a second place they live. Nothing on it is a copy of anything.

What it does

A sprint board with three lanes
A sprint board with three lanes
One board, several projects
A board draws from as many projects as you point it at, so a team working across three of them plans in one place instead of three.
Sprints with a goal and dates
A sprint carries a goal and a start and end date, and the schema refuses one date without the other. A half-dated sprint is the kind of record that quietly breaks every report downstream.
Shared or private
A private board is invisible to everybody else, and asking for one by URL returns a not-found rather than a refusal, which would confirm it exists.
The board is a view
Moving a card transitions the work item. There is no board-only state that can drift from the item's real status, because there is no second copy to drift.

What it is not

Naming the ceiling is what makes everything above it credible. The roadmap says which of these are deferred and why.

  • Ranked drag-and-drop ordering within a lane.
  • Automated builds or deployment integration.
  • Story points as a first-class estimate type. Estimates are durations.

The rest of the product

Try it against your own week

Log a real week of your own hours and put it through approval. That is a better test than any feature list, and it takes an afternoon.