nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Board Structure Question

JRodney Estrada

Hi all,

I'm not sure how to answer this question from a user. Any insight would be greatly appreciated!

QUESTION:

"We have a Program that will have 2 major projects, and within those projects, multiple workstreams, all using Jira as the tool. I have a setup question. Team 1 has a board "ABC Board", and has created 20 epics. Team 2 will need a board, and my question is whether I should setup a new project for that workstream OR, setup a new board within the existing Project Galactic. If I do setup 9+ scrum teams in the single project, each with their own boards, I am concerned that I will not be able to cleanly manage each individual teams work. What do you recommend for this many simultaneous teams? Multiple boards in one project, or multiple projects?"

Many thanks!

Accepted answers

John Funk

Hi @JRodney Estrada - If you have separate projects for each team, then you should probably have separate boards for each team.

If all of the teams are working in the same project, then you could get by with a single board that uses quick filters based on Components or some identifier for each team.

All comments

Stuart Capel - London

Hi @JRodney Estrada

I would definitely advise to go with a new project, and create a board in one of those projects that contains both projects if you want to see the issues all in the same board.

Boards are good for displaying issues in different ways but you're better off recording all the issues from each project at project level.

John Funk

Hi @JRodney Estrada - If you have separate projects for each team, then you should probably have separate boards for each team.

If all of the teams are working in the same project, then you could get by with a single board that uses quick filters based on Components or some identifier for each team.

JRodney Estrada

hi @Stuart Capel - London ,

good to know, thank you sir!

Manali Butey_74pgd2

Hi @JRodney Estrada Based on my experience on large scale digital transformations, this is a tricky question to answer and ans depends on multiple factors such as admin resource capacity, the depth of Jira use, reporting requirements, and level of user’s experience with the tool.

if you plan to use the release and component functionality it will be hard to mage the versioning if you have your build team and test team using different projects. You will have to manually align the versions and mange the release notes per team.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

jira-cloud