I am a Scrum Master of a team that currently uses multiple projects within Jira based on their mobile platforms. Based on whatI have used with Jira and Greenhopper, you lose some of the capabilities when you have a Scrum team utilize multiple projects that are setup in Jira with different components and versions. Questions.
1) Is it best practice to have one project setup as the scrum team when go off one backlog?
2) What are the limitations if a scrum sets up different projects for every platform that is developed? What is the suggested way of using Jira/Greenhopper for this type of scenario?
The new GreenHopper has been designed to deal with multiple projects as in reality, teams may need to handle issues coming from multiple projects, and at the same time need to prioritize. The main thing is to ensure that the team gets the work from a single backlog, so that there are minimum discussions on cross project priorities. That said, it become irrelevant as long as the team is just bothered to look at a single backlog.
If you are looking to manage the board using simplified workflow, then you do not have a choice, it has to be a single project per board.
We do not use the simplified workflow, so that should not be an issue. Our issue is having a way to indicate what sprint is what when the mobile projects we use have many different releases and we would have a mess of versions if we have to include the sprint (x) and release date when the classic board only pulls the fixed version and the component to help filter
For the first question, I personally recommend use a single project per board, I guess by using this way, you will have more freedom to check the reports and there will be no confusion but that depends on your requirements.
For the second question, as I have mentioned before you can use single project with single board but you can still use multiple projects per board and I don't think there will noticeable limitations.
Please let us know if you need any further questions.
Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the 104 years logged in 2017 , and we aren’t even through December yet....
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!
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