Recommendation on Jira Board setup for engineering org with 8 teams using one Space

[David Ludwig]

Hi,

Looking for recommendation for a Jira board setup for a small organization with 8 teams of 1-3 engineers to migrate from single Kanban board with 8 swimlanes (one per team) within one Jira Space and Jira tickets use Components for each swimlane to divide the work. Goal to migrate all teams to using a Scrum board approach, unified method for reviewing progress across all teams and minimize the overhead of using Jira with Scrum.

Our company uses Enterprise Jira. What is the best approach? Have all 8 teams setup individual Scrum boards and continue to leverage the Jira backlog of tickets with components for each team? How do we manage across the 8 Scrum boards? Any Jira documentation on best approach for this scenario?

Thank you,

Dave

[Viswanathan Ramachandran]

Hi, You can create 8 individual Scrum boards using existing saved filters based on Components.

1. This gives each team independent backlogs and sprints without moving tickets.
2. Use Plans (Advanced Roadmaps) to pull all 8 boards into one master timeline for high-level progress and dependencies.
3. Sync all teams to the same 2-week sprint dates.
4. Hold joint Sprint Planning, Retrospective across teams instead of 8 separate meetings.

Note: I'm not recommending a single Scrum board with Quick Filters for all 8 teams because you end up with sprint clutter and backlog chaos. Sprint reports won't be accurate. 

[Joshua Brock _ Seibert Group_ GmbH]

Greetings @David Ludwig and welcome to the Community!

Viswanathan's approach is solid for where you are today: individual Scrum boards per team (built from saved filters on Components), synced sprint cadence, and Plans for the cross-team rollup. That gets you real per-team velocity and backlog hygiene without forcing all 8 teams to fight over one board's Quick Filters, which as he noted gets messy fast once you're past 3–4 teams.

A couple of things worth deciding up front before you migrate:

• Keep Components as the team-scoping mechanism (not a custom field), since it's what boards and filters already understand natively.
• Decide now whether cross-team work items get their own parent per team or stay linked across teams as retrofitting that later is the painful part :-(
• Since your goal is a unified way to review progress across all 8 teams, plan for a shared sprint cadence (same length/start date) from day one.

If what you're really building toward is a full Agile Release Train (ART) (one program cadence for 8 teams, not just 8 independent boards) that's a structured multi-team/PI Planning setup, and there are Marketplace apps built specifically for it. Agile Hive is one, built natively in Jira:

• A Program Board that sits alongside each team's own Scrum board, so you get the cross-team view without replacing what teams already use.
• Automated detection and visualization of cross-team dependencies, so you're not tracking "what's blocking what" across 8 boards by hand.
• ART & Team Reports covering load vs. capacity and predictability across all 8 teams in one place.
• A SAFe Hierarchy (Epics/Features linking down to team-level work), so cross-team and parent/child structure doesn't rely on someone maintaining Component filters correctly forever.

Worth being upfront: this is aimed at organizations running (or moving toward) a formal multi-team planning cadence. If you just need 8 clean Scrum boards with occasional cross-team visibility, Viswanathan's native approach above is the lighter path, and I wouldn't add an app just for that.

You can find more details at agile-hive.com.

Disclosure: I work at Seibert Group GmbH, the team behind Agile Hive.

Hope this helps! Again, welcome and best of luck!

Joshua
Content Writer & US Representative
Agile Hive and Aura Apps (products of Seibert Group GmbH)

[Alexey Pavlenko _App Developer_]

Hi @David Ludwig ,

How much do those 8 teams have in common? Is every component - a separate domain? If so, what you are doing makes sense, but keep in mind that in this case you normally have separate Scrum Events, along with a separate Scrum-of-Scrums meeting where one person from each team attends for a cross-team sync.

If the components are tightly coupled and the teams share the same context, but you simply want to migrate to Scrum - just go with one Scrum board/team for a light-weight setup.

If you decide to have 8 teams, I recommend the app I developed for this use case - 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