nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

One view for Product Discovery and a Software Project

Ashleigh Hamilton_nslhma

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?

Accepted answers

All comments

Joey_x4f3b3

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:

CleanShot 2024-12-03 at 11.44.28@2x.png

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

I hope this helps!

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.

Amina Bouabdallah

Hi there! thanks for reaching out.

What do you think of

having a dedicated JPD project to receive all incoming tickets
creating an epic for a corresponding idea that engineering works on
marking the epics coming from idea intake with a specific label
showing in a Jira Board all epics with the specific label?
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_nslhma

I agree with all your points.

Ashleigh Hamilton_nslhma

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

Steven Purcell_xw69h4

This is adding complexity to something that does not need complexity. We are in the trial right now and it seems completely unnecessary to create an entire new project just to gather feedback on an already established software project. Just let me do product discovery on my software projects.

Ashleigh Hamilton_nslhma

I dont understand your point. My question has nothing to do with feedback. It was about ideas versus delivery tickets and how best to allow my engineers to work from one place.

I ultimately resolved this issue by creating a substatus in the JPD project and then leveraging automation to synchronize the substatus of the JPD idea with the delivery ticket statuses once it was created.

This allows my engineers to work out of the JPD project while still tracking the delivery ticket for execution.

It also allows the Field Team to have visibility into their request from one place.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

best-practice

jpd