You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We often get questions about the relationship between between Jira Product Discovery and Jira Software and Advanced Roadmaps. I'll try to clarify a few things here.
First, here's a high level view of how we see things:
Jira Product Discovery is here to help you with Discovery
Jira Software is the market leader for Delivery
Discovery and delivery work hand in hand. There are some things that are clearly in the realm of discovery (e.g. assessing potential solutions for opportunities based on insights), others that are clearly in the realm of delivery (e.g. running sprints), and things that are in the overlap between the two (e.g. technical spikes, deciding how to prioritize technical debt vs new features)
In this first version of Jira Product Discovery we have focused on the core discovery jobs, and spent a limited amount of effort looking into the areas of overlap with delivery - which is where you see the “delivery progress” field for example. It’s an area we plan to unpack a lot more as the tool matures.
We are creating Jira Product Discovery so you can collect all the ideas/problems/opportunity/solutions you have, many of them you will never do anything about, and decide which ones you prioritize and why - that’s where you hold these conversations with your teams and stakeholders across the company and with customers and end users. You validate these decisions continuously by talking to end users and capturing all of this, and reassessing continuously what is going to have the biggest impact to the goals you’re after, based on learnings. The outcome of all this is a product roadmap showing high integrity commitments, that you can easily share with everyone.
When it comes to delivering these commitments, you can use to Jira Software. You have corresponding epic(s)/initiative(s) for each idea, you can break them down in smaller chunks, and try to map out how all the things will fit together, focusing on dependencies, team constraints, more detailed planning if the sequencing is tricky, etc. This is what Advanced Roadmap is here to help you with.
It is still early days, Jira Product Discovery is in beta and we see the current experience as “version 1”. There are many opportunities for how Jira Product Discovery and Jira Software can better work together to help you build better products, and we are exploring many concepts for that… Because we know there is so much we can do by having discovery and delivery in the same app! Down the line you can expect the line to become more blurry between these two experiences. In the meantime, here’s a simple way to think about things:
If you are creating a product roadmap that you want to share with your CPO, CEO, business teams, support, sales, customer success: use Jira Product Discovery, and create views that explain the “why”
If you are creating a delivery plan that explains how you plan to sequence the work taking into account all constraints, in discussions with the people who care about the details for the “how” (e.g. engineering leadership): use Jira Software and Advanced Roadmaps.
Note: here's a great blog that was a source of inspiration for how to innovate from within Jira when creating Jira Product Discovery - we're still very much in the "iterate" phase.
Product @ Atlassian
101 accepted answers