Jira Classic - What is the best practice? One programme, two teams, multiple workstreams

[Meena Kanagavel]

Hi there, wonder if you can advise me?

I am a product owner, working on a large programme that contains multiple workstreams. We have two feature teams and we work on fortnightly sprints. 

Would it be better to have a separate projects set up for 2 teams so they have a clear view of their backlog and workstreams? Or can we set up two boards within the same project? 

There are a few dependacies better the workstreams and the workload might shift now and again between the two teams - so would like to know the best practice in Jira Classic please.

Many thanks 

Meena

[Marieke Bouwman]

Hi Meena, Hi Community

I was looking for the same answer on this question. Is there a custom field that can be used to make sure tickets 'land' a specific board (1x Jira Project and 2x Work streams (teams) with each their own backlog and  board)

How do I make sure tickets are 'seen' for a specific team.

Target scenario:

Jira Project AB

Team (Board) A, seeing tickets tagged or labelled with A (> what 'field' to use? ) 

Team (Board) B, seeing tickets tagged or labelled with B (> what 'field' to use? ) 

Thank you, 

[John Funk]

Hi Marieke - Welcome to the Atlassian Community!

First, it is always better to post a new question to the Community instead of adding to an already old post. That way many more people will see your question. 

For this, however, yes you can create Components on the project and use that value as a part of the board filter for each board. So the filter would look like:

Project = ABC and Component = 123 (Board A)

Project = ABC and Component = 456 (Board B)

[John Funk]

Hi Meena - Welcome to the Atlassian Community!

If the teams are very separate from each other, I would create two separate projects. I tend to equate that a Project in Jira equals a Team, not a true project in the regular sense. 

[Meena Kanagavel]

Hi John, thanks but not sure if I had explained fully, sorry bear with me.

the teams are NOT very separate - sometimes development teams cross over between the 2 teams.

Both the teams are working in one big programme but we have multiple workstreams that the 2 teams are working on. And there are dependanices between the workstreams so we will need to link the issues up as we progress into the programme. 

Also, we have a list of BAU changes (ever changing) that will need to be priortised and assigned on a ongoing basis. Hence thought it would be best to keep them in one project so the BAU issues can be dragged and dropped between the 2 boards. 

We would like to have 2 sprints running at different timelines, and would like to get the velocity and reporting done correctly in the due course. So please advise what is the best approach in setting the Classic project?

Many thanks 

Meena

[John Funk]

I am not familiar with running 2 sprints at the same time from the same project. But as you further describe it, I would indeed use a single project with multiple boards. 

[Meena Kanagavel]

Ermm...sprints not running at the same timelines though!!

I am looking to run parallel sprints (with different timelines) for the same programme (Project), is this not a standard practice? ie. say, team 1 sprint will run from 06/04 to 20/04 and team 2 sprint will run from 13/04 to 27/04 

So, I have got one programme (project) with multiple workstreams; allocating the worstreams to 2 teams. So I will have 2 separate board so the 2 teams will have their own backlog items for each board. Hence the 2 sprints (or parallel sprints) at different timelines.

Can Jira Classic support running parallel sprints under each board, and would it allow us to measure progress report for each board separately, when we set up as a single project? Please confirm - as my senior mgt wants to see the velocity of each team in a few months time. 

Thanks Meena

[Jack Brickey]

Hi Menna,

Yes you can do what you are asking in a single project. Separate boards with their own sprints and own backlogs. You will just want to ensure that the two don’t overlap in how they are defined (filters). It might be that you use the Components field to separate the two teams and require the component to be selected during creation of the issues.

[John Funk]

Hi @Meena Kanagavel  - Did this ever answer your question? If so can you click on the Accept Answer above so we can close this one out?