How can have 2 scrum boards and 1 kanban that share one common backlog?

João Ribeiro July 24, 2024

Hi 

One project will now be handled by 3 different teams, and we want to share the backlog. How would you do that?

Some ideas that popped up are:
- Use a label and then configure the board with a specific filter.
- Use a component and then configure the board with a specific filter.

I would appreciate it if you have any other options that allow both teams to share a backlog but use different boards and also get separate insights...

Thanks in advance for all the help! 

1 answer

1 accepted

2 votes
Answer accepted
Hans Polder _Devoteam_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 24, 2024

HI @João Ribeiro ,

Welcome to the community!

To start: I would always recommend AGAINST using labels for this purpose. Labels are very prone to error (a small spelling mistake is easily made).

Components are indeed a good solution, you can find more information here as well: https://community.atlassian.com/t5/Jira-articles/How-to-use-Jira-Components-Tips-and-Best-Practices-Infographic/ba-p/2205935. You can then use filters like "project = XYZ and component = <subteam component>" to filter out only issues relevant for that team. 

You could also try looking into the 'Teams' functionality where you can create Atlassian-wide Teams, and also fill this information on issue level, and then use filters like 'Team = <id of the team>' for your board. You could let this work in tandem with components, using Jira Automation to automatically set the right 'Team' depending on which components are filled in (or maybe other (custom) fields that might lead to a specific team).

João Ribeiro July 24, 2024

Hi @Hans Polder _Devoteam_

Thanks, happy to be here!

Yes it makes sense. I'm going with the teams option since it looks the most appropriate one.

Can I have one single view of two teams? The catch here is one of them is using kanban and the other Scrum board...

Many thanks for the quick reply!

Cheers,

JR

Hans Polder _Devoteam_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 24, 2024

Hey @João Ribeiro ,

If you can put it in a filter, you can put it in a single view :-) But, you won't be able to work Kanban AND Scrum based on one board. What shared insight would you want from seeing both teams, compared to them having their own boards?

Maybe you could achieve such insights by creating a Dashboard, rather than trying to solve it in a board. If you really want a regular board, you can make a filter to contain both teams, but you'd still have to choose a type of Board to show it in, and in both cases you'll have issues (If you choose Kanban, you won't be able to see/work with the Sprints, and if you choose Scrum, likely some parts from the Kanban experience also won't work as expected.

João Ribeiro July 24, 2024

@Hey @Hans Polder _Devoteam_ 

Well this was just because we will share a daily and it was easier to only show one board. But since I wan't dif insights and the teams have dif methodologies I will keep them in dif boards.

Many thanks,

JR

Hans Polder _Devoteam_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 24, 2024

@João Ribeiro ,

I wouldn't know a foolproof method to combine it into one, it all depends on your workflow, statuses, etc. For now I would recommend using the separate boards, and once you're more used to this way of working, dive into options that might fit your situation in one (dash)board.

If you have gotten the answer you search for, would you mind hitting that 'Accept answer' button? It will mark the question as 'resolved', helping others prevent opening the ticket to help out, only to realize it's already solved ;)

João Ribeiro July 24, 2024
Like Hans Polder _Devoteam_ likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events