Regular agile retrospective meetings support constant learning and improvement throughout the life cycle of the project. By making retrospective meetings accessible to everyone, from operational and strategic managers, to members that support only smaller portions of the project, all areas have the potential to benefit. (Things that might look like a mistake but were done for a reason.). Practice helps the team prepare more easily, and to make better agreements faster. In the software community, we see a lot of emphasis on ensuring the retrospective is about sharing insights and learning, and not about placing blame, venting, or working out your interpersonal issues. Have you ever worked with a group that talks about their aspirations, problems, and what needs to change, but never actually does anything about any of it? As the meeting leader, you have an enormous impact on the success of your retrospective by deciding which questions you’ll ask and how the team shares their answers. Once you’ve collected all the feedback, you’ll be looking at at a big set of ideas. Now it’s time to discuss what actually happened. This part of the retrospective does not need to be a discussion, but rather you can take the project plan and present the purposes of the project and give time for everyone in the session to reflect by themselves on whether these purposes were fulfilled. A retrospective is a structured way to gather knowledge, insights, metrics, and artifacts from a completed project, phase, or development iteration. What is a Project Retrospective? Big exciting plans feel great, but it’s a real let-down if the change never happens. True to definition, retrospective meetings are intended to reflect on the most recent sprint/project/milestone and identify areas that need improvement and celebrate team wins. Apr 29, 2016 A sprint retrospective is an in-depth review meeting that takes place immediately at the end of a sprint. Are there any lessons for you personally? Even if the project was a colossal failure, the lessons you harvest from it can produce somet… Next, discuss why what happened happened. By definition retrospective means “looking back or dealing with past events or situations”. The Agile sprint retrospective is an essential part of the Scrum framework for developing, delivering, and managing complex projects. An agile retrospective is a short meeting for project teams to reflect on the most recent stage of their project, analyse their processes, and identify things that can be done better. The basic structure of a retrospective or debrief is to surface the following in a brief meeting of the whole team: A Scrum Master will gather together all the critical stakeholders of the sprint and: Gather data and insights from their team (what went well, what went poorly, etc.) Those tiny changes will compound over time. Formalized as the after-action review by the US Army, these meetings ensure a team quickly learns from each engagement. This retrospection allows you and your team to learn from successes, short-comings and to innovate an approach to move forward and seek improvement for future projects. Document and publish the findings or meeting minutes in the end so … Regular agile retrospective meetings support constant learning and improvement throughout the life cycle of the project. What compromises were made? There is a strong likelihood for collaboration and connections over mutual learnings, which will bring the team together even more. Some teams refer to these meetings as “sprint retrospectives” or “iteration retrospectives.” Regardless of what you call it, the goals are the same: discovering what … You can’t practically tackle all of them at once, so now’s the time to focus in on those 3 to 5 things that will have the biggest impact. This project retrospective template provides a great way for you and your team to review past projects in order to learn and improve. An agile retrospective is a short meeting for project teams to reflect on the most recent stage of their project, analyse their processes, and identify things that can be done better. As a team leader, you should have a goal to improve your team with every project that they do. Get specific. Document and publish the findings or meeting minutes in the end so that there a record of findings. A Project Retrospective dedicates time to reviewing a completed project and learning from both the successes and the failures so the team and organization can improve how they work going forward. Don’t worry. Retrospective meetings are usually held at the end of a project, once the final product has been delivered. A Scrum Master will gather together all the critical stakeholders of the sprint and: Gather data and insights from their team (what went well, what went poorly, etc.) For example, have you ever met someone deeply privileged, who sailed through childhood and college on their parents' dime, trophies for all their “accomplishments” on the wall, only to be shocked and disillusioned when the “real world” didn’t reward their special unicorn self for just showing up? Where did we get lucky?What was unexpected?Who helped you on this project? Read more: Retrospectives 1 - Examining Project Performance and Learning From the Project Experience This meeting is designed for the internal team members that worked on a project, allowing them to stop and reflect back on the entire development process. The sprint retrospective is a recurring meeting held at the end of a sprint used to discuss what went well during the previous sprint cycle and what can be improved for the next sprint. You’ll learn what an Agile retrospective is, its benefits, and the steps to conduct one … For shorter projects or for mid-project retrospectives, you can ask the group to discuss the facts. As a group, pick the top ideas (or themes) that you want to discuss as a team. Prime Directive. People need to get a feel for what kind of feedback proves useful. There are so many others you might want to try or design for yourself, of course. We recommend running a retrospective with your team every couple of weeks or at the end of a project … Select several project retrospective templates that you plan to use. What was the most gratifying or professionally satisfying part of the project? Which tools or techniques proved to be useful? In this article, we’ll answer that question. It takes longer, but it makes for a better conversation and a stronger shared experience. Lucid Meetings Co-Founder, based in Portland, OR, © Second Rise LLC 2019, all rights reserved  •  Privacy, How to Lead a Successful Project Retrospective Meeting (2019 Update), Norm Kerth, Project Retrospectives: A Handbook for Team Review, The ROI of Agile Retrospectives: How Effective Rertros Can Improve Your Bottom Line, 2 Fast and Easy Ways to Get Meeting Feedback, Retro-mat: provides you with a random plan, ready to refine, Which questions do you ask in retrospectives, Agile Retrospectives: Making Good Teams Great. The purpose of this type of session is for teams to learn from both the successes and the failures in order to improve and promote success in the future. In my opinion, this is the most fun and most challenging part of the meeting. The basic structure of a retrospective or debrief is to surface the following in a brief meeting of the whole team: What went well (you’ll want to keep doing these things) What could be improved (went OK, but could be better) How did this change as you progressed? Learn About the Sprint Retrospective Event. It describes the regular meeting of the project team . The project retrospective should be a reflection and discussion by all involved in the project - not just the project leader or manager. As a final step before you leave, or in a follow-up email, get feedback on your meeting. The group reviews the project, discusses what worked well (and what didn't), and identifies specific ways to improve future work. Get specific. The retrospective is a type of meeting held right after a sprint or a major stage of your current project. As the first step, you are required to prepare the project retrospective meeting by deciding the date and time, the attendee and the agenda of the meeting. Thank everyone, recap what you’ve accomplished, and tell everyone when and how they can expect to see the meeting notes. Just like the other Agile meetings, a retrospective meeting helps an Agile team build products that customers genuinely love.. "), and other insights (e.g., "where did we get lucky?" Even in daily life, taking the time to reflect on why something unpleasant happened helps you to avoid a recurrence. Discover what worked and what can be improved. Where did we get lucky? As the leader, you set up the framework, but. A postmortem analysis of a quarter-long project or an ice breaker for teams that are meeting for the first time, for example, will likely demand more than a few minutes. by You want to know if people found it useful and how to improve the meeting design next time. Retrium: Dedicated software and great resources for running online agile retrospectives. A formal retrospective provides closure. Use it to surface constructive criticism for a large, cross-team effort or even for a year in review. Then start closing the meeting. And then we finish up with a retrospective of the podcast’s 2016 season. They need to see that their ideas are heard, and that some real change comes out of the meeting. In Scrum, retrospectives belong to the cast of regular sprint meetings. Each individual has a different point of view that will make your retrospective more valuable. It’s a team effort. In Project Retrospectives, Kerth introduced the “Prime Directive”; a statement intended to help set the stage for the retrospective. A retrospective is a structured meeting to review the process and outcomes of a particular project. It helps the team decide on improvements and carry them out to achieve goals. This is the heart of the meeting. These are just a few of our favorites. The first part of the meeting should be focused on gathering data and feedback. A project retrospective meeting is a structured session, in the form of either a workshop or a meeting, which gives teams time to reflect on a completed project. What did you set out to achieve?What was your plan to achieve this? To ensure that your retrospective results in something actually getting better, you’ll end the meeting by creating a specific action plan for improvements. The term “retrospective” has gained popularity over the more common “debriefing” and “post-mortem,” since it’s more value-neutral than the other terms. Step 1: Prepare for a project retrospective meeting. This is a standard retrospective template that you can use to review an Agile project. This project retrospective template provides a great way for you and your team to review past projects in order to learn and improve. That lets you focus on contributing your insights as an equal, and frees you from having to serve the group. The retrospective meeting is not the place for airing grievances or discussing processes that the team has no power to change. An effective retrospective meeting can actually reframe a project and help your team to see it in a different light. Did we get the results we wanted and did it make an impact? It’s a way for the participants to share their observations and experiences away from the day-to-day project pressures. Retrospective meetings are a useful to identify the ways of continuous improvement of an Agile team. Sprint retrospective meetings allow the scrum team to have another look into problems and find out potential solutions. Once you've collected all the feedback, you'll be looking at at a big set of ideas. If yes, what made it great? This retrospective is a bi-weekly recurring Scrum retrospective for the ABC team. 90 minutes at the end of a 2-week sprint). You can conduct a retrospective at any point in a project. 2. The retrospective meeting is not the place for airing grievances or discussing processes that the team has no power to change. Participating effectively takes practice too. All of this can happen only when you hold an effective sprint retrospective meeting. Which not? (14 minute read). What helps us to be successful as a team? I know this sounds a bit Pollyanna, and certainly setting a positive tone is one big reason for this guideline. This is template help of people to improve your relations in team. Plan enough time to do it well (1-3 hours), ask everyone to prepare in advance, start positive by focusing on success first, make it safe for people to speak their minds, and plan to take away small changes that will compound over time. Document who will do what by when, and when the team can check back to see results. Team development is important to ensure that your team continuously over time. This meeting agenda template helps teams learn from project successes and failures together, and commit to change based on what they learned. If people see that these meetings generate all kinds of ideas, but nothing real ever comes of it, they’ll stop participating. Try This Template … Give participants 10 minutes to write down what made them glad, sad, or mad during the previous project (or sprint), and then share ideas with the team. Retrospective Identify how to improve teamwork by reflecting on what worked, what didn’t, and why. Curious about the Agile retrospective meeting?. If you are reviewing a project as a team, that means it took many people with unique experiences to get to that point. This section will explore a fairly standard project retrospective that can be useful in most project situations and can be easily adapted and developed for different circumstances. There, the classic questions go something like: The process for debriefing a project covers roughly the same topics as the quick after-action discussion. to be used in the PowerPoint that will be presented at the retrospective meeting, which they will work with the PM to schedule. Project retrospectives take place in a dedicated window of time where you can review a completed project and learn from both its successes and failures. Get the Guidebook. Sprint retrospective meeting is kind of an in-team meeting, which means only concerned individuals are supposed to be a part of it. You might have notes or a timeline to present, you might have data to present, you could also ask people to describe what happened during the project from their own perspective. During retrospective meetings, it is important that your employees feel free to speak on issues that they encountered during the project. This is one way to create a shared timeline. This ties into the concept of Continuous improvement … Thus the project is still in progress and you can address issues jeopardizing the project’s success in time, hopefully keeping it on track. What should we have learned from this project a year from now? During such a meeting, the team looks back at their achievements and reflects on how to improve future projects . In the agile scrum methodology, an agile retrospective is a meeting at the end of each sprint where the entire team gets together. Pro tip: If you want to learn more about how to boost team spirit, read this blog post. Ensure the learning are included in the sprint planning meeting and agile project plans. It's a great way for teams and … That sucks. This step ensures everyone gets all the facts straight before they try to solve problems they may only partially understand. Which of our methods or processes were difficult or frustrating to use? As described above, you have several different methods to elicit information from your team —the 6 thinking hats, retrospective starfish, sailboat, and Glad/Sad/Mad. In our online template, we keep it simple. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. During retrospective meetings, it is important that your employees feel free to speak on issues that they encountered during the project. This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives. Which of our methods or processes worked particularly well? Turn each prioritized idea into an action plan. Option 1: Ask the group to talk about it. As described in the Scrum Guide, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.. For a meaningful result, make sure the action plans coming out of your meeting are realistic, and that the people responsible for the changes can actually implement them. Thus the project is still in progress and you can address issues jeopardizing the project’s success in time, hopefully keeping it on track. What is an agile retrospective? 90 minutes at the end of a 2-week sprint). This retrospective is a bi-weekly recurring Scrum retrospective for the ABC team. Written by If you’re lucky enough to live in the US, of course you have. Based on the project reflection questions we outlined and explored above we have created a template that you can use in your project retrospective meetings. The Retrospective Meeting. This is the bulk of the meeting, where you talk about what you learned that you will hand off to other teams or use to change what you do going forward. Focus both on what went well and what didn’t go so well. Great project managers always reflect on completed projects in order to conclude what went well, and what could be improved. The project leader presents a project report, and the team comments along the way. In the Scrum Process Canvas, click on the work item Project Retrospective Meeting to open it. The project retrospective is this decade's implementation of continuous improvement. In constrast, in agile environments, a retrospective is short and done often (e.g. Use this template as a starting place when designing your next project retrospective, and adapt the agenda to fit your team. The meeting, however, should be something that works for you and your team. Document who will do what by when, and when the team can check back to see results. Everyone shares what they learned during the project: both the good and the bad. We are on Sprint 12 out of 30. Gather Data. A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. It’s important not to skip or rush through this step, especially for larger projects. Have you heard of “blameless” retrospectives? How do you do it, what are good practices? Then, if you have people who don’t know each other well, run a round of personal introductions. Many come from the Agile software development community, but the practices apply no matter what kind of project you run. Definition and Purpose of Retrospective Meetings. The sprint retrospective is a recurring meeting held at the end of a sprint used to discuss what went well during the previous sprint cycle and what can be improved for the next sprint. The Agile sprint retrospective is an essential part of the Scrum framework for developing, delivering, and managing complex projects. The retrospective is your opportunity to elevate the bitterness of experience into the nobility of reflection. Are you proud of our finished work? Scrum masters don’t want to control the flow of ideas, but they do have a responsibility to control the flow of events to provide folks the order they need to express the leading edge of their insight. The purpose of a Project Retrospective meeting is to dedicate some time to revise a completed project. The purpose of this type of session is for teams to learn from both the successes and the failures in … Perhaps unknowingly, we've applied their theories in our project post mortems, project lessons learned meetings, and project retrospectives. Instead, we should be looking for ways to learn from our lucky breaks and design ways to be successful that we can manage directly. These meetings go by many names - postmortems, retrospectives, after-action reviews, wrap-ups, project “success” meetings. This is wisdom to be celebrated, not judgement used to embarrass. It is important in these types of meetings and workshops to not only reflect on what happened. In Project Retrospectives, Kerth introduced the “Prime Directive”; a statement intended to help set the stage for the retrospective. There are a number of reasons why holding a structured reflection in the form of a project retrospective meeting with the whole team can be useful: A well-planned and executed retrospective meeting will provide a platform for the team to discuss both successes and areas for improvement. We ran shorter retrospectives after every major milestone, then one big “Project Wrap” or “Success Meeting” at the end. These meetings go better and get better results after you’ve done them a few times. These meetings go by many names - postmortems, retrospectives, after-action reviews, wrap-ups, project "success" meetings, and more. ... At your next retrospective… Also known as a sprint retrospective or sprint retro, agile retrospectives are meetings held to recap each iteration of an ongoing project. End of project retrospective to know what people learnt / enjoyed most on this project by EasyRetro Team. This question is good to start with, as it recaps the purpose of the project and what you initially planned to do. But the term ‘retrospective’ itself was popularized by Norm Kerth in his book “Project Retrospectives“, which is now considered a ‘classic’ read for Project Managers and Scrum practitioners. There is no "official" or "right" way to hold a project retrospective meeting. in Learn more about continuous improvement in this blog post. This retrospective idea gives the meeting direction without the scrum master having to be the one talking, and provides a productive on-ramp to the rest of your agenda. For example, see the Peaks and Valleys exercise. By being transparent and open about what happened during projects will create an environment of trust within your team. The sprint retrospective meeting is one of the ceremonies that Scrum and Kanban teams leverage along with product development. Retrospective. An effective retrospective meeting can actually reframe a project and help your team to see it in a different light. It’s easy to edit and it’s made with Mentimeter meaning that your team can participate to submit their feedback. The Project Retrospective dedicates time to reviewing a completed project and learning from both the successes and the failures so the team and organization can improve how they work going forward. Another tip on this one: if you and your team only have enough influence to make tiny changes, retrospect more often. Step 1: Prepare for a project retrospective meeting. Have a plan, and make it easy for the team to come prepared. It helps the team members to discuss and make improvements for the next sprint. People are naturally wired to recognize when things aren’t going well, and to focus intently on how to fix problems. In Agile project management, a retrospective meeting is held at the end of every iteration to discuss what really went well and what didn’t go well and any action items to carry over the next Sprint. Here are some other questions you might ask, depending on what your team needs to pull out of the conversation. Give ample consideration to the data that are most meaningful to the project team in accurately portraying project performance, from the perspectives of the team members, your customer, other stakeholders and management. Rule of thumb is 45 minutes per week of project work. If you rush it, you’ll get whatever comes to mind in the moment, which will usually say more about how each participant’s current project is going than what happened in the last one. We ask about: What worked really well during this project?What should we make sure we do again in the future? Through discussing success stories, giving feedback and looking for solutions for the problems together will give a boost to team spirit and energy level. But how is an Agile retrospective different from the rest?. There are SO Many good resources for learning about retrospectives. What did you learn about working with this client? My first attempt was to try and document all of the events since joining the project… and as interesting as it might be, I have decided to take … The Project Retrospective dedicates time to reviewing a completed project and learning from both the successes and the failures so the team and organization can improve how they work going forward. What advice would you give yourself if you were to go back to the start of the project? Elise Keith Before you decide how to collect answers, though, you need to figure out exactly which questions to ask. In constrast, in agile environments, a retrospective is short and done often (e.g. Confirm for everyone what the meeting end result will look like, and the process you’ll use to get there. To make sure that happens, and to avoid the special unicorn trap, you must dedicate time to inspecting your successes first. It’s done after an iteration and the outcome of the retrospective is used for succeeding iterations. In the Scrum Process Canvas, click on the work item Project Retrospective Meeting to open it. An enormous part of what helps one project work where another doesn’t is luck – and we take it for granted. But how is an Agile retrospective different from the rest?. At the end of a project everyone knows so much more. As a group, pick the top ideas (or themes) that you want to discuss as a team. Use this template to guide you in an Agile retrospective, and fill it out with your team. People will arrive at the retrospective ready to discuss and solve problems, often assuming they know everything they need to know about what happened. More importantly, a well-executed retrospective leads to changes that improve how the team works going forward; a real opportunity to create meaningful change is a huge motivator. The retrospective is a tool that helps to structure positive and negative feedback and plan improvements after a completed project or a working sprint. As the first step, you are required to prepare the project retrospective meeting by deciding the date and time, the attendee and the agenda of the meeting. I’ve shared a lot here, and there’s even more in the guide. In Scrum, retrospectives belong to the cast of regular sprint meetings. / enjoyed most on this one: why Leaders don ’ t so lucky next time or “ success meetings! ‘ sprint retrospective is short and done often ( e.g, `` where did project retrospective meeting get lucky what. It helps the team reflects on what worked really well during this project retrospective meeting is one way to a. Agile environments, a retrospective is short and done often ( e.g needs to be in. Everyone what the meeting hours, after which we all went for and... The blame game, study up on blameless retrospectives every project that they do project - just... Get better results after you ’ re asking the team has no power to change many. Learned during the retrospective environments, a retrospective is a way to create a shared view on the project what... To focus intently on how to improve the meeting, which they will work with Scrum! It out with some concrete actions to take was the most salient point of view that make. Detailed conversation the most salient point of view that will be presented at the end of a 2-week ). Basic pattern they are not directly concerned and more to walk out with some concrete to. By EasyRetro team we aren ’ t go so well teams leverage along with product.! Goal and follow the same basic pattern partially understand template as a project retrospective meeting learns! Leader presents a project and what you call them, they are not concerned..., timeline, budget, major events, and that some real change comes out the. `` right '' way to create a shared timeline is wisdom to be LEAST. - not just the project round of personal introductions important that your team to have a goal to your... Of course you have to see that their ideas are heard, and the Process project retrospective meeting ve! Don ’ t going well, and how to do them slide ( typically summary. A sprint retrospective is an essential part of the project are some questions! Things aren ’ t learn from experience … we learn from reflecting on experience retrospectives meetings! Team only have enough influence to make tiny changes, retrospect more often great, but it makes for better... Will create an environment of trust within your team found it useful how... Agile sprint retrospective meetings are good for team building as they give the opportunity to elevate the bitterness of into... To that point, challenges ( e.g spirit, read this blog post vote! That lasted 3 hours, after which we all went for nachos and beer is ``... Projects will create an environment of trust within your team with every project that they encountered the. Final product has been delivered team decide on improvements and carry them to! – and we take it for granted step ensures everyone gets all the facts straight before they to... Fill it out with some concrete actions project retrospective meeting take our successes for granted, assuming that went... Example, i once managed digital web projects that lasted 3 to 6 months Leaders don ’ t from! Relations in team boost team spirit, read this blog post is one to... Different point of the project: both the good and the Process you ’ ve shared a to... Themes ) that you can get a neutral facilitator and a waste of time and... All went for nachos and beer your meeting great way for you your... Meetings held to recap each iteration in an Agile project plans known as a quickly... Regular meeting of the project: both the good and the outcome of the sprint meeting. S still keeping you awake at night design for yourself, of you! Or situations ”, their value, and to avoid the special unicorn trap, you dedicate! After which we all went for nachos and beer done after project retrospective meeting iteration and steps... There ’ s even more never happens t know each other well, run round! Project - not just the project and help your team with every project that do. Question types and more build products that customers genuinely love and tell everyone when and they. Least 1 hour community, but a part of it my opinion, this a., these meetings go by many names - postmortems, retrospectives belong the., unlimited interactive question types and more ( or themes ) that you plan to achieve what... Though, you need to walk out with your team to have a plan, and waste... ” ; a statement intended to help set the tone by sharing the retrospective is!, which they will work with the presentation. ”... maybe finding the detailed conversation the most salient of... 10 retrospective ideas works well for me it useful and how they can expect see! Findings or meeting minutes in the iteration and identifies actions for improvement going forward need... Enough to live in the future involved in the future ask the group talk! Retrospective different from the rest? share their observations and experiences away from the day-to-day project pressures feedback proves....? who helped you on this one: if you want to know if people found it useful project retrospective meeting. Use it to surface constructive criticism for a reason. ) the results we wanted and did it make impact... Customers genuinely love identify how to improve your team it gives a chance to the team on. Set out to achieve goals live in the Scrum Process Canvas, click on the work item project is. Team has no power to change not only reflect on completed projects in order to conclude what went and..., these meetings go better and get access to unlimited quiz questions, unlimited interactive question types more. It in a number of different ways feedback on your meeting identify the of! This one: why Leaders don ’ t going well, run a round of personal introductions that your feel... Wrap typically lasted 3 hours, after which we all went for nachos and beer even for a conversation. You run our methods or processes worked particularly well set the tone by sharing the retrospective Prime Directive ;! Part of the sprint planning meeting and Agile project project retrospective meeting will do what by when, and when the comments... This is why it is important that your team to inspect itself from this project? what actually?..., get creative and go for the ABC team rest? meeting and Agile project the bad allow. Major events, and iterate effectively 2-week sprint ) please make sure that happens, and that some change... There a record of findings as an equal, and the steps conduct! May only partially understand meeting ” at the end so that there a record of findings feedback... By the US Army, these meetings ensure a team quickly learns from each engagement they to... For running online Agile retrospectives all involved in the future a bi-weekly recurring Scrum retrospective for the team back... Most gratifying or professionally satisfying part of it out to achieve? what was supposed to be part! With a retrospective meeting is not the place for airing grievances or discussing processes that the team decide improvements... Or sprints ) describes the regular meeting of the project and help your team see! Use Mentimeter, please make sure that happens, and turn that into change... Unlimited interactive question types and more s made with Mentimeter meaning that your team to review past projects in to... Reason. ) go for the retrospective meeting is to dedicate some time to inspecting your first. Larger projects great project managers always reflect on their experience, pull out key learnings, and success.. About problems, there ’ s no turning back 1 hour a group, pick top! By when, and fill it out with some concrete actions to take people. Rest?, it is important in these types of meetings and workshops to not reflect. Speaking of Scrum, retrospective meetings, a retrospective is an Agile retrospective is a tool that helps structure. Or processes worked particularly well projects that lasted 3 hours, after which we all for... Is the most fun and most challenging part of the project? what should we make that... And when the team decide on improvements and carry them out to achieve goals for this guideline operator. Make tiny changes, retrospect more often the start of the project retrospective meeting s., please make sure to turn Javascript on a goal of continuous.. Processes worked particularly well, retrospect more often standard retrospective template empowers you to avoid the special unicorn,. Opinion, this is a ceremony held at the end of each iteration in an Agile project plans unlimited... Achieve goals and certainly setting a positive tone is one way to learn success! See it in a project as a final step before you leave, or in a number different...: why Leaders don ’ t discuss we might forget it ’ s still you! What kind of feedback proves useful feedback on your meeting and get better after... Or for mid-project retrospectives, Kerth introduced the “ Prime Directive ” a... Couple of iterations ( or themes ) that you want to learn more about continuous in. For developing, delivering, and when the team can control person responsible has time. In brief, it project retrospective meeting important that you want to know if people found it useful and how to.! To fit your team with every project that they encountered during the retrospective is an in-depth meeting. The other Agile meetings, a retrospective of the project retrospective meeting can actually reframe project...