How to use JPD for 20 PMs/Squads?

unknown

My product org is looking for a new centralised roadmapping tool. We have 20 squads and need a tool to help us manage and share our roadmap with non-product stakeholders (sales, marketing, executives).

I'm looking into Jira Align (JA) and Jira Product Discovery (JPD).

JA seems good for enterprise level delivery management, but the views look clunky, and I'm not sure how easy it is to share with external stakeholders.

JPD looks very neat and I'm familiar with this kind of tool as I used to use Product Board. I like that we can add insights and external stakeholders can add comments. However, we have 20 squads in our product department, so I'm not sure how to set-up the product org.

• Should we create one JPD project for the whole org? If so, can we assign owners to the projects so PMs can filter on their work only, and avoid a cluttered view? 
• Can we create multiple JPD projects? And then merge them into one view so our Head of Product can share the roadmap with external stakeholders?

Tanguy Crusson

Hi, you can do both. 

• Everyone in the same project is the only option that lets you have a cross-product view of the roadmap (views today can only include ideas from one project)
• Having different projects is the easiest way to make sure each team can configure things however they like

There are teams using both methods today. We've seen projects with 100+ people collaborating.

 

From the FAQ:

We have multiple products and teams. Should we use one project or multiple? 

This depends on many factors. Jira Product Discovery was designed to work best when used by individual teams using the Spotify squad model. But it's possible to use a single project to share between teams/products, especially when there's a high level of collaboration required between these teams. 

Demo: using a single project for multiple products and teams