Use this when: You're at the start of a cycle and need to decide what ships, who works on what, and how to protect the team from mid-cycle scope creep.
You're done when: You have shaped pitches with clear boundaries, the team understands the appetite, and there's a cooldown period scheduled before the next cycle.
The Sequence
Template
Kill the status meeting
This lesson shows up on a lot of teams: someone eventually points out that a standup could be replaced by an email. The rule is simple: every recurring meeting needs a clear purpose beyond "getting updates." If the meeting is just people reading their status aloud, replace it with an async update and give the team their time back. The sprint kickoff is worth doing live because it's about making bets and resolving ambiguity. The daily check-in usually isn't, because it's about information transfer, and writing does that better.
Fixed Time, Variable Scope
The entire Shape Up methodology that underpins this sequence comes from one principle: fixed time, variable scope. Traditional planning asks "how long will this take?" and lets the scope dictate the timeline. That's backwards. Fix the time (six weeks), then shape the scope to fit. An estimate starts with a design and ends with a number. An appetite starts with a number and ends with a design. This forces real trade-offs upfront instead of mid-sprint panic.
Keep the Team Constrained on Purpose
Things should feel meaningfully constrained, not chronically starved. Constraint is a feature, not a bug, because it forces sharper trade-offs about what to build. But there is a line: if the team is permanently underwater, quality drops, morale erodes, and judgment gets worse. The sprint planning discipline of shaping pitches and killing bets works when the team can't do everything, not when they're too exhausted to do anything well.
Keep planning simple: ask what you want to build over what time frame, how many people you need to actually do it, and what the relative priorities are. Don't overthink the process. A clear bet table with honest appetite sizing does more than an elaborate sprint planning ceremony.
Example
A B2B SaaS team shaped a pitch: "Customers can't tell which team members are active vs. idle."
- Appetite — 1-week small batch
- Solution sketch — add last-active timestamps to the team page and a weekly email digest
- Rabbit holes — don't build a full activity feed (that's a 6-week project)
- No-gos — no real-time presence indicators, no manager dashboards
At the betting table, leadership killed two other pitches and committed to this one plus a 6-week billing migration. The team self-organized using hill charts — no daily standups, no ticket-by-ticket status updates. They shipped the activity feature in 4 days, used the remaining day for polish. The 2-week cooldown after the cycle handled accumulated bug reports and let one engineer prototype a feature for the next cycle.
Written with ❤️ by a human (still)