Agile Scrum ceremonies: 4 events + backlog refinement

Traditional ceremonies mark key milestones, from graduations to weddings. Agile ceremonies borrow from this concept, but rather than celebrations, they serve as consistent checkpoints throughout your project's lifecycle to keep your team aligned and moving forward.

What is an Agile ceremony?

An Agile ceremony is a structured meeting where your team aligns on priorities, reviews progress, and plans the next steps in the Agile process. The four main ceremonies are sprint planning, daily stand-up, sprint review, and sprint retrospective. These ceremonies are typically facilitated by product owners or Scrum masters to keep Scrum teams focused and aligned.

Before each ceremony takes place, all team members should have a clear meeting agenda and know this key information:

• Who on the development team is involved in this ceremony?

• When does this ceremony begin?

• How long does this ceremony take?

• What happens in this ceremony?

• What is the expected outcome?

What is a sprint?

A sprint is a fixed period of time during which a team works toward specific deliverables. Sprints typically last two weeks and are a core component of Agile project management frameworks, which are commonly used by product, engineering, or software development teams. Working in sprints gives teams an opportunity to iterate and continuously improve their processes, because when a sprint ends, the team records and incorporates their learnings into the next sprint.

Below, we'll dive further into the four main Agile ceremonies and explain how to answer each question.

Why Agile ceremonies matter

Agile ceremonies are essential touchpoints that keep your team aligned, focused, and moving in the same direction. Here's why they're valuable:

• Foster transparency: Ceremonies create regular opportunities for team members to share progress, challenges, and insights with one another.

• Drive alignment: By meeting consistently throughout the sprint, everyone stays connected to the team's goals and priorities.

• Enable continuous improvement: Retrospectives and reviews give your team dedicated time to reflect on what's working and what needs to change.

• Reduce miscommunication: Frequent check-ins help catch misunderstandings early, before they derail your sprint.

When done well, Agile ceremonies transform how your team collaborates, turning scattered efforts into coordinated progress and driving team effectiveness.

What are the 4 Agile ceremonies?

There are four major Agile ceremonies that happen during every sprint cycle. Before starting each ceremony, your team members should understand the purpose of each meeting and how it impacts the sprint.

1. The sprint planning meeting

The sprint planning meeting is when the development team plans out what work will be completed during the upcoming sprint.

• Who's involved? The development team, Scrum master (if your team is using Scrum), or the product owner.

• When does this ceremony happen? At the beginning of each sprint.

• How long does this ceremony take? Approximately one hour per week of work. If your sprints typically last two weeks, sprint planning should take approximately two hours.

• What framework is this ceremony commonly used in? The sprint planning meeting is used in both the Scrum and Kanban methodologies. Most Agile methodologies have some form of sprint planning, even if there isn't a whole dedicated ceremony for it.

• What happens in this meeting? The product owner or Scrum master works with the development team to identify items the team will focus on for the current sprint goals. These items are traditionally pulled from the product backlog. During Scrum, the team assigns story point estimates to tasks to gauge how long each backlog item will take to complete.

• What is the expected outcome of this ceremony? By the end of the sprint planning meeting, everyone on the development team should know the sprint's end goal and which specific items will go into the sprint backlog.

2. The daily stand-up meeting

The daily stand-up meeting is a development team meeting to update fellow team members on what they're working on.

• Who's involved? The development team, Scrum master (if applicable), and the product owner.

• When does this ceremony happen? Once per day, typically at the very beginning of the workday, before everyone can dive into their tasks.

• How long does this ceremony take? Approximately 15 minutes. Daily standups should be very quick and shouldn't require booking a conference room or sharing your screen.

• What framework is this ceremony commonly used in? Most Agile frameworks include a daily standup meeting so teams can easily check in with each other on what they're working on for the day.

• What happens in this meeting? Everyone on the development team, including the product owner and Scrum master, discusses three main points: what they completed yesterday, what they're working on today, and any blockers in their way.

• What is the expected outcome of this ceremony? The intended goal here is for everyone on the development team to touch base. If someone on the development team has a blocker, the Scrum master or product owner will work with that developer. This happens after the meeting to prevent the daily stand-up meeting from becoming too long.

3. The sprint review meeting

The sprint review meeting is an opportunity for the development team to receive feedback from key project stakeholders. If adjustments are needed, the Scrum master or product manager will update the sprint backlog for the next sprint.

