Multiple projects for one team-need one backlog

[Zara]

I am trying to set-up Jira for company. We have about 20 teams. We have grouped these teams into "Areas". Each "area" will be a Project in Jira. However, I have services teams that support multiple areas. They will now need to maintain multiple backlogs.

How can I effectively manage this?

Should i just create one big project with those 20 teams and create Quick filters?I do not want these services teams to maintain multiple backlogs in the different projects.

Or keep Areas as separate Projects and then have the Services teams create Boards for multiple projects?

[Jack Brickey]

It is hard to say exactly  how I would set things up based upon the info you have provided. However, I would think separate projects if the teams want to work independently of each other. However, if they are all working on a single ‘product’ then one or a few project would work using Components to define the areas.

now regardless of the number of projects you can simply create different boards for each team/area. This allow the teams to work independently.

[Zara]

Thanks for the response Jack!

Basically  they are their “own” products- each have their own product owner. 

Can I create scrum and Kanban boards for multiple projects? This way my services team (who work across all the products) can have their own backlog? I would assume that I would need to create the same Component across all the products (projects in jira) and then create a board on the Projects and that Component?

just trying to solve this for the services team who work across all the Projects.

[Zara]

Here is my situation- make it more clear :) @Jack Brickey

Team A, Team B, Team C, Team D,Team E

 Consolidated by Product area

Team A and Team B= Product 1

Team C, D, E= Product 2

In Jira, I will create 2 Jira Projects: Product 1 and Product 2

Now I have Team Z, that team's work is shared between Team A-E.

If I give them both the Projects (Product 1 and Product 2), they will now have multiple backlogs.

So how can I solve Team Z's issue- where they will see only their own backlog ?

Option 1: I can create the Component "Team Z" for all Teams (Team A-E).

Then create a Scrum Board and Kanban board with both Product 1 and Product 2 projects for Team Z.  Team Z then can add Component filter ("Team Z") on their board and only see what was filtered to them. 

Option 2: Create one project for all Teams (A-E, Z) but is that the best way for 25+ teams?

[Jack Brickey]

I can’t say what is best. My opinion would depend on really understanding your environment, team, culture, processes. However, generally I stick with a single project if the issuetypes, workflows, permissions, screen schemes etc. are the same. Otherwise I split the project. Now with that said, if these are truly different “products” with independent release cycles and teams I would have a project for each. To me, at least for SW development Jira’s Projects have a 1:1 relationship with my “products”.

[Zara]

@Jack Brickey

If I have 25+  teams under One project- would it be difficult to maintain? Would there be any performance issues? 

They all follow the same release cycle. 

I guess I am trying to figure out the best way to approach this (and the less painful way).

[Jack Brickey]

The number is not a concern. It just comes down to the likelyhood that the teams want to configure their workflows differently. You can always move a teams issues to new projects later as long as you have some field you can filter on to distinguish them from the rest.