Using JPD for Products with multiple versions

Kevin Sauer

Hey Everyone!

Our organization is just starting to use JPD in small doses and so far we, and our stakeholders, are finding it very beneficial. One topic that has come up recently as we are starting to input ideas is how should we represent projects that will have several iterations/versions on the board. As of right now, we are putting the high-level idea as the line item on the JPD board and then tagging the Epics representing the different versions on the Ideas Delivery tab. The issue here though is if you have something that will have many versions to be completed, the idea could sit on there for an extremely long time and seem like no progress is being made.

How do you all represent Ideas that will require multiple versions to be fully complete on JPD? 

Tanguy Crusson

Hi Kevin, 

Today we use JPD ourselves (in the team creating JPD) in both ways: sometimes ideas that encapsulate the entire effort are on views, sometimes we split ideas in multiple ones (and link them together) when it makes sense from a product perspective. 

On that topic, there is this question in the FAQ that may be relevant - that shows how you could show high level items on a view, and sub-items in other views:

How can we create a roadmap at 2 levels? (one with a list of themes, one for each theme?) - sort of like a hierarchy

During this webinar we've demonstrated how the JPD team uses a roadmap at 2 levels: one for the overall team, with broad themes, and one for each squad, with more details about each theme. Here's how to replicate this:

Demo: a roadmap with 2 levels

Here's a follow-up to this video, showing how you can show the list of ideas for each boulder when you open the boulder: 

Demo: Show the list of ideas when opening a boulder.