ryan-singer's book describing Basecamp's product development methodology, published as a free online book in 2019. Shape Up is explicitly positioned against mainstream Agile practices — scrum, sprints, backlogs, daily-standups, and Kanban boards are all rejected by name — making it the most prominent post-Agile methodology document since the agile-manifesto itself.
The shape-up-methodology
Shape Up proposes an alternative to sprint-based development built around:
1. 6-week cycles: Not 2-week sprints. Six weeks is long enough to build something meaningful and short enough to maintain urgency. There is no sprint review at the end — teams ship.
2. Shaping: Before work begins, senior people ("shapers") do rough design work to define the problem and the approach at the right level of abstraction — enough to know what we're building, not so much that we're designing for the team. Shaped work has a fixed appetite (how much time we're willing to spend) and a rough solution, but leaves details for the team to work out.
3. Betting: Rather than a backlog maintained by a Product Owner, Basecamp uses a "betting table" where shaped pitches compete for cycle slots. Rejected pitches don't go on a list to be revisited — they're dropped. This prevents the backlog from becoming a graveyard of half-formed ideas.
4. No backlogs: The explicit rejection of the product backlog is the most radical departure. ryan-singer argues that backlogs grow indefinitely, create false obligations, and lead to planning debt that teams never repay.
5. Teams have full latitude within cycles: Once a team takes on a bet, they own the problem. They don't receive tasks — they figure out what tasks exist and work them in any order.
Critique of Agile
ryan-singer argues that Scrum's two-week sprints are too short to build anything meaningful, that the sprint ceremony (planning, review, retrospective) consumes significant time, that the backlog creates anxiety and obligation, and that standups interrupt and surveil rather than coordinate. These are not new criticisms — many practitioners share them — but Shape Up is unusual in providing a concrete alternative rather than just critique.
The methodology reflects Basecamp's specific context: a small product company with stable teams, no external clients, and the ability to make unilateral decisions about what to build. Critics note that the approach may not generalize to teams with clients, regulatory requirements, or team structures unlike Basecamp's.
Relationship to the Agile tradition
Shape Up sits in the post-agile-era tradition, sharing ancestry with lean (timeboxing, working in cycles) while rejecting the institutional forms of Agile. It does not engage with the agile-manifesto's values directly, though its emphasis on working-software (ship at end of cycle) and individuals-and-interactions (teams own the solution) is consistent with manifesto values, if not the certification ecosystem that grew up around them.