Scrum Board Templates
Which Framework Fits Your Decision
Each template scores tasks on a different set of factors. Match the framework to the call you're making, then grab it below.
Browse the Frameworks
Every framework, ready to open. Preview the layout, scan how it scores, and grab the one that fits.
Most used
Sprint Board
Best for Single team, 2 week sprints
A standard Scrum board with Backlog, To Do, In Progress, Review, and Done columns, wired to sprint boundaries and WIP limits.
Portfolio Scrum Board
Best for Scrum of Scrums, 3 to 5 teams
A multi team board that rolls up sprint work across 2 to 5 teams into program level epics with cross team dependency tracking.
When to Use Each Scrum Board Layout
The Sprint Board is the starting point for any team adopting Scrum. It enforces the core workflow: stories move from Backlog through active columns to Done within a time boxed sprint. The WIP limits prevent the team from starting more work than they can finish, which is the single highest leverage practice for improving throughput.
The Portfolio Scrum Board adds overhead that only pays off when multiple teams share dependencies. A single team using this template will spend more time maintaining swim lanes than delivering stories. But a program with 3 to 5 teams that routinely block each other on shared APIs, design assets, or infrastructure work will catch those blocks weeks earlier.
Getting the Most From Your Board
The board is a communication tool, not just a task tracker. During daily standup, walk the board right to left (starting from the Done column) to surface blocked items before discussing new work. This keeps the team focused on finishing work in progress rather than starting new items.
Review WIP limits at the end of each sprint during the retrospective. If the team consistently hits the limit in one column (usually Review), that column is a bottleneck worth solving. Common fixes: pair programming to double review throughput, automated test suites to reduce manual QA time, or staggered story sizes so reviews arrive at a steady pace instead of all at once.
Frequently Asked Questions
At minimum: Backlog, To Do (committed to this sprint), In Progress, and Done. Most teams add a Review or QA column between In Progress and Done. Avoid more than 6 columns. Each additional column adds process overhead without improving flow unless it represents a genuine handoff between different people or roles.
Technically yes, but it defeats the purpose. Scrum boards work because they update in real time as the team drags cards. A spreadsheet Scrum board requires manual cell updates, provides no WIP limit enforcement, and cannot send notifications. Use ClickUp, Jira, or any board tool with drag and drop and live updates.