How to setup Jira where a project equals a product?

[John Safar]

We are transforming our enterprise into a Product based operating model and we are looking to start a new Jira instance where we base all of our work around a Product and not a team. In our current state, all of our projects equal a team and it is extremely hard to know what team is working towards what product and in some instances we have one team supporting multiple products.  

We want to align our Jira Project to equate to a Product and then have teams work within that product. Can anyone guide me on how to set this up and how to setup the boards where teams can work on their respective products or work in a cross functional model as needed?  Our enterprise is large and this would eventually scale across the entire enterprise. 

[Laurie Sciutti · Accepted solution]

Hello @John Safar and welcome to the Community!  We do this and it works quite well.  Simply set up your projects based on a product with a main board pulling in everything from that project/product.  Teams can then create their own team-based boards that can pull by multiple projects and team.  For instance, a team-based board filter would look something like this:  

project in (AA, BB, CC) AND Team = 111 OR Team = 222 ORDER BY Rank ASC

HTH 

[John Safar]

Thanks for the response @Laurie Sciutti ! How do you organize the team based boards? Do you use a specific attribute as a team? We have over a thousand team, I would be hesitant to use labels, is there another way that can scale? 

[Laurie Sciutti]

Hi @John Safar ~ we use the Team field (from Roadmaps).

[Jamie Stanczyk]

I know this post is a little bit old, but I do have a question based on the answer. We currently have company-managed scrum projects, where each project is a product. 

We also have an additional project set up for each team, that uses a cross-project filter to show all of the products that the teams are working on. That way we can see what work items specific to product for that team. The cross project filter works, but with using sprints, each sprint is separated out on the backlog view and active sprint view. This makes starting and completing each sprint tedious and very manual, along with reporting being difficult within Jira to track team velocity over all products.

Any ideas?