What I kept from being a scrum master

A white castle on a forested hillside below rocky Alpine peaks, with a flat meadow and bare trees in the foreground

Before I managed engineers I ran their process. I was a team's scrum master, running the planning, standups, retrospectives, and board. When I became a manager I assumed I would leave most of that behind. I think I was half right. The ceremonies I left behind. The habits underneath them turned out to be most of what managing is.

Making the work visible

The first thing I kept is the conviction that work should be visible without anyone having to ask. A board that reflects what is happening, a plan people can see, a clear statement of what done means. As a manager I think it is the difference between a team that is trusted and one that has to keep explaining itself.

It also protects the team. When the work is visible, why something is late answers itself.

Asking what is in the way

The daily standup question, what is blocking you, is the one I still ask more than any other. But I think the discipline of asking it every day, and then doing something about the answer, is the most useful thing a manager does. Most blockers are small and most are mine to remove.

Facilitation over direction

A scrum master runs a meeting without being its subject. The team decides, the facilitator makes sure the deciding happens. The meetings I run go best when I say the least, and the decisions that hold are the ones the team reached rather than the ones I announced.

I think this is the part most new managers get backwards. The authority of the role makes it tempting to use. The facilitation habit reminds you that a team that decided for itself will do the thing. A team that was told will do it until you stop watching.

Retrospectives, but honest ones

I kept the habit of looking back on purpose, at a set time, with the whole team. What I had to learn is that the manager is now part of what the retrospective is about, and a retrospective where the manager is exempt is theater. The ones that work are those where the first thing changed is something I was doing.

What I dropped

I stopped owning the process for its own sake. Scrum, kanban, whatever the team wants, the manager's job is the outcome, not the ritual. When I catch myself defending a ceremony rather than a result, I take it as a sign I have slipped back into the old role.

I also stopped treating velocity as a target. The moment it becomes a number the team is held to, it stops being a measurement and starts being a negotiation. I still look at it. I do not manage to it.

Where this stops being true

Some teams need a process owner who is not their manager, and I think that is healthier when the team is large enough to support it. The habits here are a manager's habits either way. The ceremonies can belong to someone else.

Photo source: https://photos.robertstowe.com/bavarian-alps