Coaching Intervention Rhythm

Definition

Coaching a team is not a constant, evenly distributed activity — it has a rhythm tied to the natural boundaries of the work cycle. Whole-team coaching (teaching, observing, giving feedback to the group) belongs at the beginning of a sprint, when the team is starting up, and at the end, during the retrospective. In the middle, whole-team coaching should quiet down almost entirely, replaced by individual coaching and quiet "ground crew" support so the team can focus.

In the Book

Chapter 5 draws on organizational psychologist J. Richard Hackman's research that coaching interventions have their strongest effect at the beginning and end of a project, and translates it to agile's shorter cycle: the sprint. Figure 5.1 depicts the coach's attention swinging from whole-team (sprint planning, retrospective) to individual (mid-sprint, when problems surface one-on-one) and back to whole-team again. The book is explicit that an ill-timed intervention — bringing a big observation to the whole team mid-sprint — "can do more harm than good," disrupting the focus agile is designed to protect. At the very start of a team's life this rhythm is amplified into a single formative event: the coach's job is to "breathe life into the team's structural shell" so it can start functioning on its own, front-loading education before backing off.

Why It Matters

This reframes coaching effort as something to budget across a cycle rather than apply uniformly — the same principle that governs when to run a code review, hold a 1:1, or intervene in any team executing a bounded unit of work. Knowing that boundaries (start/end) are where guidance lands and the middle is where it corrodes momentum turns "when should I say something" into a answerable, structural question instead of a judgment call made fresh every time.