• Who's involved? The development team, Scrum master, and product owner are all required to attend this meeting. Key stakeholders, such as management or end customers, are also present during this meeting to provide feedback.

• When does this ceremony happen? This ceremony takes place at the end of the sprint, after all tasks are completed but before the sprint retrospective.

• How long does this ceremony take? Similar to sprint planning, this meeting should last about an hour for every week the sprint lasts. If you have a two-week sprint, you will have roughly a two-hour meeting.

• What framework is this ceremony commonly used in? This framework is used in both Scrum and Kanban methods. In Kanban and other Agile methods, reviews may occur at the end of a project rather than at the end of a sprint.

• What happens in this meeting? The goal of this meeting is to receive feedback on the development team's work during this sprint. The Scrum master or product owner organizes the meeting, showcases the team's completed work, and facilitates questions from external stakeholders who are not on the development team.

• What is the expected outcome of this ceremony? This ceremony is an opportunity for both internal and, if necessary, external stakeholders to give feedback and ask questions about the end product. You may want to call external stakeholders if you're an agency developing something for a client. The Scrum master may use this opportunity to work with stakeholders to determine whether the product backlog needs adjustment.

4. The sprint retrospective meeting

The sprint retrospective meeting is an opportunity for team members to reflect on the past sprint and think about what went well and what could be improved for next time.

• Who's involved? The development team, Scrum master, or product owner. Anybody who actively worked on tasks throughout the sprint should attend this meeting.

• When does this ceremony happen? This happens at the very end of a sprint, after a sprint review meeting.

• How long does this ceremony take? This meeting should take about 45 minutes per week for the sprint to last. If you have a two-week sprint, your sprint retrospective meeting should last about an hour and a half.

• What framework is this ceremony commonly used in? Retrospectives are commonly used in Scrum and Kanban. Teams that use Kanban may hold retrospectives at the end of each project, rather than at the end of each sprint.

• What happens in this meeting? This is when the development team takes some time to look at the team's progress this sprint. The team reflects on what went well and what they can do better for future sprints.

• What is the expected outcome of this ceremony? The goal of this ceremony is to identify key points for iteration. If team members identify something to change or improve for the upcoming sprint, they should share it with the entire team. Some Agile methodologies rely on continuous improvement and process improvement methodologies, and retrospectives are an integral part of that process.

What about backlog refinement?

Many teams refer to five Scrum ceremonies rather than four because they include backlog refinement (also called backlog grooming). While it's not officially listed in the Scrum Guide, it's widely practiced and keeps your product backlog organized and ready for upcoming sprints.

During backlog refinement, the product owner and development team:

• Review and clarify backlog items

• Break down large items into smaller, more manageable tasks

• Add details, estimates, and acceptance criteria

• Re-prioritize items based on new information or changing goals

Most teams hold backlog refinement once or twice per sprint for about an hour. This helps sprint planning run more smoothly because the team arrives with a well-prepared backlog.

Tips for Agile ceremonies

Agile ceremonies are just a fancier way of naming meetings. Follow a few of these tips to keep your meetings running more smoothly.

Assign user stories for all sprint backlog items

A user story is a short description of how a product should function, written from the end user's perspective. Every item in your sprint backlog should have one attached.

User stories help your team by:

• Providing context: Developers understand why they're building something a certain way.

• Speeding up ceremonies: Team members don't have to track down information; they can focus on identifying dependencies.

Before sprint planning, the Scrum master or product owner should review the product backlog and ensure each item includes sufficient contextual information.

Hold your Agile ceremonies at the same time every sprint

Daily stand-ups are easy to remember because they happen every day. Apply this same concept to your other ceremonies by scheduling them at the same point in every sprint.

For example, hold your sprint retrospective every other Thursday. As your team runs more sprints, ceremonies will become second nature.

Make sure the right people are included

If you notice your meetings are starting to get bogged down, evaluate who is attending. Are the people currently sitting in the room the people who need to be there? Having more people than necessary in a meeting can slow productivity, so bring only the team members needed for that specific ceremony.

Coordinate Agile ceremonies with work management software

Keep your ceremonies and Agile team organized by using work management software like Asana. A work management tool gives your entire team a centralized place to see notes for the daily Scrum meeting, backlog items, and information about the next sprint. Get started and see how Asana can help your team run more effective ceremonies.

Frequently asked questions about Agile Scrum ceremonies