What Happens in Retrospective Meetings?

Posted by. Posted on: at.

What is a Review Meeting?

Postmortems, post-action reviews, project successes, retrospectives, commonly called review meetings, are held to examine the success of a particular project, especially one involving programming . With the help of the Retrospective meeting, you can improve the efficiency of your team on future projects. Additionally, with these review meetings, teams can learn to work more efficiently next time.

These are designed for a number of purposes, such as teaching, finding the wrong, making rights the next time, developing for the next big thing, training, and so on. Therefore, it is important to host your retrospective meeting, keeping some tactics in mind and learning from previous experiences.

As a scrum master, it is your responsibility to hold a review meeting. But, first things first, what is a post meeting? A review meeting will be held to evaluate past work cycle and team progress. The meeting will be held at the end of each round of energy project. It helps in gathering feedback and all aspects of a project, good or bad.

When is a Retrospective Sprint Meeting Held?

First things first and that is a time box, meaning answer the question when will a sprint review meeting be held? In Agile software development, a sprint review meeting takes place at the end of a turn in a review meeting. These meetings are important and should be held after a sprint review; therefore, a sprint review meeting should be held before a meeting is scheduled for the next sprint.

What is a successful review?

An energetic review meeting is considered successful if the team progresses in the next step after the session and receives information, ie flaws and positive points from the sprint meeting. Continuous improvement is an indication of a successful outlook.

A very suitable form of Agile Retrospective:

It usually takes ½ to 1 hour for a review to be completed. Here are the three pillars for a successful review:

Evaluate & Celebrate:

This is important. As a scrum master, you should respect the team for their performance and identify the new client, good product, or feature message. This will help boost team confidence and push them forward.

Discuss barriers:

Review meetings have one purpose, and that is development for the next. These meetings provide an opportunity to resolve previous issues. Following analysis, teams should consider the problems and obstacles they faced in the final sprint and plan for their implementation.


Identify and solve the obstacles facing the sprint.

Suggestions for developing review meetings

Here are some suggestions you can follow to improve your review meetings:

1. Prep, Prep, Prep:

Before you go to that meeting, as a scrum master, you have to examine everything and think. You would not want to go unprepared. There will be questions, answers, and some new ideas to deal with. Therefore, it is important to examine the whole project and then pick up the points that you think should be addressed in order to develop the next one. Make sure you are fair and have an impartial mind in choosing what is wrong with your team.

2. Be urgent but not personal:

Again, you should be ready before you throw some hard truths at your team. As you speak at the meeting, keep an open mind and listen to everyone. See what others have to say about how you lead a project. It’s important to let your team share their feelings about anything that’s bothering them.

3. Share knowledge

Rather than playing the blame, these meetings should be about sharing experiences and learning from them. Of course, people are going to make mistakes; that is stable. However, playing a blame game is unhealthy for a team. So make sure everyone shares thoughtful experiences about development in the next project, rather than blaming someone else.

4. Ask questions

Asking questions is important in any organization. And as a project leader, you have to ask and address these questions. If people in your team are lazy to ask questions, make sure they are comfortable. And if they are afraid to ask questions, you should know that something is not going well. It would be best if you let everyone ask questions. In this way, the door to more creative ideas and problem solving opens. It helps not only in team development but also builds trust across people.

5. What can make things better

Now that you have asked questions about what went wrong and how things should be, plan on doing things better for the next project. Ideas and solutions will initially lead to a successful meeting, but achievement is the most challenging part. Start working on how you can make things better for your next project. How do you deal with a specific client? If there are obstacles, like a scrum master, you need to remove those obstacles.


An overview meeting is important after project activity. Therefore, it is important to pay attention to detail and ask the right questions. Make sure you do this the right way because your next project is up to you.