Options for 2 teams working off the same backlog

We are building a backog for one feature with user stories which will be worked on by 2 scrum teams.

We are not yet in a position to upgrade JIRA to 5 and so can't go to GreenHopper 5.9.x and use a RapidBoard. Not being able to add items to a Sprint (added in 5.9.1), is a blocker to replacing the task board for us.

Previously when working with mutiple teams under a same project we have used different fixVersions to filter the task board for each team.

We could also have a project context for each team, use the same FixVersion and filter on labels on issues.

I am wondering is there a smarter way. I have heard about hierarchical backlogs but not sure if relevant as we can't necessarily split our backlog functionally.

3 answers

1 accepted

This widget could not be displayed.

We have stayed with different fixVersions and find it a bit more intuitive than having different contexts. We have also added an issue type of story bug at the same level as sub-tasks.

We basically use boardtc's method.

We have a child fix version for each team, which rolls up under a sprint, then the sprint fix versions roll up under the release.

I think heirarchical backlogs are just another form of the child-parent fixversions. So why split out the backlog ... you only want to see it split out when the work is "in sprint".

This widget could not be displayed.

To handle multiple teams, it is not needed to have multiple fixVersions, as you said different contexts are sufficient. We had a Assignee changed to the team email-id and contexts were created based on this. That was sufficient to handle multiple teams.

Thanks. Do you see the team contexts as filtering on a label? That means that any new issues created (bugs) need to be laballed as well, I was hoping to avoid this step which is error prone. That's why I was wondeirng if there were smarter options.

No, we created the filters with two conditions.

  • With assignee as any of the team member or the common team email id

OR

  • Reporter as any of the team members (for Technical Tasks for Task Board usage for Sprint Burn Down)
This widget could not be displayed.

Folks, Nowadays Jira Server version have had for a long time the ability to create boards based on the users, etc. So we use that and run parallel sprints for a  project (one per each of the three sub teams working on this same product backlog).

But Jira reports are a mess with parallel sprints, specially gadgets and velocity. Do you have a solution for that?

Thanks a lot 

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted yesterday in Statuspage

What are your best incident management tips and stories? #HugOps

 👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...

70 views 2 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you