What would the best project setup be for multiple tech teams?

[Mike Mixdorf]

Hello,

Our current Jira setup for our digital tech teams separates each team into their own Jira Project. Recently we are beginning to have work projects need to involve several of these teams in order to complete these items (many tickets for a website, a few for DEVOPS, for example).

This current setup does not allow for good cross-project tracking, especially in terms of sprint planning, velocity, releases, etc.

One potential solution was to merge all of these separate tech team Projects into one Project and create separate boards for each team, so each could retain their own sprints, velocity, etc. This would allow more fluidity in tickets/work that may need to be cross-team and would not have the need to be moved to a different Jira Project for another team to pick it up (and potentially not have room to work on it in their current sprint).

What would some best practices be for setting up a Jira workflow when several teams are involved and could potentially need to work on tickets relating to each other (but would most often need to be separate for sprints, velocity, reporting)?

Example: Newsletters - most newsletter work is done by one team, but may need some support from Devops for backend code while also needing work done by our website team to add links to the site redirecting back to the newsletter sign-up page. Currently, these are three separate Jira Projects, one per team.

[Asha Goyal]

Hello Mike, 

Your proposed solution to the problem of cross-team collaboration in Jira is an effective way to manage multiple teams and their work within one project. By creating a Scrum board in company Managed project, you have provided a centralized location for all the teams to track their progress and work together towards the same goal. The creation of a Master Board and different boards for each team in the project, along with the creation of components with the name of each team, ensures that each team has a dedicated space to manage their progress.

By adding filter queries by components and selecting a component for each board in the board settings, you have enabled easy tracking and filtering of work items across the different teams. Configuring each issue to have a component dropdown menu right below the reporter is a thoughtful addition that makes the experience smoother for all the teams.

Assigning each issue a component label allows for easy tracking of progress and ensures that each issue is associated with the correct team. 

By starting each team's sprint separately, you have ensured that sprints are visible separately on each team board, and one master sprint on the main board. This provides the flexibility to manage each team's work while still allowing for the project's overall progress to be tracked and managed. Overall, this is an excellent solution to the problem of cross-team collaboration in Jira, and it should help to improve efficiency and productivity in the project.

Another option would be to use Advanced Roadmaps, which can be a great asset in managing cross-team projects.

https://community.atlassian.com/t5/Jira-Software-questions/Team-crossover-on-Projects-and-how-to-handle-it/qaq-p/1645900

https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-roadmaps/

Finally, an additional option could be to have one master project and use automation or a third-party plugin to create subtasks based on the team's requirements. This approach would allow each team to have its dedicated workflow and tasks.

Thanks