STATIK Canvas
This is a template with the most important aspects to map and understand a product or service at it's current state.
This template was built to help agile leaders, managers or facilitators to start a successfull Kanban implementantion. It is the kickstart to evolve your process and service delivery though an evolutionary change approach.
Use it when you're starting a new change initiative or you're being introduced to a new team, product or service for the first time or whenever you think that all those aspects from a STATIK process should be revisited.
Don't worry about having all fields full of information, just make sure you have mapped all the crucial aspects of your service and that you got a big picture of your process that shows you how things works. That's the first step to start an evolutionary change initiative.
This template was created by Lucas Guimaraes.
Get started with this template right now.
Fibonacci Scale Template
Works best for:
Agile Methodology, Prioritization, Agile Workflows
When you manage a team, you often have to estimate how much time and effort tasks will take to complete. Try what often works for Agile teams all over the world: Turn to the Fibonacci Scale for guidance. Based on the Fibonacci sequence, where each number is the summation of the two previous numbers (0, 1, 2, 3, 5, 8, 13, 21, etc.), this template can help you build timelines like a champ—by helping make sure that work is distributed evenly and that everyone is accurate when estimating the work and time involved in a project.
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.
FMEA Analysis Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
When you’re building a business or running a team, risk comes with the territory. You can’t eliminate it. But you CAN identify it and mitigate it, to up your odds of success. Failure Modes and Effects Analysis (FMEA) is a powerful tool designed to help you manage risk and potential problems by spotting them within a process, product, or system. And you’ll spot them earlier in your process—to let you sidestep costly changes that arise late in the game or, worse, after they’ve impacted your customers and their experience.
121 Kanban
Works best for:
Kanban Boards, Agile Methodology, Agile Workflows
121 Kanban template streamlines task management by providing a structured framework for prioritization and execution. It encourages a focused approach to task completion by limiting work in progress (WIP) and promoting collaboration between team members. With clear visualization of tasks and progress, teams can maintain workflow balance and deliver high-quality results efficiently.
Design Sprint Kit Template
Works best for:
Agile Methodology, UX Design, Sprint Planning
With the right focused and strategic approach, five days is all it takes to address your biggest product challenges. That’s the thinking behind Design Sprint methodology. Created by Tanya Junell of Blue Label Labs, this Design Sprint Kit provides a set of lightweight templates that support the Design Sprint’s collaborative activities and voting—and maintains the energy, team spirit, and momentum that was sparked in the session. Virtual sprint supplies and prepared whiteboards make this kit especially useful for remote Design Sprint Facilitators.
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.