Product and Engineering Ideas/Roadmap in JPD
Asked by Matt Allen:

Myself (being the Product guy) and our Engineering lead want to have a more collaborative approach to roadmapping, primarily to get better insight into each other's work, conflicting priorities and dependencies.

For info, there are two product portfolio's to handle, within each portfolio are around 3-4 individual products.

Any thoughts/suggestions on how others use JPD between engineering, product and across many multiple products?

Our thinking is one single JPD project, then split into different sections by product/team.


Answers:
author: Jet
body: Hi [@Matt Allen](/t5/user/viewprofilepage/user-id/5273145)

You could use a single JPD project that has multiple sections and views by product/team/craft.

This is also how we set it up for our Atlassian Growth team that works on multiple products.

**1. Create a section for each product**

**![Screenshot 2024-09-16 at 11.40.06?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347497i277C54047A7CA247/image-size/large?v=v2&px=999 "Screenshot 2024-09-16 at 11.40.06?AM.png")**

**2. Create views within each section**

For example, as a PM I want to create a high level (now, next, later) roadmap that I can share with my stakeholders. To do that I *create a new board*grouped by now, next later (and add a label to the ideas to filter by now/next/later)

![Screenshot 2024-09-16 at 11.39.09?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347500i91DAA43F11F044A5/image-size/large?v=v2&px=999 "Screenshot 2024-09-16 at 11.39.09?AM.png")

You Engineering counterpart probably wants to see the roadmap on a timeline, so you could create a a timeline view for that within each section

![Screenshot 2024-09-16 at 11.49.10?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347502iC697C4B2AA2929AC/image-size/large?v=v2&px=999 "Screenshot 2024-09-16 at 11.49.10?AM.png")

**3. Create an ideas backlog filtered by team to collaborate on prioritisation**

I recommend creating an ideas backlog for each product, organised by feature/focus area, which allows you to prioritise your roadmap as a team (together with engineering)

Here's an example of what that could look like

* Create themed list view that shows ideas with prioritisation criteria/scoring. You can drag ideas around to list them in order of priority.

![Screenshot 2024-09-16 at 11.56.53?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347504i4638EE081D1BA36D/image-size/large?v=v2&px=999 "Screenshot 2024-09-16 at 11.56.53?AM.png")

* Once you have done the high level prioritisation with you eng/design counterparts, you can create a board view like this that's easier to read and allows you to easily see the top priorities and re-prioritise if needed. Again, you could do this for all your products/features.

![Screenshot 2024-09-16 at 11.53.08?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347503iDEC11D1C8CAD7900/image-size/large?v=v2&px=999 "Screenshot 2024-09-16 at 11.53.08?AM.png")

Hope this helps! Happy to answer any other questions

Cheers,

Jet

comments: author: Tanguy Crusson
body: Hi [@Matt Allen](/t5/user/viewprofilepage/user-id/5273145) : what [@Jet](/t5/user/viewprofilepage/user-id/397079) shared above ?

Also, you'll find some answers for this in the Jira Product Discovery handbook, in particular the [Prioritization](https://pm-dev.atlassian.net/wiki/external/ZWFjOTNkMThiZTY1NGY2MmFlODQ0MTAyNDM5MmE4YTg) and [Roadmapping](https://pm-dev.atlassian.net/wiki/external/OGY3MmI5ZTFhYWEwNDk4NjhhZTM3YzkwMTUyMjMwYzk) sections.


Tags: cloud

jira

jira-cloud