Sprint Retrospective Meeting

100% helpful
(1/1)

After the Sprint Review meeting, schedule and run a Sprint Retrospective. This meeting of the Scrum team and project sponsor can be held right after the Sprint Review, after stakeholders, management and project teams have left. First, adjust the sprint backlog is adjusted redistribute the sprints if estimates were off. Second, review how the team process is working.

Sprint Backlog. The project sponsor determines which user stories are considered complete. The Scrum Master returns incomplete user stories to the Product Backlog (Master bucket). Next, the Scrum team, Project Sponsor and stakeholders add any new user stories to the Product Backlog and Manage the Buckets!

Review how close your estimate of time to complete medium user stories was to the actual time they took to build. If the numbers are not close, update the sprint plan.

Note – during the review meeting that follows sprint two, the customer begins to see all of the potential of the Anaplan platform. They want everything and they want it now. Manage their expectations and always, the buckets!

Team process. After reviewing the sprint backlog and adjusting the sprint schedule, focus on the team process. How well is the team working together? In addition to checking in on team ground rules, ask some additional questions to generate discussion:

What did we do well?

Did we miss any opportunities to collaborate?

What are our team’s strengths / weaknesses?

Do we have the right people in the right roles?

These discussions bring areas that need improvement to light. Then, the customer is empowered to make decisions about what to do differently to improve. Are the ground rules in need of an update? Have some behaviors improved? Recognize the good changes and work on eliminating the behaviors that get in the way.