Sprint retrospective is an opportunity for the scrum team to calibrate themself. The sprint retrospective is a recurring meeting held after the sprint to know what they did well.

Isn’t it simple to understand? But it took me plenty of patience to return to a current conclusion. As various terms were springing up in my head while staring at it, like

Are sprint review and sprint retrospective the same?

Is it a scrum or a strategy in scrum?

So today I’ll share the details of the sprint retrospect to make you to understand how simple and effective it’s for your business.

As you must know scrum is an agile framework. We can say Sprint Retrospective is an element of a scrum team. Sprint Retrospective is a vital part of difficult projects as it helps to develop, deliver, and manage such projects.

Attendees of sprint retrospective
It is held by scrum master after sprint review and before sprint planning. A whole development team and product owner attend this meeting.

Duration
If the retrospective meeting is for a week, then it should be for 45 minutes. So, the rule generally goes as
180min (3hrs.)- a month
135min (2.25 hrs.)- 3 weeks
90min (1.5hrs.)- 2 weeks
45min -1week

Retrospective is conducted in 5 simple stages:

Set the stage– State the agenda you need to figure out. Involve members into the proper mood.

Gather information– Create a picture using everyone’s perspective and experience. Collect the data.

Generate insight-View a wider picture from gathered information. Reason out the causes.

Decide further steps– Plan for further action including an obstacle you need to face.

Pack up retrospective– Summarize the meeting, appreciate members, and collect ideas to improvise further sprint retrospectives.

Isn’t it a simple thing to do?

So, let’s see further why it’s effective by knowing its purpose in a scrum.

You cannot grow without knowing your positives and negatives, retrospective focuses mainly on those basic three things which improve team and projects success.

What went well

In retrospect, the team discusses a radical idea about what went well during a sprint by knowing
● What motivates the team,
● What we did differently to achieve success
● Which skills help to attend success
● What are team member’s and team’s positive points resulting in success?

What doesn’t go well?

As positive’s, we also have to discuss negatives. For that, a team should discuss answers to questions
● What went wrong and what are the causes to make it happen.
● Did we know prior about the consequences of our actions?
● Did we understand before implementing it?

What we attempt to improve further

Knowing all the positives and negatives, the team should learn from them and discuss what to try again and what to do differently by creating a closed planned concept for the future.

The sprint retrospective is a “lesson learned” together with providing ownership to each member simply and effectively making it truly Agile and successful.