Agile Product Roadmap (Now, Next, Later)
This is a Themes-based Product Roadmap in a modified "Now, Next, Later" form made to assist teams who transform to a Product Operating Model to build Outcomes-based High integrity Product Roadmaps because it is so different from what those teams are used to see and use as Product Roadmaps.
About Agile Product Roadmap (Now, Next, Later) template
This is a Themes-based Product Roadmap in a modified "Now, Next, Later" form made to assist teams who transform to a Product Operating Model to build Outcomes-based High integrity Product Roadmaps because it is so different from what those teams are used to see and use as Product Roadmaps. This Roadmap has prefixes "probably", "maybe" in addition to "Never", "Next", "Later" to emphasize its agility nature: if something is on Agile Roadmap it doesn't mean that it will be eventually delivered to the customers. It's absolutely not!
How to use Agile Product Roadmap
Start with the "Now" section. Add some Themes (hard, real customers/users/company problems that your team is working this quarter/month) sticky notes to a "To Do" section of "Now." Themes must be based on (i.e., exist there because of, prioritized, and split among the existing teams) a Product Strategy created by Product Leaders. "Now, Next, Later" sections represent Product Strategy prioritization. The "Now" section split by Product Teams represents teams topology. Example of Theme: "Signup completion rate is about 20%, which is too low."
Move some of Themes from "Now" to "Next" and "Later" sections to init Product Roadmap prioritization (or simply create new Themes in those sections).
Change Themes in a "To Do" list of "Now" section to OKR's (Objectives & Key Results). Example of OKR: "Increase signup completion rate from 20% to 50%."
Move sticky notes from "To Do" to "Discovery / Delivery" and then to "Delivered" or to "Next" or to "Later" or even to "Never". Working in a Product Operating Model, we do Product Discovery and Product Delivery. It may happen that the team discovers that it is very expensive for a company to solve this problem. And that's why this problem (an OKR) will get to "Never" instead of "Delivered."
Use "Delivered" section to keep sticky notes there when you start a new quarter/month - so you can see what you've recently done. This helps to change and track the course of the Product Strategy.
Keep items in the "Never" section. Once a sticky note gets to a "Never" section we need some document that explains the story behind that sticky note: what was Discovered that lead to a conclusion that our company Product Leaders (along with the Product Teams) decided not to deliver a solution to that problem (at least for now).
Get started with this template right now.
Features Prioritization Tool
Works best for:
Agile
The Features Prioritization Tool offers a systematic approach to prioritizing product features based on criteria such as value, effort, and strategic alignment. It provides a structured framework for capturing, evaluating, and ranking feature ideas, enabling teams to make informed decisions about what to build next. With customizable scoring mechanisms and visual dashboards, this template empowers product teams to optimize their product roadmap and deliver maximum value to customers, driving competitiveness and market success.
Easter Egg Retrospective
Works best for:
Agile Methodology, Retrospectives, Meetings
The Easter Egg Retrospective template offers a themed approach to retrospectives, incorporating elements of the Easter holiday. It provides elements for reflecting on past iterations, hunting for hidden insights, and brainstorming improvements. This template enables teams to have fun while addressing serious topics, fostering creativity and collaboration. By promoting a playful yet productive atmosphere, the Easter Egg Retrospective empowers teams to uncover hidden gems, drive improvement, and strengthen team cohesion effectively.
Salesforce Implementation Plan
Works best for:
Roadmap, Planning, Mapping
The Salesforce Implementation Plan template offers a structured framework for planning and executing Salesforce deployment projects. By outlining key milestones, tasks, and dependencies, teams can ensure a smooth transition to the Salesforce platform. This template facilitates collaboration between IT and business teams, ensuring that implementation efforts are aligned with strategic objectives and deliver value to stakeholders.
Outcome Mapping Template
Works best for:
Diagrams, Mapping, Project Management
Use Miro’s outcome mapping template to improve your operational efficiency. Outcome mapping will help you visualize all the possible strategic outcomes for your upcoming project, allowing you to see into the black box to identify any potential challenges along the way.
Product Launch Lifecycle
Works best for:
Product Management, Planning
The Product Launch Lifecycle template guides product managers through the stages of launching new products. By outlining pre-launch, launch, and post-launch activities, this template ensures comprehensive product launch planning and execution. With sections for defining launch objectives, identifying target audiences, and tracking performance metrics, it facilitates coordinated efforts across marketing, sales, and product teams. This template serves as a roadmap for successful product launches, maximizing market impact and customer adoption.
Agile Board Template
Works best for:
Agile Methodology, Meetings, Agile Workflows
Part of the popular Agile framework, an Agile Board is a visual display that allows you to sync on tasks throughout a production cycle. The Agile Board is typically used in the context of Agile development methods like Kanban and Scrum, but anyone can adopt the tool. Used by software developers and project managers, the Agile Board helps manage workload in a flexible, transparent and iterative way. The Agile template provides an easy way to get started with a premade layout of sticky notes customizable for your tasks and team.