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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,311 views 14 20
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot