Practical playbooks for scrum masters and agile coaches — written from real facilitation experience, not vendor marketing.
Action items die because most retro tools treat them as sticky notes. Owner, due date, carryover into next retro, push to Jira — the four features that decide whether anything happens after the meeting.
Most async retro support is theatre — a comment field, a 'remote-friendly' badge, and a meeting that still has to happen on Tuesday. Two tools clear the bar end-to-end, and two patterns make the difference more than any feature.
Most teams agonise over Mad/Sad/Glad vs 4Ls vs Starfish when the variables that actually move the needle are anonymous input, time-boxing, and follow-through. The format is the smallest lever in the room.
Most free retro tools cap at the wrong moment. Three free retro tools genuinely hold up for an 8-person team running a fortnightly retro — here's the short list, and what fails on the rest.
A vendor-neutral framework for choosing the best retrospective tool for your team. Features, integrations, pricing red flags, and the 5 questions to ask before signing.
12 proven retrospective formats explained: Start/Stop/Continue, 4Ls, Sailboat, Mad/Sad/Glad and more. When to use each, how to run them, and what to expect.
Run distributed retros that feel as engaged as in-person — silent parallel input, anonymous voting, async patterns, and action item tracking before the call ends.
10 small facilitation habits that separate retrospectives people endure from retros they look forward to. From managing dominant voices to surfacing dissent safely.
A practical playbook for scrum masters facilitating sprint planning, daily scrums, sprint reviews, retrospectives and backlog refinement — agendas, time-boxes and anti-patterns.