Summarize all notable events since the last retrospective. Share updates on initiatives, key metrics, and anecdotes. Compare the current timeline and deliverables with what was originally planned.
What went well? Were any special milestones accomplished? Let each team member contribute.
What went wrong? Did any unforeseen obstacles arise? Identify the root cause of each one. Allow each team member to contribute. And remember, this isn't a blame game—focus on continuous improvement.
What were the main lessons from the roadblocks discussed? How can we solve each issue and improve?
Summarize any other valuable discussion points. It does not have to be directly related to the retrospective's main topic.
What were the main insights from this retrospective meeting? Include key decisions, plans, and any opportunities or concerns that should be shared with key stakeholders.
Clarify next steps, who's completing them, how we will measure them, and when they should be done by. Note this information here to share and assign.
How will we keep in touch and stay up-to-date about progress? When is the next retrospective?
A time for reflection can be a powerful force to move forward faster and better. Holding regular retrospective meetings (a.k.a. a "retro meeting") is one of the most effective ways to transform lessons from the past into plans for a brighter future. Use this retrospective template to capture invaluable insights, generate meaningful ideas, and move your team in the right direction.
Continuous improvement is the name of the game when it comes to retrospectives. This meeting note template lets you tap into the profound potential of these sessions by forming a blueprint for better teamwork through three main components:
Agile product teams made retrospective meetings popular, but anyone can benefit from them. Whether you're running a retrospective for project, service, or leadership teams, this outline can be easily modified to fit your unique approach. Tailor it to keep your sessions simple, stay focused, and capture the fresh feedback that matters most.
Cultivating an open, honest atmosphere is crucial to figuring out what's been working well and what needs work. Streamline trust through transparency by opening up this retrospective template to your team. With sharing and centralization capabilities, your team can contribute key discussion points before the meeting and stay aligned on the main takeaways afterward.
Staying action-oriented is essential for making true progress. This meeting note template can connect to your organization's favorite workflow tools and transform any of your notes into assignable actions with a few clicks. So your team can stay aligned and tackle the work in an environment that works best for them.
It's important to take a step back once in a while to see the best way to move forward. Drive positive change in your project, team, and organization with this retrospective template.
Yes. You can download the example retrospective agenda as a Word Doc or make a copy as a Google Doc. You can also add it to your free Hugo account from this page.
A retrospective meeting is a way for an organization to diagnose issues in their operation and discuss what can be done to improve. It's typically done after a project has occurred, with the idea of improving future projects. For example, if a company is struggling to meet deadlines on their construction project because they don't have enough staff members to do the work, the company may hold a retrospective meeting in order to discuss what problems they can overcome before moving forward.
The team needs to decide what they want to discuss during this meeting. During this meeting, the team should treat it like a brainstorming session. They will come up with ideas of how to approach the problem at hand. After their discussion, they will need to decide on what steps they will take in order to improve their process. It's important that all options are treated equally so that no idea can be discarded because it doesn't seem like an immediate solution.
A retrospective meeting is a meeting that takes place some time after the completion of a project to discuss what went well, what did not go well, and what can be done better. The goal is to identify some key learnings from the project in order to improve future projects.
It depends on your team. Some teams might decide that these meetings are helpful while others might decide that they're just a waste of time. It's up to you and the rest of your team to determine if these meetings will be worth their time and effort and whether or not you'll stick with them for the long term. If you're using Scrum, it's recommended that retrospectives should take place at regular intervals so that the team can review progress made towards meeting goals.
Retrospective: A retrospective is a meeting or other event at which we review what has happened and apply the lessons learned to our current work.
Retroactive: The word retroactive can be either an adjective or a verb and it literally means that something is done after the event.