Here is my requirement
I have multiple projects and a single core team. I want to split the team into 3 teams who will be working on the same backlog items.
I tried searching legit jira solutions, but couldn't find anything. I could see some work arounds but not sure what the cons are.
Plus most of the solutions are from 2013-14. I am using the latest version of classic board. NOT next gen
I always recommend people to look at boards as the home for work of a single team. Ideally, a team has one single board where all its current work can be scheduled and moved from to do towards done, visually. Whether that should be a scrum or a kanban board is very much depending on the type of work (is your team responsible for defining and scheduling its own work up front eg versus is it handling incidents that come in as they occur, e.g.) and your internal planning processes.
Having separate boards for each team creates focus for your teams. They can see their work without being distracted by things they are not responsible for getting done. And - having separate boards also ensures that the out of the box reports (cumulative flow, velocity, sprint reports, burndown charts, etc) show you metrics specifically for your team. Which means you can detect bottlenecks in your team's daily operations much easier.
Having separate boards for your teams does not mean you have to put the issues in separate projects as well. Each board is populated with issues from a board filter (JQL), so you as long as you assign tickets to your teams, filters can cherrypick the right issues for them as you need:
Project = YourProject AND Team = "Team A"
Project = YourProject AND Team = "Team B"
Project = YourOtherProject AND Team = "Team B"
In this example, I have theoretically some issues for Team A in YourProject. Team B has other issues is YourProject as well and additionally some issues in YourOtherProject as well. The board filters for team A and B would look like this:
Team = "Team A"
Team = "Team B"
It is a good thing to see your boards and projects as different things. Where you organise your boards from the perspective of your teams, rather look at the projects from the type of issues you plan to put in them. Are you working on an application or a product? Great! Set up a project for that product or application and another project for another product or application. That way, all work for a single application ends up in 1 central place.
Hope this is some food for thought :-)
Given an ART has multiple Product Teams, what are the advantages/disadvantages to using
1. one Jira Project for each ART Product Team
2. one Jira Project for all ART Product Teams, with one board dedicated to each Product Team
Additionally, which method works best with Jira Advanced Roadmaps?
I also having similar problem .... In my project I have 5 teams delivering a shared outcome and each one having a requirement of using a their own custom workflow for stories.
One chain of thought is to create multiple projects - one Jira project for each team - this gives them flexibility to manage their own workflows
other is to create just one Jira project for all the teams - which will enforce each one of them to use one type of story workflow
For Advanced Roadmaps, from what I have seen, we can pull together the issues form different boards / projects ... so assembling that view in advanced roadmaps will be agnostic to where we are pulling the info from.
I am wondering, will it be a problem If I am trying to save/commit the plan to jira ? will Advanced Roadmap be able to commit changes to multiple projects ?
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