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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

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

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?

0 comments

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you