Scrum Board Templates
Find Your Use Case
Built for a specific kind of work. Each one opens in ClickUp, ready to customize.
Scrum Board Template for a Single Team
Best for A single team running 2-week sprints
The Sprint Board framework for one Scrum team. Five columns, sprint-bounded, with WIP limits and a burndown chart that updates as cards move.
Scrum Board Template for Multiple Teams
Best for A Scrum of Scrums across 3 to 5 teams
The Portfolio Scrum Board framework. Team swim lanes, program epic rows, cross-team dependency flags, aggregated velocity, and PI planning columns for a Scrum of Scrums.
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.