Difference between revisions of "Roadmap"
| Line 5: | Line 5: | ||
*It is not a project management tracker: Many managers confuse roadmaps with the documents or software applications used to compile all of the details to complete the initiative — the individual assignments, the personnel responsible for each task, meetings scheduled to discuss specific issues or milestones, deadlines for completing each element of the project, etc. These details should be tracked and updated throughout any strategic undertaking. But the tool for this will be a project management tracker, such as Trello, PivotalTracker or JIRA. | *It is not a project management tracker: Many managers confuse roadmaps with the documents or software applications used to compile all of the details to complete the initiative — the individual assignments, the personnel responsible for each task, meetings scheduled to discuss specific issues or milestones, deadlines for completing each element of the project, etc. These details should be tracked and updated throughout any strategic undertaking. But the tool for this will be a project management tracker, such as Trello, PivotalTracker or JIRA. | ||
*It is not a list of features: Finally, many product managers mistakenly assume their planned list of features or epics constitutes the roadmap itself. But this is not the case..<ref>What a Roadmap is Not [https://www.productplan.com/roadmap-basics/ Roadmap Basics]</ref> | *It is not a list of features: Finally, many product managers mistakenly assume their planned list of features or epics constitutes the roadmap itself. But this is not the case..<ref>What a Roadmap is Not [https://www.productplan.com/roadmap-basics/ Roadmap Basics]</ref> | ||
| + | |||
| + | |||
| + | == See Also == | ||
| + | [[IT Roadmap]]<br /> | ||
| + | [[Business_IT_Alignment|Business IT Alignment]]<br /> | ||
| + | [[IT_Strategy_(Information_Technology_Strategy)|IT Strategy]]<br /> | ||
| + | [[Business Strategy]]<br /> | ||
| + | [[Corporate Strategy]]<br /> | ||
| + | [[Strategic Planning]]<br /> | ||
| + | [[Strategic Planning Cycle]]<ref> | ||
| + | [[Strategic Management]]<br /> | ||
| + | [[Project_Portfolio_Management_(PPM)|Project Portfolio Management]]<br /> | ||
| + | [[Kano Model]] | ||
| + | |||
| + | |||
| + | == References == | ||
| + | <references/> | ||
Revision as of 16:51, 7 October 2019
A roadmap is a strategic plan that defines a goal or desired outcome and includes the major steps or milestones needed to reach it. It also serves as a communication tool, a high-level document that helps articulate strategic thinking—the why—behind both the goal and the plan for getting there. When it comes to understanding the role of the roadmap, perhaps the most important concept to remember is that it is a strategic document, not a document that captures all of a plan’s details. With this in mind, it is also worth reviewing what it is not.[1]
What a Roadmap Is Not
- It is not a backlog: This is another very specific type of document. A backlog is essentially a to-do list of the tasks required to complete a strategic initiative, ideally arranged according to priority. Roadmap planning is often the process of creating a high-level strategy out of a collection of backlog tasks and ideas. A roadmap, therefore, can and should work together with a backlog in the sense that the person responsible for the roadmap (typically a product manager in the case of a product roadmap) will translate its high-level strategic components into tasks that can be assigned and tracked throughout the project. Which leads to a related item that roadmaps are often confused with....
- It is not a project management tracker: Many managers confuse roadmaps with the documents or software applications used to compile all of the details to complete the initiative — the individual assignments, the personnel responsible for each task, meetings scheduled to discuss specific issues or milestones, deadlines for completing each element of the project, etc. These details should be tracked and updated throughout any strategic undertaking. But the tool for this will be a project management tracker, such as Trello, PivotalTracker or JIRA.
- It is not a list of features: Finally, many product managers mistakenly assume their planned list of features or epics constitutes the roadmap itself. But this is not the case..[2]
See Also
IT Roadmap
Business IT Alignment
IT Strategy
Business Strategy
Corporate Strategy
Strategic Planning
Strategic Planning Cycle<ref>
Strategic Management
Project Portfolio Management
Kano Model
References
- ↑ Defining a Roadmap? ProductPlan
- ↑ What a Roadmap is Not Roadmap Basics