You can also discuss what commitments your team can make to ensure the next sprint is successful, based on data and observations from your previous sprint. Sandwiching the retrospective between the two, you and your team can most effectively discuss what worked in your previous sprint, as well as what can be improved, while your previous sprint is fresh in your mind. Your sprint retrospective meeting should be held after your sprint review and before the next sprint planning session. When is a sprint retrospective meeting held? What can we do to improve productivity?.What should we stop doing in the next sprint?.What should we start doing in the next sprint?.What did we do wrong in the previous sprint?.What did we do right in the previous sprint?.The meeting is meant to give the Scrum team the opportunity to ask and address questions such as: So what do you discuss in a sprint retrospective? Really anything that affects how the team creates the product is open to scrutiny and discussion, including processes, practices, meetings, environment, and so on.
Simply put, the Scrum retrospective meeting lets you analyze your process in the previous sprint and create a plan for improvements in the next. What is covered in a sprint retrospective? This article includes some fun ideas that you can easily incorporate to run your sprint retrospective meeting more effectively and efficiently. In fact, a good sprint retrospective idea may be to discuss how many meetings the team attends, how long meetings should last, how productive those meetings are, and how you can make meetings more productive. If you’re going to spend a large chunk of your time in meetings, you should always make sure that the meetings you plan-especially one as important as a sprint retrospective-are productive and efficient. If you are a Scrum master or in middle management, it’s possible that you spend up to 50% of your time attending meetings. On average, anywhere from 23% to 37% of your time is spent in meetings.
0 kommentar(er)
