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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Are these two similar scenarios same from an Agile management perspective?
Scenario 1: For a new product, enabling Jira Align for everything above the pod level (only the Team/Pod level uses Jira), while other levels (Product, Portfolio, and Enterprise) use Jira Align;
Different teams would be onboarded to each of these versions of Jira
Scenario 2: A fresh instance when we use Jira and Jira Align, integrated with each other, from scratch across the enterprise
@Rishabh Kochhar I'm not exactly sure if I fully understand your question but I'll try to answer.
Scenario 1: If a new product means new teams aligned under a single program/ART, then yes. Teams would reside in Jira and POs or PMs and higher (strategy) would reside in Jira Align.
Scenario 2: Be careful as we don't want to create a new Jira instance for every new product or sets of teams. This is where, if you are flowing work to the teams, aka a new product which relates to stories, features, epics to develop, then you may not want to necessarily go and create a new Jira instance (more API integration calls).
Refer to this page for some additional Jira/Jira Align integration details. https://community.atlassian.com/t5/Jira-Align-articles/Jira-Align-and-Jira-Integration-Best-Practices-and-FAQ-Table-of/ba-p/1253497
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.