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 dependencies in Compass are not the same that we track in Jira Align. In Jira Align we are identifying and capturing dependencies between teams and programs with the Feature and Epics that we are planning and executing on as part of PI Planning.
Compass will compliment the technical work between teams that are part of a Program/ART that is practicing agile at scale.
Hopefully in the near future we'll have articles and more details on how Compass and other Point A products are used in addressing Atlassian solutions.
To add to @Tom O_Connor 's point, it's best to think to of Jira Align as a way to track and make decisions about software development that is planned or in progress. Compass is a way to keep track of all system components that make up a modern microservice-based system architectures.
It will make sense for an enterprise to use both tools, though they're typically used by different roles or personas, and they support different jobs to be done.