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.
Process Map Template
Works best for:
Agile Methodology, Product Management, Mapping
Process mapping allows you to assess, document, and strategize around any plan or approach your team has put in place. It’s a useful tool for eliminating or preventing blockers. Organized by stages, a process map enables your team to divide up a process or system and record deliverables and action items at each stage of the process. By breaking down the objectives, activities and deliverables at any stage of a project, you can gain insight into whether you are on track or effectively working through a problem.
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.
Daily Stand-up Meeting Template
Works best for:
Agile Methodology, Meetings, Software Development
The entire team meets to review the day before and discuss the day ahead. These daily meetings, also known as “scrums,” are brief but powerful — they identify roadblocks, give each team member a voice, foster collaboration, keep progress on track, and ultimately keep teams working together effectively. This template makes it so easy for you to plan daily standups for your sprint team. It all starts with picking a date and time, creating an agenda, and sticking with the same format throughout the sprint.
Plus Delta Template
Works best for:
Software Development, Meetings, Retrospectives
The Plus Delta template is a simple but powerful tool for collecting constructive criticism from a group. The format encourages you and your team to focus on what went well, what you should repeat in the future, and what you should aim to change. To complete a Plus Delta template, simply make note of things that are working and things you would like to improve. You can then file these elements into two separate columns. Use Plus Delta to showcase wins and learnings for your team, stakeholders, employees, and bosses.
4Ps Retrospective
The 4Ps Retrospective template offers a structured framework for teams to reflect on past iterations or projects using the 4Ps model (Praise, Problems, Possibilities, and Plans). It provides elements for sharing positive feedback, identifying challenges, exploring opportunities, and setting action plans. This template enables teams to conduct retrospectives systematically, generate actionable insights, and drive continuous improvement. By promoting a balanced and comprehensive approach, the 4Ps Retrospective empowers teams to enhance collaboration, boost morale, and achieve their objectives effectively.
Change Control Process Template
Works best for:
Agile Methodology, Documentation, Product Management
You can predict, research, and plan for every detail of a project to go a certain way—then along comes the unforeseen and modifications are needed. That’s when a change control process comes into play. It helps define the right steps to take, gives stakeholders full visibility, and reduces the chances of errors and disruption. And this template is easy to use and highly effective—for ensuring that proposed changes are reviewed before they’re implemented, and empowering teams to veto changes that might prove unnecessary or disruptive.