Scrum meetings explained: the four, and what each is for

Scrum has four recurring meetings inside the sprint — the Scrum Guide counts the sprint itself as a fifth event, being the container the other four sit in — and each of the four answers a different question, which is the only reason there are four. Planning asks what we are committing to. The daily scrum asks what needs to change today. The review asks whether what we built is any good. The retrospective asks how the working is going. When a team complains about scrum, it is almost always because two of the four have collapsed into each other — usually the daily into a status report, and the review into a demo nobody is allowed to criticise.

The four, and how each one fails

Times are for a two-week sprint. The failure mode listed against each is the one to watch for, because all four degrade in the same direction: towards a meeting where people report to someone.

Sprint planning — up to 4 hours

Question: what are we committing to, and do we believe it? Shape: the goal first in one sentence, then the items, then an honest look at capacity including the leave, the on-call and the thing everyone forgot. Fails when it becomes an estimation ritual — hours argued over items nobody has looked at properly, producing a number that is wrong and now official.

Daily scrum — 15 minutes

Question: what needs to change today? Shape: walk the board from nearest-done backwards, blockers stated as a named ask. Fails when it becomes a status report to the lead. The tell is that answers are addressed to one person, and that people report on days they were on leave. See our standup format for the fix.

Sprint review — up to 2 hours

Question: is what we built any good? Shape: show working software to people who use it, and invite criticism explicitly. Fails when it becomes a demo — a polished walkthrough for stakeholders who are there to approve rather than react. A review where nothing is criticised has told you nothing, and it usually means the wrong people are in the room.

Retrospective — up to 90 minutes

Question: how is the working going? Shape: silent writing first, then discussion, then at most two changes with owners. Fails when agreed changes do not happen, which trains the team to give safe answers. Open every retro by reviewing the last one’s commitments — the questions page has the rest.

Backlog refinement — the unofficial fifth

Not one of the four in most descriptions, and most teams need it anyway: a standing slot to make the next sprint’s items ready. Skipping it does not save the time, it moves it into planning, where it makes planning long and bad-tempered.

The honest question about all of this

Scrum is a set of defaults, not a law. A team that genuinely inspects and adapts will end up somewhere slightly different from the book and that is the intended outcome. A team that has kept all four meetings and stopped changing anything as a result is paying the full cost of the framework and collecting none of it.

What actually goes wrong

Almost never the framework. Usually: a product owner who is not available, a definition of done that is aspirational, and commitments that are set by someone who is not doing the work. None of those are fixed by a better-run meeting, and all of them will be blamed on the meetings.

Questions

What are the four scrum meetings?

Sprint planning, the daily scrum, the sprint review and the sprint retrospective. Each answers a different question — what we are committing to, what needs to change today, whether the work is any good, and how the working is going.

How long should scrum meetings be?

For a two-week sprint: planning up to four hours, daily fifteen minutes, review up to two hours, retrospective up to ninety minutes. These are the Scrum Guide’s upper bounds scaled to a fortnight, not targets — finishing early is normal and is not a sign anything was skipped.

What is the difference between a sprint review and a retrospective?

The review is about the product — is what we built any good. The retrospective is about the process — how is the working going. Merging them means the harder conversation, usually the retrospective, gets skipped.

Is backlog refinement a scrum meeting?

It is not usually listed as one of the four, and most teams need a standing slot for it anyway. Skipping it does not save the time; it relocates it into sprint planning and makes planning worse.

Why do people dislike scrum meetings?

Usually because two of the four have collapsed into each other — most often the daily becoming a status report. The complaint is about the meeting; the cause is generally an unavailable product owner or commitments set by people not doing the work.

Can you do scrum without all four meetings?

Teams do, and some work well. The test is whether the question each meeting answers is still being answered somewhere. Dropping the retrospective usually means nothing changes any more, which is the one to be most careful about.

Who runs scrum meetings?

The scrum master facilitates rather than chairs, and the daily is the team’s meeting rather than anyone’s report. The distinction sounds pedantic and is the difference between the meeting working and not.

How long should a sprint be?

One or two weeks for most teams. Longer sprints delay the feedback the whole arrangement exists to produce; shorter ones spend too much of the time in the four meetings.

Nothing here needs a product, and we do not sell project management software. The one place capture matters is the review and the retrospective, where the useful material arrives while the person running the session has no hands free to write it down.