The Hot Air Balloon Retrospective
The Hot Air Balloon is a simple activity for helping the team identify things that makes them move faster, and things that slow them down.
The Hot Air Balloon is a simple activity for helping the team identify things that makes them move faster, and things that slow them down.
The Sunny Skies represent everything coming up that makes us feel good and happy during work.
The Hot Air represents everything helping us to achieve the sprint goal, pushing the team's balloon to go even faster.
The Sandbags represent everything that is slowing us down an holding us back on the journey towards the sprint goal.
The Storm Clouds represent potential risks ahead that could jeopardize future sprint work.
This template was created by Christian Maniyar
Get started with this template right now.
Feature Canvas Template
Works best for:
Design, Desk Research, Product Management
When you’re working on a new feature that solves a problem for your users, it’s easy to dive right in and start looking for solutions. However, it’s important to understand the initial user problem first. Use the Feature Canvas template to do a deep-dive into the user’s problems, the context in which they will use your feature, and the value proposition you will deliver to your users. The template enables you to spend more time exploring the problem to anticipate any potential blind spots before jumping into solutions mode.
Product Ops Canvas
Works best for:
Product Management, Planning
The Product Ops Canvas template helps product managers align product strategies with operational capabilities. By mapping out key operational processes, tools, and metrics, this template fosters alignment between product and operational teams. With sections for identifying bottlenecks and optimizing workflows, it supports continuous improvement in product operations. This template serves as a guide for driving efficiency and scalability in product management processes, enabling teams to deliver high-quality products at scale.
SAFe PI Planning
Works best for:
Agile
SAFe PI Planning is a collaborative event for Agile Release Trains to plan and align on program increments. It provides a structured framework for setting objectives, identifying dependencies, and sequencing work. This template facilitates PI Planning sessions, enabling teams to visualize their commitments and coordinate cross-team dependencies effectively. By promoting transparency and alignment, SAFe PI Planning empowers Agile organizations to deliver value at scale with predictability and quality.
DMAIC Analysis Template
Works best for:
Agile Methodology, Design Thinking, Operations
Processes might not seem like the funnest thing to dive into and examine, but wow can it pay off—a more efficient process can lead to serious cost savings and a better product. That’s what DMAIC analysis does. Developed as part of the Six Sigma initiative, DMAIC is a data-driven quality strategy for streamlining processes and resolving issues. The technique is broken into five fundamental steps that are followed in order: Define, Measure, Analyze, Improve, and Control.
8 Bit Hearts - A Retrospective
Works best for:
Agile Methodology, Retrospectives, Meetings
The 8 Bit Hearts - A Retrospective template offers a nostalgic and creative approach to retrospectives, using retro gaming elements to engage team members. It provides elements for reflecting on past experiences, celebrating achievements, and identifying areas for improvement. This template enables teams to foster a fun and collaborative atmosphere, promoting open communication and creative thinking. By combining nostalgia with reflection, the 8 Bit Hearts - A Retrospective empowers teams to build stronger bonds, boost morale, and drive continuous improvement effectively.
Quick Retrospective Template
Works best for:
Education, Retrospectives, Meetings
A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. The term “retrospective” has gained popularity over the more common “debriefing” and “post-mortem,” since it’s more value-neutral than the other terms. Some teams refer to these meetings as “sprint retrospectives” or “iteration retrospectives,” “agile retrospectives” or “iteration retrospectives.” Whether you are a scrum team, using the agile methodology, or doing a specific type of retrospective (e.g. a mad, sad, glad retrospective), the goals are generally the same: discovering what went well, identifying the root cause of problems you had, and finding ways to do better in the next iteration.