Hi, I'm new in Jira.
I have the following scenario:
Given that squads have different downstream workflows, what is the best way/good practice to configure this in Jira?
Hi @Dionei Piazza - Welcome to the Atlassian Community!
One way to solve that is with a single project and workflow like you have it.
Then create a Group for each Squad and place the members in it.
Then put Conditions on the Transitions to the phase that allows only that Group (Squad) to access it.
Another way to do it with the same project and workflow is to create a custom field with multiple select. We call it Dev Needs. Then put the optional phases in the field. The user then selects the check box for the applicable phase.
Then put conditions on your transitions again that check the Dev Needs field (or whatever you might call it) for that phase value.
That is a quick solution although maybe not all that clean. It works for us though.
Hello @Dionei Piazza
I'd sit more on the side of 'multiple projects', one per squad. It has great benefits and aligns with the needs you present:
The issue I've seen raised in the past with this sort of system is that squads have less visibility over what the other squads are doing. We overcame this by having our squad sync up during demos.
Hope this helps you better weigh out your options
@Fernando Bordallo and about Kanban metrics?
Lead time, Throughput, Flow Efficiency, Predictability (Monte Carlo), etc.?
We know that Jira is not the best in the clarity of the reports. That's why most people use Actionable Agile solution.
Can I use Actionable Agile with multiple projects? Or in this case would be better a single project (with different boards per squads) and filter them in Actionable Agile with the labels?
I can't say, to be honest. I haven't used Actionable Agile before. However, the docs presented don't give insights into how it can best be leveraged. I would assume it will be driven by JQL, at which point it becomes purely a matter of personal taste. Project split vs backlog managed-split
hey @Dionei Piazza thanks for letting me know your direction. So just so i get it right, because the teams/squads have different flows, you decided to create a project per squad?
Since we have various teams, some will have one project for all sub-teams, and some project per sub-team. It also depends if they need to use the same workflow, etc.
In regards to dependencies, what have you decided to do in this case?
Hi @Meytal BM
Well here the answer is a little bit longer and I think we can break it down.
1 - "So just get it right, because the teams/squads have different flows, did you decide to create a project per squad?"
> Yes, as a matter of organization and maintenance effort, I've decided for each squad to have its own project.
2 - "In regards to dependencies, what have you decided to do in this case?"
> To resolve this point, the solution will depend a lot on which Jira version you have.
Here we use 100% Kanban and we have the Jira Software Standard version. To resolve dependencies, we create a custom field called "Squad". It's a list with the names of all our Product/Engineering squads. This field is displayed for all issues types. With that, a "project A", with the "squad XYZ", can inform that a certain card of that "project A" is being attended by the "squad KFG" that can be part of the "same project", or even be allocated to a different project, such as "project B".
With that, you will have to work your Reports to use this Project and Squad filter. If you use something like Nave Analytics, it will work even better!
Another option to solve this is to use the Jira Components feature.
Note:, If you have the same version as we have, remember that the Roadmap feature only works for one project. So if you want to see more than one project on the Roadmap, get ready for a license ($$$$$$) of Jira Premium that is double the value of Jira Standard, and even then, it's not a robust and flexible solution for understand Portfolio.
Was I able to help you? If you have more questions (because it's a more complex matter), you can send an invitation to a call and we'll resolve your context. My email is firstname.lastname@example.org
Hi community 👋, as every Monday we're bringing you a quick update on what happened in the Atlassian ecosystem last week. There were a few interesting events like for example the announcement of th...
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