Sprint Planning

Attendees

• Scrum Team(s), Product Owner.
• Business stakeholder(s) might attend as needed.

Objectives

• Review the project backlog and plan the work to be completed in the upcoming sprint.

Guidelines

• Most of the backlog grooming be completed separately, in advance of the sprint planning.

Sprint Demo

Attendees and Audience

• Scrum team(s), along with business users and business stakeholders.
• The primary target for sprint demos is business users and stakeholders.
• The secondary target is other team members.

Objectives of Sprint Demos

• Review and present the work completed in the previous sprint cycle, from an end-user perspective.
• Present an overview of the stories and functionality that was completed in the previous sprint cycle, in order to solicit and capture feedback on what was completed in the previous sprint cycle.
• Present an overview of the goals for the next sprint cycle.
• Foster conversation and communication between the scrum team and the end users and business stakeholders.

Guidelines

• Technical feedback should be saved for the Sprint Retrospectives.
• Demo focuses on functionality that is done (meets definition of done). We don’t present functionality that is in progress.
• Demo complete stories.
• Demo functionality that provides value to the end users.

Sprint Retrospective

Retrospectives might be one of the most critical aspects of Scrum.

Scrum retrospectives are meetings that are held at the end of each sprint in the Scrum framework. The purpose of these meetings is to reflect on the previous sprint and identify areas for improvement. The goal is to continuously improve the team's processes and workflow, and to identify and address any obstacles or challenges that the team may have faced during the sprint.

Retrospectives are a key part of the Scrum process because they provide an opportunity for the team to come together and identify ways to improve their work. By regularly reviewing and adapting their processes, teams can become more efficient and effective, which ultimately leads to better results.

Retrospectives also allow team members to share their thoughts and ideas, and to collaborate on solutions to any issues that may have arisen. This can help to build team cohesion and create a sense of ownership and responsibility among team members.

Attendees and Audience

• Scrum Team.

Objectives

• Review the work done in the previous sprint.

Guidelines

• Complete the Sprint Demo before the Retrospective so that feedback from the Sprint Demo can be reviewed at the Retrospective if needed.

Daily Standups

• What did you do last (yesterday)?
• What are you doing next (today/tomorrow)?
• Are there any roadblocks (issues)?

Attendees and Audience

• Scrum team.

Objectives

• Each team member reports (1) work completed yesterday, (2) work to be done today, and (3) any roadblocks they are facing.

Guidelines

• The scrum master needs to maintain the flow of the meeting and keep it on target.
• The scrum master is responsible for following up on any roadblocks or delegating this to another team member.
• Daily standups are generally done with the team members talking to one another, however, if team members are unable to attend, or the scrum team is large, team members may provide short written summaries of their three points in advance in order to help streamline the standup.

References

• https://www.commitstrip.com/en/2020/10/01/daily-meeting/
• https://dev.acquia.com/blog/how-to-give-a-great-agilescrum-sprint-demo/09/08/2018/19771
• https://reqtest.com/development/how-to-succeed-at-a-sprint-demo/
• https://www.atlassian.com/agile/scrum/ceremonies
• https://www.easyagile.com/blog/agile-ceremonies/