Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to have one common backlog for two scrum teams.



Looking for some advice on the following subject.

Currently we have one large scrum team that we are splitting into two scrum teams. The two scrums teams will work on one product backlog as they are working on one product. 

How do we setup our boards in itrack to meet the following? 

• Stories created and pulled from one common backlog

• Report on each scrum team metrics separately (burndown, velocity, predictability, etc…)

• Run separate sprints for each scrum team

Thanks in advance for any advice you may have.

2 answers

1 accepted

0 votes
Answer accepted

Hi @Jeremy Dickens -- Welcome to the Atlassian Community!

For a question like this, you may want to work with your site admin to contact the vendor's support team at iTrack for help.

Kind regards,

Thanks Bill, we are working with our site admin but not happy with what is being proposed. I am curious how others have solved so I can come better prepared with alternative solutions.

Gotcha... Inside of Jira, you would have different options, depending on your project type: company-managed or team-managed.  For example in company-managed, you could use something to distinguish teams (like components) and use separate boards and sprints for one project.

I am not familiar with iTrack, so I am unable to help with that tool.

Thanks again Bill, we will take a look at that.

Like Bill Sheboy likes this

We solved it that way:


We created a Project e.g. "Changes" where all Change Request were put in.

We created for each of our 3 Teams an own project. e.g. Team "WEB", Team "PHP", Team "Ruby"

When a PO of a team is taking an EPIC of "Changes" he is replacing the "Auth" Attribut , tags it with the label "WEB". When writing a story / Task for his WEB Team he simply puts the Epic link attrib to the parent EPIC in "Changes".

So the sprint where maintened independently from the other teams, but they are alle fed by "Changes" which can be considered as the company product back log.


So we literally have a hiearchy with Jira projects: Level 1 "Changes" (containing the Changes which are EPICS)

and e.g. Team Projects e.g. "WEB"  or "PHP" which are containing Stories and Tasks of the Teams including their sprint administration. So ech sprint have their own sprint boards and we still have an overview how they are doing when we look at the "Changes" boards where alle Epics are being located. When you drill down the EPIC you can see which Team with which stories they are working on. Nice. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events