villatopia.blogg.se - Project retrospective template

Related: 5 Tips for Holding Effective Post-Mortems Who benefits from a project retrospective?Įveryone who’s been involved in the project will benefit from a retrospective because it’s designed to help the team work more efficiently and improve over time. If you run retrospectives at the end of each sprint, they help you monitor project progress at regular intervals. Project retrospectives can be run at the end of a project or at the end of Agile sprints, which may happen multiple times throughout a project timeline depending on the length or complexity of the project. It’s most often used by agile teams following the Agile methodology, but it’s also helpful for any team looking to reflect on project progress and encourage continuous improvement. What is a project retrospective?Ī project retrospective is a process where a project team reflects on a completed project and looks for opportunities to improve the way they work together in the future. Candidly discuss what went well, what didn’t, and where you see potential for better processes or outcomes in future work together.

Moved Next Steps to first page, and added Key Takeaways column.Gather a group to thoughtfully analyze work during a recent project.

Renamed from “Debrief” to “Retrospective”.

“The Secret to a Good Retrospective? Actually Having Them!” November 20, 2018.

Unless otherwise stated and to the extent possible under law, we dedicate this toolkit to the public domain.

Discuss and capture Key Takeaways and Next Steps.

This makes sure you cover all three dimensions adequately.

After everyone has had a chance to contribute, review Results, Process, and Relationships section-by-section.

The facilitator should do this while allowing the participants to speak more free-form. It’s not necessary for participants to categorize what they want to share under Results, Process, or Relationships.

Open up discussion to other thing that went well and could be improved.

For example, did something unexpected (either good or bad) emerge that wasn’t captured in the Success Spectrum?

Capture other Results, both good and bad.

Mark the hits and misses (for example, you could bold the hits and strikethrough the misses), adding notes in the appropriate Results column. Ideally, people are taking notes during the project itself, not just waiting until the Retrospective. This can also happen asynchronously before the full-group meeting. People should take their own notes in this phase rather than use the shared template, so that everyone has the opportunity to do their own thinking.

Give everyone time to reflect individually on what went well and what could have been improved.

Be sure to copy the project’s Goal + Success Spectrum into the appropriate section of the template, so that the team can review this together. You should allocate 1-2 hours for a full-group meeting, depending on the complexity and size of the project. Using the Retrospective TemplateĮveryone on the team should participate in a Retrospective. We use Interaction Associates’ Results-Process-Relationships framework to highlight the different dimensions of a successful project. What about the relationships between the participants worked well, and what could be improved? What about the process worked well, and what could be improved? What were the outcomes, both good and bad? Includes a copy of the Goals + Success Spectrum. For example, if you’re debriefing a meeting, what shifts in the meeting design did you make in the moment, and why? Any changes you made to the plan as you were executing it.

High-level learning and immediate next steps. To use, click on this link to open Google Docs, then select File > Make a copy… in the menu. It is a critical part of the learning process.įor bigger projects, we use this Google Doc template for retrospectives. In its simplest form, the Retrospective captures what went well, what could have been improved, and the changes to make for next time. The Retrospective is an opportunity to debrief projects, make meaning of what happened together, and document lessons learned.