What a Sprint Board Is For
A sprint board is a visual representation of all work committed to the current sprint, organized by status. It answers three questions at a glance:
- What’s not started?
- What’s in progress (and by whom)?
- What’s done?
If your sprint board can’t answer these questions within 5 seconds of looking at it, it’s not working.
The sprint board is not a reporting tool (that’s analytics), not a backlog (that’s your prioritized queue), and not a project plan (that’s the Gantt chart). It’s the real-time state of the current sprint.
Setting Up Your Board
Columns = Statuses
Each column on the board represents a status in your workflow. The most important design decision is choosing the right columns.
Too few columns (just Todo/Done) — you lose visibility into where work actually is. Everything is “in progress” until it suddenly appears in Done.
Too many columns (7+ statuses for a sprint) — the board becomes cluttered and cards spend time in transitional states that don’t represent real work stages.
The sweet spot for most engineering teams:
- Backlog (not started yet)
- In Progress (someone is actively working on it)
- In Review (PR submitted, waiting for review)
- Done (merged, deployed, or accepted)
Add columns only if your process has a genuine stage that requires visibility. “Ready for QA” is valuable if you have a separate QA process. “Blocked” is useful if blocked items need to be visually distinct.
Cards = Tasks
Each card on the board is a task committed to the sprint. The card should show:
- Title (enough to identify the task without clicking)
- Assignee (who is working on it — avatar or name)
- Priority indicator (if relevant)
- Any blocking indicators
Keep cards clean. If every card shows 8 fields of metadata, the board becomes unreadable. Show what matters for the board view; put the rest in the task detail.
WIP Limits
Set work-in-progress limits on the “In Progress” and “In Review” columns. This prevents work from piling up in any stage and makes bottlenecks immediately visible.
A starting point: WIP limit per column = number of team members × 1.5. Adjust based on how the team actually works.
Maintaining the Board
The Board Must Reflect Reality
The sprint board only works if it’s current. A card that’s been in “In Progress” for 5 days but was actually abandoned 3 days ago is misinformation. A card in “In Review” that was merged yesterday is stale.
Making the board easy to update is the best way to keep it current. This is where tool speed matters — if updating a status takes 50ms (FlowEra) versus 2 seconds (traditional tools), people update reflexively instead of batching updates for later.
Daily Board Review
Replace (or supplement) the daily standup with a board review. Walk the board from right to left:
- Done: Celebrate completions. Brief — these are already finished.
- In Review: How long has each item been waiting? Is anyone blocked on a review?
- In Progress: Is anything stuck? Does anyone need help?
- Backlog: Is the remaining work achievable in the time left?
This takes 5–10 minutes if the board is current. It takes 30 minutes if the board is stale and the team is explaining discrepancies.
Sprint Board in FlowEra
FlowEra’s Kanban view, filtered by the current iteration, is your sprint board. It shows only tasks assigned to the active sprint, organized by your custom status model. Drag cards between columns to update status. Click a card to see the full detail, comments, and linked documents.
The board updates in real time across all team members. When a teammate moves a card, you see it move — no refresh required. The burndown chart at the top of the view shows remaining work against time.
For distributed teams, the sprint board is the single artifact that everyone references. It replaces status meetings, Slack questions about progress, and spreadsheet-based tracking.