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.
Agile Retrospective
Works best for:
Retrosprective, Agile Methodology, Meetings
The Agile Retrospective template offers a dynamic and adaptive framework for teams practicing agile methodologies. It provides elements for reflecting on sprint performance, identifying bottlenecks, and planning improvements. This template enables teams to adapt and refine their processes continuously, fostering a culture of learning and innovation. By promoting agility and adaptability, the Agile Retrospective empowers teams to optimize their workflows, drive continuous improvement, and deliver value to their stakeholders effectively.
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.
To-do List Template
Works best for:
Project Management, Education, Decision Making
A to-do list helps teams manage, organize, and prioritize their upcoming tasks. As a result, they can improve time management and streamline work operations. Using Miro’s to-do list template, teams create interactive, collaborative, and user-friendly task lists.
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.
I Like | I Wish | I Wonder
Works best for:
Agile
Feedback is a key part of any project development and crucial to the iterative process.
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.