SPRINT RETROSPECTIVE

An experienced Scrum team may have completed many successful projects. It may also be implementing Scrum effectively. The team might be perfect from every point of view. However, Scrum principles suggest there is always a scope of improving upon the work process to make it even better, and even more efficient. The “inspect” and “adapt” principles help to generate inputs that are very important in the improvement process. Scrum dedicates a special event to support these principles. The event is called sprint retrospective meeting. Some experts also refer to the meeting as a Scrum retrospective.

A sprint retrospective can be thought about as a “lessons learned” type of meeting. During the meeting, the team thinks about how everything worked out in the sprint just completed. It tries to retrospect and evaluate the outcomes of the sprint. The event is team driven and the entire team participates in it. The team decides how the retrospective should be held and how it should proceed. A healthy atmosphere fostering trust and sharing of ideas should ideally prevail in the meeting. The members should feel comfortable while contributing their ideas and sharing them with other team members. Senior team members should lead by example and help new joiners understand the scrum process and how the objectives of holding a retrospective can be best fulfilled.     

Scrum retrospective – When, Who, and For how long

The retrospective is the last event to be held in a sprint cycle. It is conducted just after a sprint review event finishes. The entire Scrum team, including the product owner and the scrum master should ideally attend the meeting. The sprint retrospective should generally last for three hours but it can be extended if required. At times, discussions .  read more at  https://goo.gl/L2DaNu