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.
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).
This template was created by Aleksei Soskov.
Get started with this template right now.
Empathy Map for Educational Purposes
Works best for:
Product Management
Enhance your educational approach with the Empathy Map for Educational Purposes template. This tool helps educators understand students' perspectives, needs, and emotions. Use it to create a more empathetic and effective teaching strategy, ensuring that your educational content resonates with and supports your students. Ideal for teachers and educational planners aiming to improve student engagement and learning outcomes.
Sprint Planning Template
Works best for:
Agile, Sprint Planning
The Sprint Planning Template is a useful tool for agile teams to organize and conduct sprint planning sessions. It enhances team collaboration and communication by providing a clear visual layout of sprint goals, tasks, and timelines. The interactive design ensures team alignment toward sprint objectives, leading to effective teamwork. The template is a central hub for planning, discussion, and decision-making, creating a collaborative and productive environment.
Product Roadmap by Petra Ivanigova
Works best for:
Product Management, Roadmap
Plan your product journey with the Product Roadmap by Petra Ivanigova. This template helps you outline key milestones, set priorities, and visualize your development path. Use it to align your team, ensure everyone is focused on the same goals, and keep stakeholders informed. Ideal for product managers and teams looking to streamline their planning process and achieve strategic objectives efficiently.
Prune the Product Tree Template
Works best for:
Design, Desk Research, Product Management
Prune the Product Tree (also known as the product tree game or the product tree prioritization framework) is a visual tool that helps product managers organize and prioritize product feature requests. The tree represents a product roadmap and helps your team think about how to grow and shape your product or service by gamifying feedback-gathering from customers and stakeholders. A typical product tree has four symbolic features: the trunk, which represents the existing product features your team is building; the branches, each of which represents a product or system function; roots, which are technical requirements or infrastructure; and leaves, which are new ideas for product features.
Product Roadmap (Now, Next, Later, Trash)
Works best for:
Planning, Mapping
The Product Roadmap (Now, Next, Later, Trash) template allows teams to organize their product development initiatives into four distinct categories: current priorities, upcoming features, future plans, and discarded ideas. By visualizing the roadmap in this manner, teams can maintain focus on immediate objectives while keeping an eye on future opportunities and managing stakeholder expectations effectively.
A Halloween Retro
Works best for:
Retrospectives, Meetings, Agile Methodology
The Retrospective Halloween template offers a themed approach to retrospectives, perfect for the spooky season. It provides elements for reflecting on past iterations, identifying scary issues, and brainstorming solutions. This template enables teams to have fun while addressing serious topics, fostering creativity and collaboration. By promoting a playful yet productive atmosphere, the Retrospective Halloween empowers teams to tackle challenges, drive improvement, and strengthen team cohesion effectively.