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

[Bryan Mack]

I am preparing to launch two projects...one 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?

[Renjith Pillai · Accepted solution]

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.