He allows enough room for each team member to bring in ideas and retrospect. The scrum master ensures full-scale participation of the concerned team members. However, he holds no authority to make desired changes in the scrum process but only those which are discussed and agreed upon. The meeting cannot take place in his absence. Scrum master acts as the head of the sprint retrospective meeting and authorizes the scum team. If he does not attend, the scrum master can later brief him on any changed course.
Sprint retrospective sample answers free#
The product owner can be a significant part of this meeting however, he is free to choose whether he wants to attend or not. Here’s what makes your spin retrospective meeting team complete: Product Owner To ensure that your scrum team does not lose any magic and sprint retrospective meeting goes successfully, here are some sprint retrospective meeting best practices to follow: Everything that plays a role in the creation and development of the product, such as tools, processes, and environment, is open for questions, investigation, and discussion. It helps evaluate the results of the sprint review meeting and prepare for the sprint planning meeting.ĭuring the sprint retrospective meeting, the team has a good opportunity to improve their working and designing a plan of action to incorporate the improvements. Sprint retrospective acts as a middle step, taking place after sprint review and before sprint planning. The purpose of this meeting is to figure out what went well, what could have been improved, and what actions can be taken to do so. Only the scrum team members, such as the product owner, development team, and scrum master, attend this meeting. At the end of every sprint review meeting, the scrum teams hold a sprint retrospective meeting.