What RetroSync does, by sub-chapter. Each entry has a short description, a figure where it helps, and a cross-reference to the chapter where it's used most.
A paper-craft retro surface. Real-time, anonymous-by-phase, with first-class action items.
Themes drafted from notes, summaries written for stakeholders, a coach that suggests action items.
An MCP server over HTTP, a retrosync CLI, personal access tokens, scoped permissions, per-call audit. Detailed in § 4.
.NET tool; JSON-by-default; pipes into jq, xargs, your shell.read, read,write. Server-enforced on every call.Themes turn into owned, dated tickets. Sync to Jira or Linear without leaving the board.
A small, useful set of charts. No vanity. Designed so a Friday glance tells you where the team is heading.
Every retro produces three numbers — sentiment (1–100), participation (% of members), completion (% of actions shipped). Stored, charted, and comparable across teams.
The controls your security team will ask for. SSO, SCIM, audit, scoped tokens. No surprises.
Read the rest of the book at your own pace. Or skip to the demo.