Shape Up is Basecamp's software development methodology, documented by ryan-singer in shape-up (2019, published free online). It emerged from Basecamp's own practice over roughly a decade and represents a deliberate, explicit rejection of scrum — particularly the two-week Sprint, the Product Backlog, and the velocity-based planning model. Shape Up attracted significant attention as one of the most substantive alternatives to the Scrum/Agile mainstream to emerge from the post-agile-era.
Core Concepts
Six-week cycles — Shape Up uses six-week development cycles, not two-week Sprints. Singer's argument: two weeks is too short for meaningful, coherent work. Projects are either broken into disconnected pieces that don't ship value, or they spill across Sprint boundaries and undermine the Sprint model's accountability. Six weeks is long enough to build something significant from conception to completion.
Shaping — Before a project enters a cycle, it is "shaped" by senior people (typically a product designer and developer) into a well-bounded proposal: a rough solution concept, identified risks, defined appetite (how much time this is worth). Shaping is creative, high-risk work done before betting on a project. It is not specification — shaped work still has unknowns — but it is specific enough that the team can build without being overwhelmed by open-endedness.
The Betting Table — Shaped projects are "bets" that leadership makes at the beginning of each cycle. There is no backlog that accumulates and ages. Projects not chosen in a given cycle are either re-pitched next cycle or abandoned. Singer is explicit: the absence of a backlog is a feature, not a bug. Backlogs become organizational debt — a list of things that were once thought important but never examined again.
Cool-down — A two-week period after each six-week cycle where no planned work happens. Teams fix bugs, explore ideas, and recover. This directly instantiates sustainable-pace without the political negotiation that typically surrounds it in Scrum organizations.
No micromanagement of tasks — Teams do not break work into tasks assigned to individuals before the cycle begins. The team figures out how to build the shaped work during the cycle itself. This is self-organizing-teams operationalized: the team has the shaped concept, the appetite, and the six weeks — they decide how to use them.
The Rejection of Scrum Ceremonies
Singer is explicit that Shape Up emerged from dissatisfaction with Scrum's ceremony structure. His arguments:
Shape Up's explicit anti-Scrum positioning makes it unusual in the Agile adjacent landscape — most post-Agile proposals work within the framework ecosystem. Shape Up claims to offer a different model for organizations with the autonomy to adopt it.
Applicability
Shape Up is most clearly applicable in Basecamp's context: small, senior teams with clear product ownership and organizational autonomy. Critics note that the shaping and betting functions require senior practitioners who can distinguish good-shaped from bad-shaped work, and that the model does not address how to coordinate multiple teams. It does not scale the way safe-scaled-agile-framework or less-large-scale-scrum attempt to. Its contribution is as a proof of concept that the Scrum ceremony structure is not the only viable option, not as a universal enterprise alternative.