It is essential to run the sprint retrospective meeting in an open and relaxed environment to encourage the active participation of all team members.Īs a moderator, the scrum master will set the ground rules, explain the meeting goals and ask the team members to come prepared. How to Run a Sprint Retrospective Meeting However, these members can participate in sprint review meetings to verify the acceptance criteria and see the product demos. Some stakeholders and managers don’t join the sprint retrospective meetings unless specifically invited when there are specific agenda points that need to be discussed with them. Subsequently, the causes of deviations will be discussed in the sprint retrospective meeting. If they find deviations, the scrum master and the team will take corrective action and fix the deliverable. The scrum master also checks the quality standards of the product. All team members will have perspectives on how the past sprint went and share their experiences to improve the quality of the product. One team member acts as the scribe and documents the discussion and items for future action. Product owner presence is optional but recommended. The scrum master facilitates the sprint retrospective meeting. Who Runs the Sprint Retrospective Meeting? Sprint Retrospective Templateīelow is an example of a sprint retrospective template. The scrum master ensures the scrum team improves its quality and effectiveness and creates an enjoyable environment for the team to work in the next sprint. Some action items might be added to the sprint backlog for the next sprint. The most impactful improvements are addressed as soon as possible. The scrum team identifies the solutions to improve the product quality. The scrum master facilitates the retrospective meeting and discusses what went well and what didn’t during the previous sprint, whether they encountered problems, etc. The team members must have a common understanding of “done” to decide if the deliverable is completed and meets requirements. The Definition of Done might vary from scrum team to scrum team. The scrum team inspects how the last sprint went regarding individuals, interactions, processes, tools, and their Definition of Done, etc. The sprint retrospective meeting aims to develop plans to improve quality and effectiveness. What is the Purpose of a Sprint Retrospective Meeting? If an action item for the risk is discussed during the retrospective meeting, the scrum master will update the risk register and the risk backlog. The scrum master will also update the lessons-learned document. These items are added to the prioritized product backlog whenever they are discovered. Usually, non-functional requirements (e.g., response time) are not completely clarified at the beginning of the project and can surface during the sprint retrospective meeting. Each action item will have an assignee and due dates for the scrum master follow-up. The output of the meeting will have a list of actionable items that need to be addressed, including process improvement suggestions for future sprints.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |