Team

About this shelf

Team is for people who’ve watched a “process” become the product — and want the coordination layer of shipping to stay legible again.

Reviews, planning, on-call, metrics, retros, shared failure — the through-line is mechanism. Queues you can see. Rituals that earn their calendar slot. Accountability that doesn’t need a villain. Peers who’ve sat in the room, not people collecting agile badges.

Ceremony worship stays out. So do culture slogans with no operating model, and “just communicate more” as the whole answer. Another standing meeting is probably the wrong fix — or the wrong shelf (People if the calendar is eating the humans). The pieces here name the mechanism, not the slogan — start with review that teaches if the merge queue is where coordination actually breaks.

If you’re new, use the picks. Levels cut a shorter path through the rest of the grid.

Start here

  1. Code Review That Teaches — Not Just Slows Merges

    Review as teaching, not a merge tax.

  2. Cross-Team Dependencies — How to Not Get Blocked

    Dependencies without living in someone else’s backlog.

  3. DORA Metrics Are Not KPIs

    Stop turning delivery signals into performance theater.

  4. Your First Sprint Retrospective — Without the Venting Session

    A retro that isn’t a venting session with sticky notes.

TeamMastery

DORA Metrics Are Not KPIs

What gets gamed the moment it's a target — and what actually tells you something about team health.

6 min · July 25, 2026

TeamDoing

Ceremony Fatigue Is a People Problem

Your team can hit every Scrum event and still lose the humans who do the work — because the calendar was never about sustainable pace.

6 min · July 9, 2026