What is Shape Up?
What is Shape Up?
Basecamp's 6-week product development methodology — what it is, how it differs from Scrum, and what BAs can learn from it.
The core concept
Shape Up works in 6-week building cycles with three phases:
- Shaping: Senior people define work in enough detail to estimate whether it can be done in 6 weeks — but not so much that it removes team autonomy. Output: a "pitch" document with appetite (how much time the problem is worth) and rough wireframes.
- Betting: Leadership reviews shaped pitches and commits to which ones to build. What is not selected is not kept on a backlog — it is discarded.
- Building: Teams work autonomously for 6 weeks. No daily standups. Teams define their own tasks and manage their own scope within the "appetite."
What BAs can learn from Shape Up
Even if your organisation uses Scrum, Shape Up's "Shaping" phase has ideas worth applying:
- Appetite over estimate: "How much time is this problem worth?" is a better starting question than "How long will it take?"
- Pitches over PRDs: A 5-page pitch that describes the problem, scope, and constraints is more useful than a 50-page PRD that pre-empts every design decision
- No backlog: Discarding unprioritised items forces teams to ask "does this really matter?" rather than accumulating technical debt in an ever-growing backlog
📌 Key Points
Shape Up is not widely used in ANZ but its concepts — especially "appetite" and "shaping before committing" — are transferable to any methodology
The "no backlog" principle challenges BA assumptions about requirements management. What if ideas that don't get actioned in 6 weeks were simply dropped rather than queued indefinitely?
For the CBBA exam, Scrum and Kanban are more important to know than Shape Up — but Shape Up demonstrates breadth of Agile knowledge in interviews
Read the free Shape Up book at basecamp.com/shapeup — it's 150 pages and genuinely worth the time for any BA working in a product environment