Best way to give a sub-team its own scoped agile reports (velocity/burndown)

[Bailey Lissington]

We're on Jira Cloud Premium. A larger team works in one software project, and within it we have smaller sub-teams. Each sub-team would like its own velocity, burndown, and sprint report — scoped to just their work — while we keep a single cross-team view (we already use Plans / Advanced Roadmaps for the roll-up).

What I've found so far:
• The project is team-managed, so it has a single board — I can't add a second board scoped to a sub-team.
• Board and backlog filters (assignee, labels, custom filters) only filter the view, not the reports.
• The velocity chart, sprint burndown, and sprint report are board/sprint-scoped and can't be narrowed to a sub-team.

Given that, what does Atlassian recommend for this situation? Specifically:

1. Is the recommended pattern to give each sub-team its own team-managed project (so each gets its own board, sprints, and reports) with Plans rolling them up — or to move to a company-managed project with one board per sub-team, or something else?

2. Does the answer depend on whether each sub-team runs its own sprints vs sharing one team-wide sprint? If sub-teams share a sprint, is there a supported way to get per-sub-team velocity/burndown, or is the team-level number the only meaningful one?

3. If splitting or migrating is the recommendation, what are the main tradeoffs and gotchas to plan for (sprint history, components, custom fields, the estimation field)?

We're trying to keep the setup as simple as possible and avoid unnecessary structure or paid add-ons if native Jira can handle it. Thanks!

[Danut M _StonikByte_]

Hi @Bailey Lissington,

Unfortunately, there is no easy way to handle this in Jira without using an add-on, especially when using team-managed projects.  

If you decide to use an app from the Atlassian Marketplace, you can solve this requirement easily with the gadgets provided by our Great Gadgets app.

Solution using Great Gadgets:

1. Create a Jira dashboard to track your cross-team (global) project and add all the necessary gadgets, such as:
   • Sprint Burndown
   • Release Burndown
   • Velocity
   • Cumulative Flow Diagram (CFD)
   • Cycle Time
   • Pivot Tables
   • Formula gadgets
2. Use the Great Gadgets Controller gadget with predefined presets (filters) for each team, allowing you to switch views and visualize data for individual teams or the entire project. When you click Apply the selected team filter will be propagated to the other app gadgets from the dashboard showing the diagrams for that team.

With this approach, your existing Jira setup remains unchanged while providing an effective and flexible way to monitor progress at both the global project level and the individual team level.

If you have any questions, feel free to contact us at support@stonikbyte.com.  

Danut.

[Alexey Pavlenko _App Developer_]

Hi  @Bailey Lissington ,

Yes, usually people create boards per smallest group of people. Especially when you need separate reports. But it comes with a trade-off, you will need to switch between team reporting tabs constantly in order to check each report. If you need a unified view, you can try the app I developed - Multi-team Scrum Metrics & Retrospectives.

With it, you can:

• Track:
  • Data across sprints, months, quarters, half-years or years. 
  • Several teams (including those ones sharing the same project) at once.
  • Velocity, capacity, allocation, completed story points (completed scope), planned (initial, final scopes), added and removed scopes, as well as other metrics. You can even create your own custom metrics using JQL.
  • Trends and average metrics across periods.
• Conduct Quantifiable retrospectives.
• And many more.

3 boards/teams in the same view, 1 period selected for analysis:

3 boards/teams in the same view, all periods are clicked for average metrics and dynamics:

Best regards,
Alexey

[Tomislav Tobijas]

Hi @Bailey Lissington ,

I'm not a fan of team-managed spaces, but you do exactly that > multiple team-managed spaces (one per sub-team).

Now, what I implemented last year was for an org that uses the Spotify model (Tribes, Squads...), where we used company-managed spaces with separate boards. 👀
Basically:

• Space = Tribe
• Board = Squad (one per sub-team in your case)

I haven't migrated the existing approach to another, but I'm pretty sure that the sprint history does not migrate. Fields, on the other hand, are easier, but you'll still need to follow some specific steps (one example article here).

In the end, it might be a bit time-consuming and will require prep., but if you ask me, I'd go with company-managed spaces as you'll probably resolve pretty much everything with that. 🤔

Cheers,
Tobi