Cross-team planning template

Schedule and assign work, manage capacity, and track progress across multiple scrum teams.

Use template

BEST FOR

Software development

KEY FEATURES

Plan
Custom reporting
Capacity management

What is a cross-team planning template?

The cross-team planning template is pre-configured to help multiple scrum teams work autonomously in separate boards while coordinating seamlessly in a single project. By bringing the project into a plan, program managers and team leads have a shared space where they can track progress and manage capacity on a sprint-by-sprint basis.

What does the cross-team planning template include?

Plan work across scrum teams

Under the project board, you’ll notice we’ve created two scrum boards; one for each team contributing to the project. Issues from both boards have been brought into a plan, where a program manager or team lead can easily track each team’s progress and the overall project timeline in a single view.

How to get started with the cross-team planning template

This template uses Jira Premium to help you plan work across multiple scrum teams.

1
What your template comes with
This template creates:
A new project
The project is where you’ll contain all the work required to achieve a certain goal or outcome.
Two new teams
These teams contribute to the shared goal or outcome by completing project work assigned to them.
Two scrum boards
Each team has their own scrum board to manage and track their work autonomously.
A new plan
All project issues and teams have been brought into a shared plan for visibility and coordination.
2
Add issues to your plan
Start populating your plan by creating issues for project work required. Plans is a sandbox environment, allowing you to safely edit issues and publish changes to Jira once ready. As issues build up, apply filters and view settings to organize and track your work.
Optionally, you can add existing issue sources (projects, boards, filters) to your plan under Plan settings. Learn more about changing issue sources in your plan.
3
Change teams (optional)
Next, add an existing project, board, and/or filter to this plan. In a plan, we call these issue sources. For this template, we recommend that you use issues from company-managed projects, and that they contain at least one epic. Learn more about issue sources in Plans.
4
Create sprints in your backlog
Navigate to the each team’s project backlog to create sprints. Learn more about creating sprints in company-managed projects.
5
Allocate capacity in your plan
In the timeline view of your plan, start assigning issues to teams and sprints using the Team and Sprint fields. Learn more about how your plan assigns capacity.

Increase visibility
Keep teams aligned and focused on the right things by enabling teams to see how their work contributes to larger business initiatives.
Collaborate across teams
Create a single source of truth where everyone can see who’s doing what and when, and reports can be customized for different stakeholders.
Scalable structure
Organize and visualize relationships between work items from the day-to-day tasks to quarterly initiatives, spanning multiple teams and projects.