Retrospectives are the primary learning, reflection and readjustment techniques on agile projects. A retrospective is a special meeting that takes place after every sprint in which the team members gather to inspect how the sprint went and what are the areas of improvements? Retrospective is one of the events that is specifically aimed at the “inspect and adapt” behavior of the team. The Scrum retrospective ceremony is a platform that gives team members an opportunity to reflect, see how they worked together, and discuss how they can become more efficient in the coming sprints.

The key to scrum team effectiveness is continuous improvement that can be realized through the inspect & adapt opportunity, the retrospectives. Retrospectives help the teams to inspect on their strengths and weaknesses and come up with some strategies to become stronger each sprint.

R-> Realize where you are and where you want to be

E-> Engage the teams in fruitful discussions

T-> Team work to build “We over I” attitude

R-> Relish the power of Inspect and Adapt cycles

O->Openness and Transparency make retrospective efficient and effective


Back stage of retrospectives:

Retrospective is not any new concept or jargon the team needs to master — but yes, in reality it becomes challenging to keep the momentum lively at all times in few cases! After the teams do many sprints, teams start complaining that they are losing interesting in the retrospective as it is losing its effectiveness. So this triggers a need to do something differently to break the usual norms so that these reflections could be made thought-provoking ones!

R-> Repeated issues pop-up

E-> Engrossing & Engaging discussions are missing

T-> Team present virtually, loses trust.

R-> Routine stuff, nothing interests the teams.

O->Observably gets boring over time.