Scrum Compass
The Scrum Compass cards are based on the Scrum Guide.
Cards contain the accountabilities of the Developers, the Product Owner, and the Scrum Master. Additionally, the deck contains the accountabilities of the manager operating in the Scrum team environment.
Although the Scrum Guide itself does not mention the role of the manager, the role of the manager does not disappear. The character of this role changes. This is confirmed by many Scrum implementations.
The primary purpose of the Scrum Compass is to help Scrum practitioners apply Scrum principles properly. Cards are used to educate people who want or already use Scrum to make products or provide services.
The Scrum Compass does not impose the rules of application described in the accountability cards. However, their application increases the chances of success. If you have a role in the Organization, you can use the blank cards to add these accountabilities (option available only on printed cards).
This template was created by Tomek Pawlak.
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.
SIPOC by Dagmar Vlahos
Works best for:
Agile Methodology
The SIPOC template by Dagmar Vlahos provides a structured framework for documenting the high-level process flow of a system or project. It helps teams identify Suppliers, Inputs, Processes, Outputs, and Customers, facilitating a holistic understanding of the value stream. By visualizing key process elements and interdependencies, this template enables teams to identify areas for improvement and optimize workflow efficiency, empowering organizations to deliver value more effectively and satisfy customer needs.
Features Prioritization Tool
Works best for:
Agile
The Features Prioritization Tool offers a systematic approach to prioritizing product features based on criteria such as value, effort, and strategic alignment. It provides a structured framework for capturing, evaluating, and ranking feature ideas, enabling teams to make informed decisions about what to build next. With customizable scoring mechanisms and visual dashboards, this template empowers product teams to optimize their product roadmap and deliver maximum value to customers, driving competitiveness and market success.
Sailboat Template
Works best for:
Agile Methodology, Meetings, Retrospectives
The Sailboat Retrospective is a low-pressure way for teams to reflect on how they handled a project. By defining your risks (the rocks), delaying issues (anchors), helping teams (wind), and the goal (land), you’ll be able to work out what you’re doing well and what you need to improve on for the next sprint. Approaching team dynamics with a sailboat metaphor helps everyone describe where they want to go together by figuring out what slows them down and what helps them reach their future goals.
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.
Kaizen Report Template
Works best for:
Agile Methodology, Operations, Documentation
What makes a great company great? They know that greatness needs to be fostered and maintained — meaning they never stop working to improve. If you’re one of those companies (or aspire to be), a kaizen report is an ideal tool. It creates a simple visual guide to continuous improvement activities on a team, departmental, and organizational level. Using a kaizen report approach, every employee in an organization audits their own processes and understands what they might have overlooked, making this a powerful tool for increasing accountability at all levels.