Scrum Board Template for Multiple Teams
Scrum Board Template for Multiple Teams
A multi-team portfolio Scrum board in ClickUp that rolls sprint work across three to five teams into program-level epics with cross-team dependency tracking.
Free, ungated, opens in Portfolio
- Team swim lanes for 3 to 5 teams
- Program epic rows that group team stories
- Cross-team dependency flags
- Aggregated velocity tracking across teams
- PI planning columns
- Rollup Dashboard for program status
How to Use This in Portfolio
Open the portfolio board in ClickUp
Click Use This Template. It loads as a Folder with a List per team and a program-level Board view that groups work into swim lanes by team.
Set up your teams as swim lanes
Rename each swim lane for one of your three to five teams. Each lane reads from that team’s List, so individual teams still work their own board while the program sees everyone at once.
Create program epics
Add Epic rows for program-level goals, then link each team’s stories to the epic they serve. The board rolls story status up to the epic, so leadership sees epic progress without reading every card.
Flag cross-team dependencies
When one team’s story blocks another’s, use the dependency link between the two tasks. Dependency flags surface on the board so the Scrum of Scrums can clear blockers in its sync.
Track aggregated velocity and plan increments
The rollup Dashboard sums velocity across all teams and maps work into PI planning columns. Use it in increment planning to commit the program to a realistic amount of work.
Who This Is For
Programs running a Scrum of Scrums
Coordinators of three to five teams who need a program view without losing each team's own board.
Release train engineers
Leads running SAFe-style program increments who need epics, dependencies, and aggregated velocity in one place.
Leadership tracking a program
Stakeholders who want epic-level progress and cross-team risk without sitting in every team's standup.
Frequently Asked Questions
Yes. The board is free to add to any ClickUp Workspace. Coordinating multiple teams tends to use more automations and Dashboard widgets, some of which scale with paid plans, but the core multi-team structure works on the free tier.
When one team’s task blocks another’s, you link them with a ClickUp dependency. The board surfaces a flag on dependent cards, giving the Scrum of Scrums a clear list of blockers to resolve in its regular sync.
Yes. Each team works its own List and board, and the portfolio board groups those into program swim lanes. The two views read the same task data, so nothing is duplicated or out of sync.