Should I split up a project into multiple projects, based on the applications?

I am preparing to launch two will be a corporate website project and the other will be a data integration project. Both will touch the same applications (Drupal, APIs, etc.). Should I only create one project (and one scrum board) for each, or should I create a project for each application and the 2 scrum boards will share multiple projects?

1 answer

1 accepted

0 votes
Renjith Pillai Community Champion Nov 15, 2013

If you have seperate versions, releases and components to be managed, then make it two projects.

If they follow same, you can keep them in the same project. Regarding boards, it really does not matter, both approaches can be handled by the boards.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

239 views 0 11
Read article

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