single or multiple projects?

My department has 6 Agile teams with nearly 100 users working on different projects. There are 6 scrum masters, each per team. We have a requirement that the VP should be able to view all teams' activities from a single report. In this case, will this be better to keep all teams under one JIRA project and then create separate scrumboard for each team within the same project? or will it be better to create separate projects, one for each team?

1 answer

1 accepted

Keep the projects separate. You can always create JIRA Boards (kanban/agile) and/or reports showing multiple projects.

Thank you. Can you please tell me the pros and cons of single project vs multiple projects in my scenario?

You can always take advantage of the per project features like Components, Versions, Separate permission schemes (which can be further refined in the Roles), Security, Notifications. That's what I can think for now. 

If projects are separate, how do I view the status of the first sprint (called Sprint 1 say) across all projects?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

23,160 views 2 7
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you