Scrum events are not ceremonies you attend to prove you are Agile. Each one has a job: forecast, replan, inspect the product, or improve the system. Facilitation is making that job happen in the timebox — including when the loudest person in the room would rather it did not.
Each event has a job. Do not freelance.
Sprint Planning answers what the Sprint is for and how the work will start. The output is a Sprint Goal and a Sprint Backlog the Developers can stand behind. If planning becomes a two-hour argument about story points and nobody can say the goal in one sentence, you facilitated a scoring session, not a plan.
The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the day's plan. It is not a status report to you, the Product Owner, or a visiting director. If people speak to your face and then wait for instructions, stop the format and return the meeting to the board and the goal.
The Sprint Review inspects the Increment with stakeholders and adapts the Product Backlog. Demonstration is a means. Feedback that changes the backlog is the point. The Retrospective inspects how the team worked and produces a small number of improvements they will try. A retro that ends with twenty sticky notes and zero owners is a group sigh. You are there to leave with a change.
Facilitate the room. Do not perform in it.
Facilitation is structure, airtime, and a written output. Open with the purpose and the timebox. Put work on a wall or a board, not in a monologue. When two people debate while eight watch, split the conversation or park it. Your success metric is whether the event produced its artefact — a goal, an adapted plan, a backlog change, an experiment — not whether you sounded wise.
Protect the timebox without being a scold. A planning session that overruns because the backlog was not ready is information: refinement failed upstream. End on time and make that the impediment. Stretching every event 'just this once' teaches the organisation that Scrum time is optional and your calendar is not.
Invite the right people and keep the wrong purpose out. Stakeholders belong in the Review. They do not belong in the Daily Scrum to 'get a feel.' The Product Owner belongs in Planning and the Review; they do not run the Retrospective. If a senior visitor turns an event into a performance review, you intervene. That is the job. Politeness that lets the framework die is not professionalism.
The failure modes you will meet in week two
Planning as commitment theatre: the team is pressured into a forecast they do not believe, then spend the Sprint quietly dropping work. Facilitate honesty. A smaller forecast that lands beats a heroic board that lies until Thursday.
The Daily Scrum as a tour of tickets. People recite yesterday without looking at the Sprint Goal. Interrupt the ritual: 'Are we going to meet the goal? What is the one thing that would make that false?' If the answer is a dependency nobody owns, you now have an impediment, which is a better use of the sixteenth minute than another round of 'I will keep working on my tickets.'
Skipped or shortened Reviews and Retrospectives under deadline pressure. That is eating the seed corn. The Review is how the product stays pointed at value. The Retrospective is the only standing appointment the team has to get less stupid. Cutting them to 'save time' is how you run the same Sprint until people leave.
Summary & next steps
Facilitate for the event's job: a Sprint Goal and backlog, a daily replan, an inspected Increment, a tried improvement. Hold the timebox. Keep status-seeking visitors from colonising the Daily Scrum. End with artefacts, not vibes.
Next: removing impediments — how to tell a blocker from a complaint, and how to clear it without becoming the team's permanent concierge.