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
About 10 teams are working together (loosely coupled; not part of the ‘same’ product).
Team A builds platform products/ components used by other 9 teams in building their own products.
All Team leads (Scrum Masters and Product Owners) meet once in 2 weeks to review “Dependencies” among the 10 teams.
Dependencies conversations generally go like this:
1. Team A announces that they will be releasing a new version of one or more of their products.
2. Other Teams who use Team A’s products need to “prepare” for this upcoming change. So, they will add a backlog item in their own Project /Team’s backlog to plan and execute the work needed to accommodate new versions of Team A products in their own Product offerings (it is something similar to getting ready to accommodate a new version of a major tool, OS upgrade, etc.)
3. Then the conversation switches to what the ‘other’ Teams want from Team A. These can be considered as Requests for new Features or Feature updates of Team A’s products. These items will be added to the Backlog of Team A.
4. Manager of Team A wants to build a Jira Plan (ARJ) that shows only the backlog items of all the teams that are “specifically” related to Team A:
4.1: Backlog items added to each team’s backlog to accommodate changes / new features coming from Team A
4.2: Backlog items added to Team A’s backlog to accommodate the Requests from each team.
in the “Integrated Plan” being built for Team A’s manager, they only want to see these two types of backlog items:
A. the Epics and Stories of other teams related to Team A (the ones discussed during the meetings; typically the work they need to do to accommodate Team A’s upcoming changes)
B. The Epics and Stories of Team A related to other Teams as discussed in the meeting (typically requests for new features or feature updates)
They don’t want to see any other Epics or Stories that are outside of above two categories.
Here is the Question please:
Q1: what is the best way to build Jira Plan (ARJ) to accomplish this goal?
a. Let each Team create a dedicated Epic in their backlog exclusively to manage the work related to Team A. Create a Filter just for this and use the filters as the Issue Sources in the Jira Plan
b. Let Team A create dedicated Epic(s) in their backlog exclusively to mange the work related to Requests of Other Teams. And use these filters as issue sources
Q2: Has anyone addressed this type of “cross team coordination” needs with JRA? If so, would you please share?
Thanks a lot in advance !