If you just joined your first agile team, the calendar is probably full of meetings you have never heard of. Sprint Planning, Daily Standup, Sprint Review, Retrospective — each one has a specific purpose, a defined group of participants, and an expected outcome. Here is exactly what happens in each one.
Sprint Planning
What it is: The ceremony that kicks off every sprint. The team decides together what they will build in the next one to two weeks. Who attends: Product Owner, Scrum Master, and the full development team. Duration: Two to four hours for a two-week sprint (scale down proportionally for shorter sprints). What happens: The Product Owner presents the top items from the backlog. The team discusses each item, asks clarifying questions, and estimates the effort involved. The team then commits to a sprint goal and pulls in enough backlog items to fill the sprint without overloading. Outcome: A committed sprint backlog — the specific list of work the team has agreed to complete by the end of the sprint.
Daily Standup
What it is: A brief daily synchronization meeting to keep the team aligned and surface blockers early. Who attends: The development team and Scrum Master. The Product Owner may attend but is not required to. Duration: Fifteen minutes maximum — strictly enforced. What happens: Each team member answers three questions: What did I complete since the last standup? What am I working on today? Is anything blocking me? The standup is not a status report to the Scrum Master — it is a synchronization point for the team. Detailed problem-solving happens after the standup, not during it. Outcome: The team leaves knowing what everyone is working on and which blockers need to be resolved before they slow anyone down.
Sprint Review
What it is: A demonstration of what the team built during the sprint, open to stakeholders and anyone interested in the product. Who attends: The full team plus stakeholders — this might include the product leadership, sales, customer success, or customers themselves. Duration: One to two hours for a two-week sprint. What happens: The team demos the working software they completed during the sprint. There are no slide decks — the demo is the product itself. Stakeholders ask questions and give feedback. The Product Owner clarifies what was completed and what was not, and why. Outcome: Stakeholder feedback that feeds back into the backlog, and a shared understanding of what was delivered.
Sprint Retrospective
What it is: The team's private reflection on how the sprint went — not what was built, but how the team worked together. Who attends: The development team and Scrum Master. The Product Owner may attend depending on team norms. Duration: One to one and a half hours. What happens: The team discusses three questions: What went well and should continue? What did not go well and should change? What should we try next sprint? The Scrum Master facilitates but does not dominate — psychological safety is essential for a retro to be honest. Outcome: One to three specific, actionable improvements the team commits to trying in the next sprint. Not a laundry list — a short, focused set of experiments.
A note for Scrum Masters
Your job in every ceremony is to make the ceremony valuable, not just on schedule. A standup that runs fifteen minutes but leaves blockers unidentified has failed. A retro that surfaces honest problems but produces no commitments has also failed. The ceremony is the container — what the team does inside it is what matters. To go deeper on the Scrum Master role and how to land your first position, visit the Scrum Master track on NewRoleKit.