Many respondents stated that a legend is another component that may help a user navigate through the roadmap. One of the most common roadmap formats is a visual that resembles a Gantt chart, which breaks up into the list of components on the left side, and the timeline on the right. When it comes to a roadmap, the general expectations from the data format include the following: Some specialists use Portfolio by Atlassian, Visio diagram, Excel, Aha tool, SharpCloud, or the in-built product roadmap functionality in the next-gen Jira. One may create a product roadmap in the form of a presentation in PowerPoint, Google Slides, or other similar tools.
Having a responsible person mentioned next to the epic allows company leaders and personnel specialists to see who is managing it. The view can include a separate list of epics that haven’t been planned yet for PMs to keep an eye on. So, the product roadmap is built of epics, which may include multiple stories/tasks documented as Jira issues, and which are accessible from the general hierarchy.Įach roadmap’s information block can be populated by additional details as well. Others review and prioritize the topics related to the product and, based on these conversations, add corresponding epics to Jira. In this case, it is always beneficial to have an opportunity to map epics to those high-level items. Therefore, some users may build a product roadmap focusing on broad topics only. The scope correlates directly with the level of detail a roadmap includes. However, some organizations prefer to delve deeper and build roadmaps on the story or task level. Its main goal is to communicate the product strategy to different stakeholders, keeping the team synchronized in that direction, and explain the next steps. Usually, it is compiled for a period from 12 months to 5 years. Generally, a roadmap represents a high-level vision for the product or service. What do users expect from a product roadmap?īelow I’ve split all the answers into categories to make it easier for you to read: Let’s start by reviewing what Jira users mentioned as crucial for a working roadmap, and then move on to the ‘how-to’ part, where I will share a step-by-step guide and a ready-made Google Sheets product roadmap template that you can apply for your project. So, by applying some spreadsheet magic even the most demanding user can adjust it to their needs. One of the core reasons is that at my company we use Google Sheets, an extremely flexible system, to document the roadmap. However, after summing up the voiced requirements, I realized that our approach to creating a roadmap can benefit a large part of the Atlassian Community.
In the end, this research confirmed that there is indeed no one-size-fits-all solution. It came as no surprise that all of them expressed different views on what the roadmap actually is, what form it should have, what information it should contain, who it should be shared with, etc. When working on this post, I reviewed the Atlassian Marketplace for numerous product roadmap-related discussions.
0 kommentar(er)
