Shape Up
Basecamp's 6-week cycle approach
Shape Up is Basecamp's alternative to Scrum. Work happens in 6-week cycles (not sprints), features are shaped (scoped and de-risked) before they're scheduled, and teams have full autonomy on implementation. There are no standups, no sprint planning, and no velocity tracking — instead, shaped pitches and fixed time budgets replace estimation.
Developed internally at Basecamp (formerly 37signals) and published as a free book by Ryan Singer in 2019.
Use Shape Up when
- ✓Small product teams (1 designer + 1–2 engineers) who can own a feature end-to-end
- ✓You want to eliminate estimation overhead and backlog grooming ceremonies
- ✓The team is mature enough to self-organise around a clearly shaped brief
- ✓You ship web products with flexible scope
Avoid it when
- ✗Large teams that need coordination across many squads
- ✗Regulated environments requiring detailed audit trails and fixed delivery dates
- ✗Teams that benefit from daily check-ins and frequent stakeholder demos
Key Concepts
The work done by senior staff before a feature enters the cycle. Output: a pitch with problem, appetite, solution, and rabbit holes.
How much time the company is willing to spend on a feature — not an estimate of how long it will take.
A document presenting a shaped feature for betting. Includes fat marker sketches, not wireframes.
A meeting where leadership decides which pitches to schedule for the next cycle. No backlog — unscheduled pitches are dropped.
A 2-week buffer between cycles for bug fixing, exploration, and admin. No new feature work.
A progress visualisation where the left side is "figuring it out" and the right side is "making it happen."
How it works
Senior staff shape the next batch of work — defining problems, setting appetites, sketching solutions, flagging rabbit holes.
1-day meeting where leadership reviews pitches and bets cycles on 2–4 of them. Unscheduled work is dropped, not queued.
Teams build. No standups, no interruptions. Teams update hill charts and reach out only when genuinely stuck.
Teams fix bugs, do technical exploration. Shapers prepare pitches for the next cycle.
Tools that support Shape Up
Industry standard for software development teams — most PMs will encounter Jira in their career
Exceptionally intuitive and visually clean interface — one of the lowest onboarding friction tools for non-technical teams
Highly visual and intuitive interface with color-coded boards — one of the easiest PM tools for non-technical teams to adopt
All-in-one platform replacing multiple tools — docs, whiteboards, goals, time tracking, chat, and project management in a single workspace
Unmatched flexibility as an all-in-one workspace — combines docs, wikis, databases, and project management in a single tool
Spreadsheet-familiar interface makes adoption easy for teams transitioning from Excel — minimal training needed for basic use
Extremely intuitive drag-and-drop Kanban interface — virtually zero learning curve, new users productive within minutes
Best-in-class infinite canvas experience — the gold standard for collaborative whiteboarding with real-time multiplayer editing
Frequently Asked Questions
Yes — many teams adapt it. The 6-week cycle, appetite-based scoping, and shaping process are the transferable parts. The betting table and 'no backlog' policy are harder to adopt in orgs with strong stakeholder expectations around roadmaps.
Basecamp natively supports Shape Up. Linear has a Cycles feature inspired by it. Some teams use Notion for pitches + any task tracker for execution.
An estimate answers 'how long will this take?' An appetite answers 'how much time are we willing to spend?' Appetite is set before shaping begins and constrains the solution scope.