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!
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.
SaaS Implementation Timeline
Works best for:
Agile
The SaaS Implementation Timeline template offers a visual roadmap for planning and tracking the implementation of Software as a Service (SaaS) solutions. It provides a structured framework for defining milestones, allocating resources, and monitoring progress. This template enables organizations to manage SaaS deployments effectively, ensuring successful adoption and realization of business value. By promoting transparency and accountability, the SaaS Implementation Timeline empowers teams to deliver projects on time and within budget, driving organizational agility and competitiveness.
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.
Rose, Bud, Thorn Template
Works best for:
Retros, Agile
The Rose, Bud, Thorn template is a structured method for team reflection and feedback, designed to help teams identify positive aspects, potential opportunities, and challenges within a project or situation. One key benefit of using this template is its ability to promote balanced feedback and productive discussions, which can lead to improved team processes and outcomes.
20/80 Process Diagram - EOS Compatible
Works best for:
Diagramming
The 20/80 Process Diagram - EOS® Compatible template is a visual tool for mapping out processes and workflows aligned with the Entrepreneurial Operating System (EOS®) methodology. It provides a structured framework for identifying core processes and key activities that drive business outcomes. This template enables organizations to streamline operations, clarify roles and responsibilities, and enhance accountability. By promoting alignment with EOS® principles, the 20/80 Process Diagram empowers teams to achieve organizational excellence and drive sustainable growth.
Cost-Benefit Analysis Template
Works best for:
Leadership, Decision Making, Strategic Planning
With so many day-to-day decisions to make—and each one feeling high-stakes—it’s easy for all the choices to weigh a business or organization down. You need a systematic way to analyze the risks and rewards. A cost benefit analysis gives you the clarity you need to make smart decisions. This template will let you conduct a CBA to help your team assess the pros and cons of new projects or business proposals—and ultimately help your company preserve your precious time, money, and social capital.
PI Planning Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
PI planning stands for “program increment planning.” Part of a Scaled Agile Framework (SAFe), PI Planning helps teams strategize toward a shared vision. In a typical PI planning session, teams get together to review a program backlog, align cross-functionally, and decide on the next steps. Many teams carry out a PI planning event every 8 to 12 weeks, but you can customize your planning schedule to fit your needs. Use PI planning to break down features, identify risks, find dependencies, and decide which stories you’re going to develop.