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
Accepted answer

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 Sign up to answer
Community showcase
Posted Monday in Confluence

Organizing your space just got easier - Page Tree Drag & Drop is here

Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...

60 views 3 2
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