Guide

A sprint board only works if everyone reads it the same way. This explains what each part is for, who is allowed to do what, and where the data actually sits.

The problem it solves

A team does a fixed amount of work in a fixed stretch of time, and everyone needs the same answer to three questions: what am I doing, will we finish, and what is stuck. This board holds one project as a set of issues — a story, task, bug or chore — grouped into epics (themes of work that outlive a sprint) and scheduled into sprints (a dated stretch, usually two weeks).

What makes this one different

Two rules that most boards leave to good intentions are enforced here. First, done is granted by a tester, not claimed by the author — an issue with a tester cannot reach Done until that person passes it. Second, what is said at stand-up is written onto the issue, so a blocker raised on Monday shows on the card instead of living in someone’s notes.