![sprint retrospective meeting sprint retrospective meeting](https://1m9qrs2s997uox6846iotvmx-wpengine.netdna-ssl.com/wp-content/uploads/2018/04/5.jpg)
Each team member must provide feedback for every question, if they can. There are three open-ended, existential questions that make up a sprint retrospective. Rather than focusing on details of the project, this Scrum ceremony is to examine the team’s work styles and what areas they can improve in. The purpose of a retrospective is quite different from a review. Thankfully, the retrospective meetings are shorter, usually lasting between 30 minutes and 3 hours. Those who should be at the meeting include the Scrum master, product owner, and the Scrum team.
![sprint retrospective meeting sprint retrospective meeting](https://www.projectcubicle.com/wp-content/uploads/2019/05/Sprint-Retrospective-Meeting-in-Scrum.png)
What is a sprint retrospective?Īs a part of the sprint cycle, sprint retrospective meeting also takes place between sprints, but it always comes after the sprint review. Read more on this process in the “ Epic, Story, and Tasks in Agile” article. The team uses different backlog prioritization techniques to achieve that. The product owner and Scrum Master add or remove user stories, and reprioritize the backlog items before choosing what the team will work on in the next sprint. This step is crucial because it provides structure and organization to the remaining increments that are to be completed.
#Sprint retrospective meeting update#
Once the stakeholders discussion is over, it’s time to update the backlog.
#Sprint retrospective meeting free#
The stakeholders, after seeing all the finished increments, are free to ask questions or provide feedback about the progress so far. Only increments that are ready to be released or implemented into the overall product are presented. During this portion of the meeting, the developers or the product owner will present all the tasks the team completed during the sprint.