Product of Products approaches?

[George Moberly]

We are evaluating JPD now. Our Jira dev projects are broken into a project per product (roughly) - and we thought to have a JPD project her dev project for symmetry.

Question is, if Ideas span multiple products (probably in our case maybe 20% would) does it make sense to have a separate project for "Initiatives"? What are best practices for having a layer "above" product ideas?

[Tanguy Crusson · Accepted solution]

Hi George, you have 2 ways to think about it: 

1. You could create a single JPD project for all products, and create different sections with views for different teams and products. That way an idea can appear in different products and teams views. We have customers who have 250 people working in the same project. If it's set up well and people understand how to participate in the project, it can work pretty well. 
2. You could create different projects, but then it isn't possible to have an idea belong to different projects. However, you could indeed create a separate project for your initiative-level ideas and link these to ideas in each team's project. You just wouldn't be able to visualize these relationships in views (initiative - team idea). That being said, we're currently working on features that will eventually make that easier. 

[Denis Paul]

@georg I like to use Plans (Ex Advanced Roadmaps) for cross team planning. You could use the new integration with JPD if you have that included in your Jira license: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Early-Access-Program-new-integration-with-Jira-Plans-ex-Advanced/ba-p/2743110