You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
"Advanced Roadmaps for Jira (ARJ)" is primarily offered as a tool to plan and track work across multiple teams / projects. It can 'pull' and 'show' data from different sources: Projects, Boards, and Filters. In most cases, ARJ deals with existing Backlog Items residing in different Projects. [source: Advanced Roadmaps Guide | Jira Software | Atlassian ]
Creating and Managing Themes and Features (higher level Backlog items) - Which is a better Practice ?
Option A: Identifying and Adding New Higher Level Backlog Items - [like Themes and Features] in the ARJ first - before they are created in individual Team's Jira projects. Each Team picks up one or more Features from ARJ and add more details in their Project level / Team level plans [like adding Jira Epics and Stories]
Option B: All Backlog items at all levels are first created in individual Projects and 'pull' them 'together' to create a Plan in ARJ.
Please share your thoughts.
Hi @Vijay Reddy ,
When working at scale like this, it's usually better to have a single Jira project as a workspace for all of the related teams, where each team gets their own individual backlog. Through this configuration, it's much easier for all teams to check the Product/Master backlog to see these Themes/Features and to add and assign their high-level work items underneath them.
If this is not an option and you plan to stay with each team using their own Jira project, it would probably make the most sense to create these "collaborative" issues (Themes/Features) in Advanced Roadmaps so that it can be seen as a source of truth. The challenge with this is that once it is time to commit an issue back to Jira, it will need to live inside a specific team project.
If Themes/Features are not collaborated across teams, then I would go with Option B. Create issues for your teams in their own workspaces and use an AR plan to see the holistic view.
Thank you so much for very helpful response!
Just to confirm my understanding.....:
Option A: Maintain ONE Jira Project [Master Project] for all teams; Create a Plan in Advanced Roadmaps for Jira (ARJ) based on just one Master Project with the desired Hierarchy levels. Always create new Issues [at any level] on Jira Master Project only; use ARJ for high level planning and Roadmapping, what-if scenarios, etc. This Option is VERY CLEAR.
Option B: Maintain Collaborative Issues in ARJ while keeping Team-specific Issues in individual Team's Jira Projects.
This brings up another question about representing work items in Jira / ARJ that need collaborating with other teams in general:
Scenario 1: Each Team plans and delivers their own items using Jira Projects. They don't have any dependencies; they can plan and deliver independently. The ARJ provides 'visibility' into the work all the Teams in a single place for Managers and others. If the work of these teams contribute to achievement of higher level items (like Features, Themes, Initiatives, etc.)
Scenario 2: Each Team has their own Backlog and the associated Project. Additionally, Each Team has a need to collaborate with 5 other Teams.
For example, Team A (a Platform Development Team) builds their Product [which is the Platform itself] that is used by other Teams to build their products. [Teams 1 - 5].
Sorry for the long message :)
Any help / guidance is greatly appreciated!!!