![]() Document and publish the findings or meeting minutes in the end so that there a record of findings.Ensure the learning is included in the sprint planning meeting and agile project plans.The retrospective meeting is not the place for airing grievances or discussing processes that the team has no power to change. The agenda should focus only on processes or procedures that the team can decide to start doing, continue doing, or stop doing. The meeting should include discussion only of issues over which the team has control. Any discussions relevant only to particular team members should be conducted in private outside the retrospective meeting. The meeting should include a discussion of topics and processes relevant to all team members, regardless of their roles or their individual expertise. Ask team members to reflect and contribute feedback to improve processes and future sprints. No one person should drive the agenda or dominate the meeting, and each team member should feel safe in bringing up any issue that he or she feels is significant. Use this retrospective template at the end of your team sprint. The ScrumMaster may facilitate the meeting, but it should be a group effort that encourages participation from all team members. If individual team members have concerns or issues that they wish to discuss with ScrumMaster, those issues should be discussed in private afterward, not during the meeting. Ideally, the retrospective meeting should not last more than an hour, and its discussions should remain tightly focused on team goals. A Sprint Retrospective is not a one-off nor a continuous event but a ritual: while traditional Lessons Learned meetings tend to be held just at the end of the project or captured throughout the project in a Lessons Log, a Sprint Retrospective perceives this event as a so-looking-forward-for-it ritual, a moment of celebration and reflection that marks the end of each sprint.Also, given that the team's capacity is limited, improvements are prioritized by the Scrum Master so that the team can focus on the actions that matter the most for the next sprint. Instead of going through all potential and imaginable improvements since the project started, a Sprint Retrospective focuses only on identifying improvements from the finishing sprint. ![]()
0 Comments
Leave a Reply. |