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.
Hi @Matt Allen
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
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)
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
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
Hope this helps! Happy to answer any other questions
Cheers,
Jet
Hi @Matt Allen : what @Jet shared above 👆
Also, you'll find some answers for this in the Jira Product Discovery handbook, in particular the Prioritization and Roadmapping sections.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.