FigJamWax nostalgic with our project retrospective template
Before you jump into your next action plan or gap analysis chart, learn everything you can from your previous campaigns with project retrospective ideas from FigJam.
Project retrospective template
Review past outcomes to refine future projects in an interactive online space.
Retro is always in style
Schedule a project retrospective meeting to take a productive trip down memory lane—and leave no stone unturned.
Reflect on challenges: Look back at a recent undertaking and identify the obstacles that stood in your way.
Leverage your learnings: Tackle your next project head-on with a new-and-improved action plan.
Celebrate a job well done: Recognize and reward every team member’s accomplishments and groundbreaking new ideas.
FigJamRetrospectives need perspectives
Receive valuable input from all involved on a collaborative FigJam whiteboard. Start with a project retrospective agenda that everyone can see, then open the floor and let the participation pour in via notes, votes, Lil todos.
Reflection leads to perfection
Learn from your last project to make your next one a masterpiece. Keep improving with more helpful tools and templates from the FigJam community.
FAQs
A project retrospective is a team exercise in which members take a comprehensive look-back at a previous project. You can think of a retrospective as a team-wide report card for a recent venture or campaign.
Project retrospectives allow you to honestly assess your progress by sorting all aspects of your project into three categories: did-wells, pain points, and actions needed.
During a project retrospective process, most teams grapple with 3 primary questions in order to gain insight into the good, the bad, and the ugly of their most recent endeavor.
What are the 3 retrospective questions, you ask? There’s a little leeway depending on the scope and purpose of your project, but most teams work to answer the following:
- What went well?
- What problems did we face?
- How can we improve next time?
First time reflecting on a campaign? No sweat. Here’s how to conduct a project retrospective, step by step:
- Gather all involved parties into a room—physically or virtually. If your project team is scattered across territories and time zones, an interactive whiteboard from FigJam can bring everyone together in one space.
- On your project retrospective template, create 3 columns—one for what went well, one for the problems you faced, and one for what you will do next. Discuss each section with the team, updating the columns in real-time with feedback and figures.
- At the end of the meeting, zoom out to identify wins, trends, and the path to future success. Then, turn your insights into action items with widgets, templates, and project retrospective examples from the FigJam community.
A sprint retrospective (also called an agile retrospective) is held at the end of a sprint. Scrum teams reflect on the previous sprint and identify ways to improve in the next one. (Note: a sprint retrospective also differs from a sprint review in that sprint reviews focus on what tasks were completed to help plan for future sprints vs. how teams completed the work).
A project retrospective meeting covers the entire project with the goal of finding ways to improve the overall project process.
All team members involved in the project should join the retrospective session; the attendee list typically includes project managers, designers, and developers that can offer their perspective, provide feedback, and identify areas of improvement for future projects.
Other templates you might like
Explore 1,000+ templates on the Figma community
Explore even more templates, widgets, and plugins—all built by the Figma community.
