Kanban Pizza Game
If you want to understand the kanban principles and practices in fun and engaging way then the kanban pizza game is for you!
Trusted by 65M+ users and leading companies
This lean-agile coaching tool is the perfect virtual template to teach individuals and teams the basics of a kanban system. Teams are guided through 3 iterations, each one adopts more of the practices until the end when teams bring it all together.
The mechanics of the game are simple, you're a team of pizza chefs and it's your job to make the most pizzas you can as a team without creating waste. Apply WIP limits and roles to manage your flow and create pizza orders for your customers.
Play as a single team or compete with multiple teams and copy as many boards as you need to facilitate this fun learning session.
This template was created by Flowana.
Get started with this template right now.
Lean Coffee: Meetings without Agendas
Works best for:
Agile
Lean Coffee: Meetings without Agendas is a collaborative meeting format that fosters open dialogue and emergent topics. Participants suggest discussion topics, vote on them, and engage in time-boxed conversations. This template provides a structured framework for facilitating Lean Coffee sessions, enabling teams to prioritize topics, share insights, and make decisions collectively. By promoting inclusivity and adaptability, Lean Coffee empowers teams to address issues efficiently and drive continuous improvement.
Starfish Retrospective
Works best for:
Retrospectives, Agile Methodology, Meetings
The Starfish Retrospective template offers a structured approach to retrospectives using the metaphor of a starfish. It provides elements for identifying what to start, stop, continue, do more of, and do less of. This template enables teams to reflect on past iterations, identify actionable insights, and prioritize improvements. By promoting clarity and focus, the Starfish Retrospective empowers teams to drive meaningful change and continuous improvement effectively.
Miro Basics: Guide for New Participants
Works best for:
Agile
The Miro Basics: Guide for New Participants template offers a comprehensive overview of essential Miro functionalities and best practices for new users. It provides step-by-step instructions, tips, and examples to help participants navigate the Miro platform confidently and effectively. This template empowers new users to leverage Miro's collaborative features and unleash their creativity in visual collaboration. By promoting proficiency and engagement, the Miro Basics: Guide for New Participants enhances collaboration and productivity across teams.
All-in-one PI Planning
Works best for:
Agile
The All-in-one PI Planning template streamlines the SAFe Program Increment (PI) Planning process by providing a comprehensive framework for teams to collaboratively plan and align on objectives and dependencies. It integrates essential elements such as PI Objectives, Team Breakouts, and Program Board, enabling teams to visualize, prioritize, and coordinate work effectively. This template empowers Agile Release Trains to deliver value predictably and efficiently, driving alignment and synchronization across the organization.
Work Plan Template
Works best for:
Mapping, Project Planning
A work plan is essentially a roadmap for a project. It articulates the steps you must take to achieve the desired goal, sets demonstrable objectives, and establishes measurable deliverables. An effective work plan guides you throughout the project lifecycle, allowing you to realize an outcome by collaborating with your team. Although work plans vary, they generally contain four core components: goals, strategy, tactics, and deliverables.
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.