Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Optimal Jira Configuration for one scrum team, multiple platforms

Joe Spadoni
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 28, 2018

I have searched the Community articles and can't seem to get a great answer for this. 

I recently adopted a product and formed one scrum team to develop in multiple platforms (iOS, Android, Server).   We just started regular sprints and it is difficult to manage multiple backlogs feeding one sprint.  Is it better to:

  1. Move things to one project and use Components(?) to segregate platforms?
  2. Keep separate projects and pull the priority items from each into the sprint and view and manage them some other way?

The platforms are on different release cycles.

1 answer

1 accepted

1 vote
Answer accepted
Scott Theus
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 28, 2018

Hi @Joe Spadoni,

There are, as you've guessed, a number of ways to handle this, at the highest level you'd either have one project with different components or multiple projects under a single program.

Since you have one scrum team that works one sprint at a time I suggest using one project with either Components or Releases..see  Configuring Versions in a Scrum Project  and Deploying a Release.

I like Release better, since as your team works  through your sprints you can monitor the progress using the Release Burndown Chart.  Meanwhile, your sprint burndown will let you keep tabs on each sprint. 

Hope this helps, 

-Scott

Joe Spadoni
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 28, 2018

Thank you Scott.  I prefer the one project approach so will give it a try.  Using releases to differentiate issues.  Since release is visible on issues in the backlog without clicking into them.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events