which is good, whether to create multiple project or multiple boards when you have various modules?

[Sathish Kumar]

Hi Guys,

We have a product developed which has various modules integrated to it and we have small scrum teams working on each module. All the module have a Front end, Service/Backend and Testing done parallel.

We have a backlog created for each of these module with the User story, Test acceptance and the DOD. Now we wanted to track these modules and their tracks via JIRA.

Note: These modules have dependencies on each other at many places.

Please advice on the below..

1. Is it good to create separate projects for each module and a respective Scrum board to track on a Sprint basis or to create one project with multiple scrum boards and parallel sprints to each scrum boards ???. Please suggest a best solution for this.

2. We would like to make use of the various charts in JIRA like burndown, velocity charts, etc, if we go for multiple project or single project with multiple scrum boards, will there be a conflict on the sprint burndown and other charts ??

3. There are few user stories (More than 50%) is completed, Is it good to load those in the backlog, if so how do we track them and get it marked as done, because we will be running active sprints for the pending user stories, is it a good practice to include these among those current sprint and get it done or any other practice is suggested from the experts.

4. Now then we have more than 50% of the tasks completed is it good to move those completed tasks under a KANBAN board and make it as done rather bringing them under Scrum board. But if I do so will we be able to use the same backlog and track them effectively ??

Please throw suggestions as much as possible. Each suggestions will be much helpful.

Thanks,

Sathish

[Warren]

Hi Sathish

One product should be one Jira project. Then you can create multiple boards, one for each module. That way each team (board) can have it's own sprints and burndown charts, all pulled from a common backlog.

The way you set it up is to use a "differentiator", often a Jira Component. So all issues relating to module A would have a component Module A etc. Then the board filter can include that module so the board A would only see issues that relate to it.

I'm not sure about closed tasks - maybe someone else has an idea for that

I hope this helps

Warren

[Sathish Kumar]

Got it Warren, Thanks so much, it was really helpful. Appreciate your feedback.