Best Practice for Several team and several Project

[Tomas Gustavsson]

Dear all Jira colleagues.

I'm sitting in a big Jira instance that have been built up for a couple of years before i started my work. 

In one part of this setup we have 10 teams and there work are split up in 10 different project each and these project are using one and the same workflow but differs in permission scheme.

This setup is working, but i wonder what could i gain with consolidating these projects into one or maybe two project, on obvious thing would be user administration and such.

Will i gain anything more trying to consolidate, and do you think it would it be worth effort.

[Tarun Sapra · Accepted solution]

Hello @Tomas Gustavsson

I am personally not a big fan of the concept of "1 project per team", because lot of times the teams don't have large number of issues in their respective projects and having more projects not only is an administration issue but also creates impediments when creating reports using advance JQL functions coming from various plugins.

The approach I follow and which works pretty well with the KPIs is that you have a component per team or a custom field called "Team" with a list of teams. So whenever you create a new issue you select the team and the issue automatically appears int he Scrum/Kanban board of that team. In this way within the same project multiple teams can work together and thus we have less admin overhead and most importantly it's easier to get insights into the progress of each team and their deliverables. 

[Hector · Accepted solution]

Hi @Tomas Gustavsson,

I would suggest having the final decision driven by the framework those 10 teams use to work/deliver, so understanding the way of working. Identifying how they measure their progress (KPIs, reporting, velocity, etc)

Jira is quite flexible, so one or multiple projects is feasible technically speaking but key points to understand before deciding the solution are:

1. Software development framework (scrum, kanban, waterfall, etc) or Operations, Support, etc
2. Reporting, KPIs

Regards,