Release Plans cover how problems are to be solved. Roadmaps cover what problems are to be resolved.  

- Project Management plans track more specific, measurable steps to resolve and issue. Roadmaps cover broader, higher level ideas to accomplish a vision

- Product Backlogs are a tier rank priority list of accomplishing tasks that are actionable. Roadmaps inform how priority decisions should be made

- Customer-Journey Maps focus on users’ journey in interacting with a product. Roadmaps communicate future work


Ohio State University, Columbus

Augustana College (IL)

A High Level Map that communicates current, next, and future work for a team to solve a problem or improve/create a product.  It is designed to assist a team’s ability to establish and perform the necessary steps of achieving a particular goal.  It is meant to be a guiding document rather than a strict schedule; a centralized resource that all team members can access.

UX Roadmap: Definition and Components

https://www.nngroup.com/articles/ux-roadmaps/

UX Roadmaps: Definition and Component

- Context
- Themes
- Confidence Estimates
- Disclaimers

Structures and Components of Roadmaps

Roadmaps need to be flexible as objectives and needs change as what they are used for and who uses them can change as a project progresses. These two components can help achieve this:
- Scope
- Lens

Adaptations

- Based on user research: Themes should be thought of as user problems to solve, and specify how future research should be done.

- Contextually Appropriate: Roadmaps should be relevant to the organization's overall strategy and adapted to the needs of the users.

- Collaborative and Living: Components of a roadmap are always liable to change as projects, users, team members, and goals change. So roadmaps should always be adaptive.


Learn Before

Related