One view for Product Discovery and a Software Project

[Ashleigh Hamilton]

We just started using Product Discovery to intake customer enhancement requests. As part of this process, a specific engineering team is responsible for scoping out the work and determining the level of effort before it is approved for development. Once approved, they will then begin development work. The problem I am running into is that the engineering team does not want to work out of two different projects.

Current Process: I have to duplicate the discovery ticket and add it as a sub-task to a parent task called 'Triage Tickets" on the Software board. I then have to manage both tickets, which is inefficient and unnecessary. 

I have created a view that shows the delivery tickets associated with the ideas, but this view has been rejected by engineering because I cannot show who is assigned to those delivery tickets. 

Is there a way to create a comprehensive view of a Discovery and a Software Project? 

[Amina Bouabdallah]

Hi there! thanks for reaching out.

What do you think of

1. having a dedicated JPD project to receive all incoming tickets
2. creating an epic for a corresponding idea that engineering works on
3. marking the epics coming from idea intake with a specific label
4. showing in a Jira Board all epics with the specific label?
5. keeping track in JPD of the status of ideas to denote if an idea was selected or discarded + delivery progress for those ideas that were selected for development

?

Hope this helps!

Amina

[Ashleigh Hamilton]

I appreciate the suggestion, but creating the epic still adds the extra step I am trying to remove. 

[Jens Schumacher - Released_so]

Hi @Ashleigh Hamilton 

A couple observations and recommendations. 

Duplicating tickets

Duplicating tickets is rarely a good idea. In this case it allows the engineers to work out of one project, but it creates a lot of overhead for you and others. Is that worth it? Is going accessing a separate project really that much of a burden? 

Estimation

Estimation at this level should be a collaborative process between product management and engineering. Unlike estimation during spring planning, this should be extremely high level. Estimation requires a detailed understanding of not only the idea, but also the potential solution. 

There is no need for detailed estimation until the work actually starts. Even than detailed estimation can be questionable.

[Ashleigh Hamilton]

I agree with all your points.

[Joey - DevSamurai]

Hi @Ashleigh Hamilton , welcome to the community!

To manage multiple projects in one view, I recommend you add them to a program using our app TeamBoard ProScheduler. It allows you to manage unlimited project types. Then, your team can work across projects in one place, and display who is assigned to which project (you can also customize the color scheme by project, assignee, status,... to visualize better). See the example below:

1/

2/

3/

If you are interested in this, please feel free to reach out at https://teamboard.cloud/contact/

I hope this helps!