Field guides

Each asset is designed to be forwarded to busy leads. Formats stay lightweight—PDF, Notion exports, or slide decks without animated builds.

Facilitation

SprintCanvas planning checklist

Single-page prompts that keep backlog refinement inside the timebox.

Format: PDF

Retrospectives

Retro arc planner

Energy mapping plus follow-through tracker for Team Retrospectives graduates.

Format: PDF

Flow

Kanban policy worksheet

Plain-language policies for triage lanes and roadmap guardians.

Format: Notion

Leadership

Leadership question bank

Short coaching questions that avoid prescribing solutions during reviews.

Format: Slides

Delivery

Dependency surfacing script

Partner call outline used in Scrum Foundations backlog refinement.

Format: PDF

Field writing archive

Linked from the home blog preview for continuity.

2025-03-12

Designing a cohort rhythm that survives time zones

By Haneul Park

Cohorts fail quietly when calendars fight the work week. We anchor live sessions to predictable windows, then mirror decisions in short written briefs so late joiners never guess what changed. The second pillar is a shared backlog of practice tasks. Each team posts a one-minute clip or screenshot of their board state, which keeps conversation concrete instead of theoretical. Finally, we rotate facilitators across modules so participants hear different facilitation styles while the rubric stays consistent. That variety keeps attention high while standards remain steady. If you are planning a global rollout, start with a two-week pilot that measures attendance, submission latency, and retro quality—not vanity completion stats.

operations · cohorts · remote

2024-11-28

Retro formats that surface role confusion early

By Minseo Choi

Role confusion shows up as polite silence in retros. We begin with a silent map of who touched each backlog item, then compare it to the intended RACI snapshot from the course packet. Next, we run a five-minute timeline reconstruction focused on handoffs. Teams narrate where work waited, not who failed, which keeps psychological safety intact. We close with a single commitment written as a pairing rule—for example, “design reviews land before noon KST.” That crisp language travels better than generic action items. These patterns are lightweight enough to reuse weekly and strong enough to catch drift within a sprint.

retrospectives · facilitation

2025-01-09

Facilitation notes from the SprintCanvas simulation lab

By Jonah Mercer

The lab is intentionally tactile: sticky notes, a physical board, and a timer you can hear. Digital boards return later; first we want muscle memory for ceremony cadence. We slowed the planning segment after noticing teams skipped acceptance checks. Adding a bright checkpoint card cut rework in the review demo by half in our internal scoring. We also split the facilitator script into color-coded beats so coaches can jump in without stepping on each other. That small production detail matters in enterprise rooms with overlapping experts. Graduates tell us the lab is where abstract ideas snap into choreography. We treat it as a rehearsal stage, not a performance review.

labs · scrum