Agile Meetings

I broke this down in the video above. Below is the written version, expanded into a fuller guide to the four meetings that run an agile team and what each one is for.

Agile meetings are where the work actually gets coordinated, and there are four basic types that every agile team runs. If you are new to agile or trying to explain the ceremonies to someone, this one is for you. The four are the daily standup, sprint planning, backlog grooming, and the sprint retrospective. Each has a different purpose, a different length, and a different person leading it. In the video I walked through all four at a high level, and here I want to lay them out so you can see how they fit together across a sprint. Think of this as the map, with deeper guides on the individual ceremonies linked along the way.

The daily standup

The daily standup is a fifteen-minute meeting where each person answers three questions, led by the scrum master.

The daily standup is the most popular meeting on the list, and the shortest. It should last no more than fifteen minutes. Each person answers three basic questions: what did you do yesterday, what do you plan to do today, and do you have any blockers. The scrum master typically leads it.

The fifteen-minute limit is the whole point. The standup exists to surface progress and blockers fast, not to solve problems in the room. What I learned running these is that the moment a standup turns into a working session, it loses its value and starts eating the team’s morning. Keep it short, capture the blockers, and take the deep conversations offline.

Sprint planning

Sprint planning is a one to two hour meeting where the team decides which stories and tasks to take into the sprint.

Sprint planning usually lasts anywhere from one to two hours. The goal is to figure out which stories and activities need to be done during the sprint. You pull in additional information from the product owner, settle on the stories you want, look at the specific tasks, and begin assigning those tasks before the sprint starts. The scrum master usually leads this one too.

I cover the full mechanics in the video. The key idea at this level is that planning turns a prioritized backlog into a concrete commitment for the next few weeks. Done well, the team leaves knowing exactly what it signed up for.

Backlog grooming

Backlog grooming is a weekly hour, led by the product owner, where the team reviews and estimates upcoming work.

Backlog grooming usually takes about an hour, and it is led by the product owner rather than the scrum master. What we do is hold one grooming session every week, so we are always looking ahead at the work the team will need to do. We estimate at a high level how much work each item will take, expressed in points.

The weekly rhythm is deliberate. We run grooming once a week so the backlog never falls too far behind, which keeps sprint planning smooth instead of painful. Grooming is the meeting that feeds planning, and a healthy backlog is what makes the rest of the ceremonies work.

The sprint retrospective

The retrospective reviews what went well and what can be improved, led by the scrum master, with a focus on only one or two improvements.

The fourth meeting is the sprint retrospective. The team addresses what went well and what can be improved, and the scrum master usually leads it. The most important rule is restraint. For what can be improved, you really want to focus on only one or two things.

I stress this in the video. Pile on more than that and the team gets overwhelmed and ends up doing nothing well. What I learned is that if you improve one thing well this sprint, another the next, and so on, the team steadily gets better, feels more accomplished, and stays motivated. Small, focused improvement beats a long list every time.

The takeaway

The four agile meetings each do one job. The daily standup keeps everyone aligned in fifteen minutes. Sprint planning turns the backlog into a committed plan. Backlog grooming keeps that backlog healthy a week at a time. And the retrospective drives steady improvement, one or two items at a time. Run all four with discipline and they reinforce each other, which is what keeps an agile team moving instead of just busy.

If this helped, the full overview is in my video on agile meetings, and I have deeper videos on each ceremony. Here is my question for the comments: which of the four meetings does your team struggle with most? Subscribe if you want more practical agile guidance.