Sprint Retrospective
If the Sprint Review is for inspecting the product increment, the Sprint Retrospective is for inspecting the team processes. Here, the team discusses what went well, what went wrong, and what can be improved. Task management can be a common theme, and there are many creative ways to make a Sprint Retrospective bring out process improvements. As the Scrum Master, you can set up the context and prime directive for this ceremony in such a way that the team can ideate on how they can be better or be more confident with task ownership. Have the team analyze their inputs and come up with the action items for them to commit to.
The Daily Standup
A quick 15-minute meeting, the Daily Standup is where each team member discusses what they’ve finished so far, what they commit to doing for the day, and what help they need or what problems they’re having. This is not a problem-solving meeting; rather, this is simply for team members to hear each other on where they are in the Sprint.
Product Backlog Prioritisation
Product Backlog Prioritisation is similar to a Sprint Planning, except the team is planning for future Sprints and releases. Here, the Product Owner and the development team talk through PBIs that have not yet been discussed. The desired functionality is made clear, acceptance criteria are declared, and efforts for completing the PBIs in terms of time and/or complexity are estimated. It would be better if tasks for the PBIs are also identified during this session. Holding regular Product Backlog refinement sessions is a practice that can save the team time during Sprint Planning, and can give everyone a better idea of where the project will be heading to next.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: