Sprint Board

A working board with the vocabulary you will hear on your first engineering team. The columns are not the lesson — the lesson is what the board makes visible: how much you committed to, what is actually moving, and what has been stuck for three days while nobody said anything.

How to use this tool

Set up the sprint: a name, a start date, a length, and a capacity in points — how much your team believes it can finish. If you have no history, guess, then correct it next sprint from what you actually finished.
Add work items to the Backlog. Give each one a size in points.
Pull items into To Do until you reach capacity. Stop there. That decision is the sprint commitment.
Move items with the status dropdown on each card. When something is blocked, say what is blocking it — a blocker with no reason attached cannot be helped by anyone.
Once a day, click Record end of day. Those snapshots build the burndown, which is the only chart that tells you whether you are going to make it.

On story points: they measure relative size, not hours. A 2 is roughly twice a 1. The sequence skips numbers on purpose — the difference between 8 and 13 is real, the difference between 8 and 9 is imaginary precision. Anything you would call a 13 is usually a story you have not broken down yet.

How this maps to Jira and similar trackers

Mapping between this board and common tracker vocabulary
Here	Jira	What it means in a standup
Work item	Issue (Story, Task, Bug, Sub-task)	"Who's on ENG-214?"
Points	Story Points	"That's not a 3, that's an 8"
Columns	Board columns / workflow statuses	"Is that in review or done-done?"
Blocked	Flagged issue, or "is blocked by" link	"I'm blocked on the vendor spec"
Capacity	Sprint commitment, informed by velocity	"We can't take that on this sprint"
Snapshots	Burndown chart	"The burndown's flat — what's actually done?"
In Progress count	WIP limit (kanban)	"You've got four things open"

Two honest caveats. First, teams disagree bitterly about almost all of this — whether to estimate at all, whether burndowns help, whether standups are worth the interruption. Walking in with strong opinions about someone else's process is a bad first move; understanding the vocabulary so you can follow the argument is a good one. Second, velocity gets misused as a productivity metric by managers who should know better, which is why some engineers react badly to being asked about points.

Sprint setup

Sprint name

Start date

Length (working days)

Capacity (points)

WIP limit per person

Add work

New work item

Title

Type

Points

Assignee

Added mid-sprint yes

Board is empty.

The board

Burndown

Record the remaining points at the end of each working day. A burndown you update once, at the end, is a drawing, not a chart.

Remaining points at the end of each day, against the straight-line ideal.
Day	Remaining	Ideal	Standing

What the board says

Add some work and observations will appear here.

Reflect

If this sprint ends and one item does not get finished, which one should it be — and who else needs to know that now rather than on the last day?

Keep your work

This tool remembers your work in this browser on this device. Nothing is sent anywhere.

Autosave is on.