Page 175 · Module 07, Operate with Precision · this screen continues that page

All 108 frameworks
7.8IntermediateModule 07 · Operate with Precision

Agile Sprint Canvas

Your team plans a lot but ships inconsistently. Sprints fill up with tasks that don't connect

The prompt

Copy & paste ready
7.8Agile Sprint Canvas
Act as an Agile coach helping design a focused sprint. Team : [SIZE, ROLES, WHAT YOU ARE BUILDING] Sprint duration : [1 OR 2 WEEKS] Priorities this sprint. : [WHAT YOU MOST NEED TO ACCOMPLISH] Capacity : [AVAILABLE PERSON-DAYS THIS SPRINT] Design a complete Sprint Canvas: SPRINT GOAL : One sentence what defines success BACKLOG ITEMS : 5–8 tasks that directly serve the goal. Each with: owner, estimate, priority DEPENDENCIES : What must happen before sprint starts RISKS : What could prevent completion DEFINITION OF DONE : How we know each item is complete STANDUP FORMAT : 3 daily questions for team alignment RETROSPECTIVE : 3 questions for end-of-sprint review Flag any backlog item that does not directly serve the sprint goal, those should be deferred. Sprint Canvas - Two Weeks That Ship, Not Just Plan Sprint Canvas Two-Week Sprint Backlog Definition Daily Standup Dependencies Risks Timeline Bar Goal Items of Done Questions
LabelsReplace theseSwap the role below

LabelsReplace theseSwap the role below

Pro tip, from the book

The most valuable sprint ritual is not the standup, it is the retrospective. Teams that run honest retrospectives improve sprint-over-sprint. Teams that skip them repeat the same problems. Block the time before the sprint starts, not at the end when everyone is rushing to the next thing.

Who should run this prompt

Module role profile

Who should audit and improve your operations? Operations problems hide in plain sight — in the handoffs nobody notices, the processes nobody has documented, and the decisions nobody has questioned. The roles on this page bring the discipline of people who have built systems that run without heroics. Use them to find what is broken before it breaks you, and to build what scales before you need it to.

Choose any role to drop it into the prompt above. Only the highlighted opening clause changes — the rest of the prompt stays exactly as printed.

Internal rolesThink from inside the organisation
Outside perspectivesChallenge your blind spots

◆◆◆◆◆ → ◆ seniority, board level down to specialist outside the organisation

How to make any role sharper

  1. Add years of experience: "...with 15 years in enterprise SaaS" produces different depth than just the title.
  2. Add what they care most about: "You care most about [X]" shapes every word of the output.
  3. Add their communication style: "Be direct. Flag risks first. No jargon." changes the tone entirely.
See also: 1.3 Role Prompting - The Expert Chair

Use this when

The problem it solves

to a clear goal. By the end of two weeks, the sprint goal has shifted or was never clear in the first place.

How the framework works

From the printed page

Developed from Jeff Sutherland and Ken Schwaber's Scrum framework, the Sprint Canvas is a one-page planning tool for a two-week sprint. It maps: Sprint Goal (the one thing that defines success for this sprint), Backlog Items (tasks selected to achieve the goal), Dependencies (what needs to happen before these tasks can start), Risks (what could prevent completion), Definition of Done (how we know each item is complete), and Daily Standup Questions (what keeps the team aligned). AI can help design a sprint that is internally coherent, where every backlog item connects to the sprint goal.

The method, in four moves

Do these in order
1

Define the Sprint Goal before selecting backlog items, items must serve the goal, not the other way around.

2

Limit work in progress, it is better to finish 5 items completely than to start 10.

3

The Definition of Done must be agreed before the sprint starts, not interpreted at the end.

4

Run a 30-minute sprint retrospective after every sprint: what to start, stop, and continue. Run focused two-week cycles that ship not just plan If you can delete an item from the backlog and the Sprint Goal is still achievable, that item shouldn't have been in the sprint. Every task earns its place by serving the goal, not by being useful, urgent, or already half-started. Backlog Items Aren't the Goal

Where the framework comes from

Jeff Sutherland & Ken Schwaber — Scrum framework, 1990s · Agile Manifesto, 2001

When this page changes, your copy of the book does not have to.

The book prints the framework. This page keeps it — and keeps the prompt current, because prompting technique moves faster than print does. When it moves, this page is rewritten and the code in your copy keeps pointing at it. No second edition, no replacement purchase, no account.

If something here looks wrong — a prompt that does not match its framework, a figure that reads oddly — tell Raphy. That correction reaches every printed copy at once.

Framework7.8 of 108
Printed onPages 174175
Prompt extracted18 Sept 2026
Costs to readNothing, no account

Copying is free. An account keeps them.

Nothing on this page is behind a login and nothing ever will be. Save any prompt to your own list, pick up on another device, and send a colleague a link with your name on it. No card, no trial, no paywall on the prompts themselves.

See how it works
Save this framework to your own list
Pick up where you left off on another device
Send a colleague a link with your name on it