I am debating whether to open multiple Jira Software Projects or a Single one for the multiple teams.
A few things about the teams:
Hierarchy: Department -> Squad/Units -> Teams
The departments vary from R&D to Security, working on different projects and processes, but sometimes they have dependencies.
And within let's say Security Unit, there are multiple teams there and again work on different products/service and processes, but sometimes they have dependencies with other teams/departments.
Also on the department level, i would like to see the big picture of all the squads/units.
Note that some of these teams, some of their requests derive from Jira Service Desk (SD), yet haven't decide whether to move these requests to Software, or leave them in SD due to the Agent licenses costs.
I know there is pros/cons to both options, yet would love to hear you feedback on what works for you in these cases.
Hi @Meytal BM
Just answering at a high level and with respect to Agile, not Jira specific. The general rule is that you have ONE backlog per project, regardless of how many teams are working on that project. Now I know that the definition of "project" can vary and if it's a monster huge project you may opt to split it into more than one backlog.
Jira easily handles multiple teams working from one backlog, be it Scrum or Kanban. Handling dependencies isn't always quite that easy in any of the Agile software packages that I've used. At my previous company we used an Excel spreadsheet with a section per team - the key for success is to ensure that any teams involved with a dependency have a discussion and come to an agreement. Then review regularly so that no-one loses sight of the dependencies.
Thanks again @Warren .
I think it makes sense (to me at least) that each Squad has it's own project regardless how many teams it has within that Squad.
As for dependencies, although I fully agree that collaboration is the key, there still needs to be a best practice on how to reflect that within the tool.
Let's say we need to develop a Report. This reports requires different teams from different Squads. In this case there are various way to go about it:
1. Each Squad/Team open their own Epic associated to this Report, then add a "label" that reflects these Epics are associated to this "Report". I am not keen on using Linked Issues in this case. Is there any other way?
2. One team takes ownership and opens a single Epic for this "Report" within that Squad's project, then opens stories for other Squads. The advantage is that it's a single Epic consisting of all the tasks, the downside, it's in a single project and that gets messy when doing quarterly planning sessions (based on Epics), as it wont show up in another's team Epic backlog. I usually tend to go with #1 above.
With both cases, there needs to be collaboration and agreement.
What are your thoughts?
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events