# Sprint Goal Canvas — Sprint {{ NUMBER }}

Fill this in before sprint planning. Bring it to the meeting as a draft.

## 1. The user

Who actually feels the difference if this sprint succeeds?

> _A specific role or persona, not "users"_

## 2. The change

What changes for that user by the end of the sprint?

> _Observable. Demoable. Not internal._

## 3. The metric

How will you know it landed?

> _A number, an event, a state. Not "we shipped it."_

## 4. The goal sentence

Combine the above into ONE sentence:

> **Sprint goal:** Ship _________ to ________ so that ________.

### Examples

- Ship the new onboarding flow to 10% of signups so that we cut activation drop-off below 35%.
- Cut p95 API latency below 200ms on /dashboard so that the team stops getting paged during peak hours.
- Get the billing import to feature-complete and behind a flag so that next sprint is purely QA + rollout.

## 5. What gets dropped first

If the sprint runs hot, which tickets get descoped while still hitting the goal?

-

## 6. What this is NOT

Things people might assume are part of the goal but aren't:

-

---

Glossary: https://sprintflint.com/glossary/sprint-goal
Sprint planning guide: https://sprintflint.com/docs/sprint-planning