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
I'm currently dealing with a scenario where multiple architectures exist and interact within the same ecosystem, each with their own lifecycle and roadmap.
Across these architectures, business projects live that can affect those architectures.
Project teams would be composed of experts in each architecture based on the projected impact on said system.
Basically, it would look a bit like this:
|Arch 1||Arch 2||Arch 3||Arch N|
Should we go with a JIRA project for each architecture, and a scrum board for each business Project?
How would this work best? What are the caveats, traps, limitations of a setup like this?