Agile Retrospective
This template offers scaffolding frames for the 5 steps of an Agile Retrospective to follow a structure that helps the group to focus.
This template offers scaffolding frames for the 5 steps of an Agile Retrospective to follow a structure that helps focusing the group on the work at hand, getting a shared perspective, fostering divergent thinking, coming up with actionable ideas and closing with a sense of having achieved something.
When to use this template?
You should try it if you your “retrospectives” are feeling ineffective and you have a feeling nothing ever changes, other challenges it helps with:
When you have room full of disengaged individuals
When your actions land on premature convergence and habitual thinking
Or there are no actions at all
Each frame has a set of activities that would fit a team of 5 or 6 looking at a 10/15 days time span. You should change activities if you think they don’t fit in your context.
How does a five steps Agile Retrospective work?
As a tech lead, scrum master or product manager you are challenged with running effective retrospectives. This template will guide you to focus on:
Setting the stage to be present and energized in a blame free mindset.
Clarify roles. Could it be useful to have somebody taking notes while you focus on facilitation? How about a timekeeper?
Is there any team agreement we need to highlight. The OARRs is the place!
You can then read Kerth’s prime directive from the template. Then you can do a voting on the ESVP (Explorer, Shopper, Vacationer, Prisoner). If everybody is a prisoner would it be beneficial to focus on why that is rather than going ahead with your plan?Gather data to pause and collect all perspectives about the topic. The FRIM activity in the template uses axis with Frequency and Impact for the events we share.Generate insights, divergent thinking about how the next iteration can be the best one yet?Decide what to do to browse the ideas that emerged during generate insights and decide which ones we want to tackle in the next iteration. The template activity circles and soups allows to visualize what the team can control and the rest.
Close out to get feedback on the retrospective. In the template use ROTIPlusDelta to determine how the retrospective went and collect one change that would have increased your return on time invested and one thing you liked about the session.
The Agile Retrospective template is a Miro representation of an Agile Retrospective as intended by its creators in the seminal book “Agile Retrospectives Making good teams great” by Esther Derby and Diana Larsen. All activities are credited in the template itself.
This template was created by Enrico Teotti. You also can see how it works in this video.
Get started with this template right now.
Timeline Workflow
Works best for:
Project Management, Flowcharts, Operations
A timeline is a visual tool that chronologically plots out projects step by step. It’s an ideal tool for your team to tell stories (such as an overview of events in your organization) and visualize your projects or processes. The Timeline Workflow template is perfect for any project that relies on visual content. You may find it beneficial to use with your team and also to share with other stakeholders or clients to keep them in the loop on your progress.
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.
8 Different Ways to Organize Your Backlog
Works best for:
Agile
Explore 8 different techniques for managing and prioritizing work effectively with this template. From prioritization matrices to story mapping, it offers a comprehensive overview of backlog management strategies. By understanding the strengths and limitations of each approach, teams can tailor their backlog organization to optimize workflow, empowering teams to stay organized and focused on delivering value.
The Hot Air Balloon Retrospective
The Hot Air Balloon is a simple activity for helping the team identify things that makes them move faster, and things that slow them down.
The 4-Step Retrospective
Works best for:
Retrospectives, Agile Methodology, Meetings
The 4-Step Retrospective template offers a simple yet effective framework for conducting retrospectives. It provides steps for reflecting on what went well, what didn't go well, what could be improved, and action planning. This template enables teams to systematically review past iterations, identify areas for growth, and implement actionable improvements. By promoting a structured approach to reflection and improvement, the 4-Step Retrospective empowers teams to drive continuous learning and enhancement effectively.
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.