The sprint retrospective is held at the end of a sprint to review what went well during the previous sprint and what can be improved for the next sprint. 

Purpose of a sprint retrospective 

The sprint retrospective is a timeboxed meeting that is held after the sprint review and before sprint planning for the next iteration. 

The sprint retrospective meeting helps in the below ways: 

To examine how the previous spring completed went and what can be DONE to improve the deliveries in the next sprint. 

1. Identify and prioritize the TASKS that went well. 
2. Identify and prioritize the tasks that didn’t go well. 
3. Identify possible amendments. 

Scrum retrospective helps Scrum team members to classify how they can improve to contribute better to the sprint. The team would ask questions themselves like what work has been done well in this sprint? What work hasn’t been done well? What should we start doing to improve? The development team then focuses on improving quality by improving work processes or adapting the definition of “done.”  

Sprint Retrospective Audience 

It usually includes development team members, the Scrum Master, and the PRODUCT owner. The Scrum Master conducts the meeting and assists the development team to enhance its workflow practices within the process framework for the next sprint.  

Stakeholders and managers who are not directly part of the team usually don’t come to a Scrum retrospective UNLESS they are invited. They engage in the sprint review meeting where the scrum team reveals what they have ACHIEVED and accomplished during the sprint through product demos.