Suggestions for naming Jira Product Discovery projects?

[David Nadri]

Curious to hear the JPD Community's suggestions on naming Jira Product Discovery projects.

For example, let's say you organize your JPD projects around your company's products, how do you name them to keep them distinct from regular Jira projects?

Example:

• Product: "MyApp"
• Jira project: "MyApp"
• JPD project: ?
  • "MyApp Discovery"
  • "MyApp Ideas"
  • "MyApp Roadmap"

[James O_Connor · Accepted solution]

I think it depends on the general terminology that you're using in your product management workflow.

For us, the 'Discovery' descriptor works perfectly for JPD projects as that is what we use to refer to our idea/feature-gathering stage across teams anyway. We've only just started using JPD fairly recently and have a well-established Jira project for our main product, so our Jira project already follows the "MyApp" format. Adding a "MyApp Discovery" alongside that just makes sense to the product teams.

'Roadmap' tends to lean a little more towards the delivery side and suggests that things in that project would definitely be delivered, whereas 'Discovery' suggests a more exploratory approach where items may be delivered or abandoned.

[David Nadri]

@James O_Connor - I also think the "MyApp Discovery" format makes the most sense. Thanks for your feedback James! 

What about the project issue key?

Let's say you have:

• Jira: "MyApp" (key: 'MyApp')

• JPD: "MyApp Discovery" (key: '?')

[James O_Connor]

Honestly, we haven't really set a standard for Discovery issue keys yet - in general for our regular Jira projects our keys tend to be 2-3 characters, so in the MyApp example our main project would probably be APP and so far the Discovery projects have just had a 'D' tagged on the end, so the related Discovery project would be APPD

[Gary Spross]

In my experience so far, it's been the best to just add "Discovery" on the end of any JPD project. Similarly, I'll just add a "D" to the end of the project key. In most cases for us there is an associated Jira project that aligns with the project naming convention.

Sounds like I do it the same way you've indicated you're doing it so far!

[David Nadri]

@Gary Spross - thanks! Appreciate your input.