Scrum has a rhythm among its various events. If you’re starting or considering Scrum, you might be asking:
Who attends each of these meetings, and what role do they play?
These Scrum meetings are critical to the success of the Scrum team. So is understanding the role each team member plays. I’ll walk you through how the Scrum team members engage at each Scrum meeting.
Now that we understand who is at each of these meetings let’s look at their role. We’ll walk through each meeting again, primarily looking at the roles of the Product Owner, Scrum Master and Dev Team. I’ll also include Subject Matter Experts and Stakeholders as they show up in some of the meetings.
Development Team: The dev team identifies how much work they can deliver at the end of the sprint. They ask questions and possibly further decomposed features using user stories and acceptance criteria. At the end of the meeting, the development team explains back to the product owner and the scrum master their initial plan for accomplishing the sprint goal.
Scrum Master: The Scrum Master facilitates the meeting, ensuring that questions are answered, and the team gets the clarity they need to begin the sprint.
Product Owner: The product owner defines the sprint goal or objective to provide clarity and priority for the sprint. They then work with the team to move requirements from the product backlog to the sprint backlog, answering questions along the way.
Development Team: Every day for fifteen minutes, the development team inspects the previous day's work, plans the next day’s work and identifies any barriers.
Scrum Master: The scrum master attends and helps the team learn to run the daily scrum, but the meeting is the team’s responsibility, and they are accountable.
Product Owner: Answer any questions or make quick product decisions that come up.
Development Team: Reviews all the Product Backlog Items or PBIs for completeness, asking questions when they need clarity. If a story is too big, they work with the product owner to break it down. The team agrees to the acceptance criteria.
Product Owner: Presents the current backlog explaining and answering questions as needed by the team. If new requirements or stories arise during the meeting, the product owner will decide how to prioritize them in the backlog.
Scrum Master: Observes and helps the team work through the process effectively while keeping the meeting within the time-box.
Subject Matter Experts: Ask and answer questions.
Development Team: The Dev Team presents and demonstrates the completed stories. The team also shares what went well during the sprint and what obstacles they encountered. They receive feedback from stakeholders and answer questions as needed.
Scrum Master: Attends to hear feedback from stakeholders and ensures the meeting goes as planned.
Product Owner: Invites the stakeholders to the meeting and facilitates the discussion. They review the state of the backlog.
Stakeholders: Ask questions and give feedback.
Development Team: The entire Scrum team inspects the last sprint regarding people, relationships, processes, and tools. You want to consider how to improve what went well and mitigate what was difficult. Take these insights and create a plan to improve how the scrum team is working.
Product Owner: Contributes to evaluating how the whole team worked together during the sprint. Suppose any changes the team decides on require additional work (like learning a new skill or fixing a broken process). In that case, the product owner should add an internal user story to the backlog to represent that work in a future sprint.
Scrum Master: Facilitates the meeting while also contributing to evaluating how things went and what might need to be changed.
Scrum has a lot of meetings and it can be hard to keep them straight, especially when you're getting started.
The Scrum meeting checklist has all the details you need to run effective Scrum meetings.