Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Best set-up advice for single scrum team with multiple products through multiple projects

Francis Peixoto
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 15, 2018

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 1Arch 2Arch 3Arch N
Project 1X X 
Project 2XXXX
Project 3 X  
Project N  XX

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?



Log in or Sign up to comment