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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
The Jira Align - Jira integration can support many approaches to the way work is structured in Jira. That is fantastic as the structure which is best for a specific organization depends massively on their specific situation. And as that situation might evolve so might the respective recommendation. However, if asked “what the best structure in a greenfield scenario is” - there is a clear preference.
1) From a tooling perspective, this structure moves the program closest together.
All teams will be enabled to gain visibility of work from other teams and collaborate with each other most easily.
2) This structure contributes to minimizing the load on the Jira API.
The amount of integrated projects increases the load on the Jira API. With 1 project per program the amount of integrated projects will be minimized.
3) The user experience in Jira is best when using this structure.
When the data of a program lives in one Jira project, many Jira features work best (non-exhaustive list):
the project or “basic” roadmap captures all the work in the program
Features/Jira-Epics can be decomposed easier into Stories if Stories and other child-work items live in the same project
4) This structure scales well from a support & admin perspective.
The structure does not clutter Jira with projects as other structures might. As Jira reflects the teams and team-of-teams organizational structure, support & admins can connect issues with the data quicker. Permissions management in Jira becomes easier as well - in many enterprises access management is centralised via a webshop and for this structure, users would need to order access to one project to gain access to the entire program in Jira.
5) This structure is easy to understand for the users.
The project the user works in reflects the program the user works in. With one custom field, the data can be sliced so it generates views on the data of the team of the user.
1) The ability to limit access to content within the program to certain members of the program is limited.
While this is not something we would recommend as it impedes collaboration across the program, sometimes restricting access to certain content in the program for certain users is a compliance necessity. An example could be a situation where multiple contractors are contributing work to the program objectives of a single program. Without further apps in Jira, only issue security would be able to fulfill respective requirements (please bear in mind that issue security is not available in Jira Align).
Solutions Architect Jira Align
13 accepted answers