Overview
Scrum is the default for product development teams. Most organizations start with some version of it: sprints, standups, retrospectives, backlog grooming. Shape Up, created by Ryan Singer at Basecamp, rejects much of that ceremony in favor of longer build cycles, fixed-scope bets, and team autonomy.
The choice between them affects how your team plans, builds, and ships. For broader context on agile approaches, see the agile product management guide and the Scrum vs Kanban comparison.
Quick Comparison
| Dimension | Shape Up | Scrum |
|---|---|---|
| Cycle length | 6 weeks + 2-week cooldown | 2-week sprints (typical) |
| Planning | Betting table (leadership bets on shaped pitches) | Sprint planning (team pulls from backlog) |
| Estimation | None. Fixed time, variable scope | Story points, velocity tracking |
| Daily ceremony | None. Async check-ins optional | Daily standup (15 min) |
| Backlog | No backlog. Pitches evaluated fresh each cycle | Prioritized product backlog |
| Scope management | Fixed time appetite, cut scope to fit | Sprint commitment, negotiate scope in planning |
| Progress tracking | Hill charts (uncertainty vs execution) | Burndown charts, velocity |
| Team size per unit | 2-3 people per bet | 5-9 people per Scrum team |
| Best for | Small-to-mid orgs, autonomous teams | Any size, teams needing structure |
How Shape Up Works
Shape Up has three phases that repeat every 8 weeks (6-week build cycle plus 2-week cooldown).
Shaping
A senior person, usually a PM or senior engineer, defines the problem and outlines a solution at an intentionally abstract level. The output is a pitch that includes the problem statement, a solution sketch (fat-marker drawings, not wireframes), rabbit holes to avoid, and a time appetite. The key constraint: the work must fit within 6 weeks. If it does not, the shaper cuts scope rather than extending the timeline.
Betting
Before each cycle, a small group of senior stakeholders reviews shaped pitches and decides which to fund. This is the "betting table." Pitches that are not selected do not carry over. There is no backlog of deferred work. This forces fresh evaluation every cycle and prevents stale items from accumulating.
Building
Small teams of 2-3 people take a bet and have 6 weeks to ship it. They have full autonomy over how to build it. No standups. No interruptions. No status requests. Progress is tracked with hill charts, where "uphill" means the team is still resolving uncertainty and "downhill" means they know what to do and are executing.
Cooldown
The 2 weeks between cycles are for bug fixes, tech debt, small improvements, and exploration. This separation prevents maintenance work from consuming build capacity.
How Scrum Works
Scrum organizes work into fixed-length sprints (typically 2 weeks) with defined roles and ceremonies. The sprint planning guide covers the mechanics in detail.
The Product Owner maintains a prioritized backlog. During sprint planning, the team selects stories from the top of the backlog and commits to delivering them within the sprint. Daily standups surface blockers. Sprint reviews demonstrate completed work. Retrospectives identify process improvements.
Estimation (story points) and velocity tracking give teams data for forecasting. After 3-4 sprints, a team can predict how much it will deliver per sprint with reasonable accuracy.
Appetite vs Estimation
This is the sharpest philosophical divide between the two methodologies.
Scrum estimates work, then plans time. The team scores a story at 8 points, checks their velocity (say, 40 points per sprint), and determines how much fits in the sprint. If a feature is estimated at 80 points, it takes 2 sprints.
Shape Up fixes time, then shapes scope. Leadership sets a 6-week appetite. The shaper designs a version of the feature that fits within 6 weeks. If the full vision would take 12 weeks, the shaper removes scope until it fits. The team never estimates effort.
Shape Up argues that estimates are unreliable and that fixing the constraint (time) and flexing the variable (scope) produces better outcomes. Scrum argues that estimation data, while imperfect, enables forecasting that teams and stakeholders need.
Pitches vs User Stories
Shape Up pitches are deliberately abstract. They describe the problem, sketch a solution direction, flag risks, and set boundaries. They leave implementation details to the build team.
Scrum user stories are more specific. "As a [user], I want [action] so that [benefit]" with acceptance criteria that define done. Stories are refined during backlog grooming before sprint planning.
The tradeoff: pitches give teams more creative freedom but require senior builders who can fill in the details. Stories provide clearer expectations but can constrain the team to a predetermined solution.
Team Size Considerations
Shape Up: 2-3 people per bet. One designer and one or two engineers. Small teams move fast, communicate easily, and do not need coordination ceremonies. But they lack redundancy. If one person is sick or stuck, the bet is at risk.
Scrum: 5-9 people per team. Larger teams can handle more complex work and absorb absences. But they need standups, planning sessions, and coordination rituals to stay aligned. Communication overhead scales with team size.
Shape Up compensates for small teams by running multiple bets in parallel. A 20-person engineering org might run 6-8 bets simultaneously, each with a small team, rather than organizing into 2-3 Scrum teams.
When Each Works Best
Choose Shape Up when:
- Your org is 10-200 people with senior, autonomous teams
- Backlog grooming has become a time sink that does not produce proportional value
- You value deep work over frequent stakeholder check-ins
- Your team has senior people who can shape work effectively
- You control your own product roadmap and do not depend on external release schedules
Choose Scrum when:
- You need predictable delivery cadence for external stakeholders
- Your organization is larger than 200 people and needs formal coordination
- Your team includes junior engineers who benefit from structured roles and ceremonies
- You operate in a regulated environment requiring documented processes
- You need velocity data for capacity planning across multiple teams
Hybrid Approaches
Most teams do not follow either methodology strictly. Practical hybrids include:
Shape Up principles for Scrum teams: Use fixed-time thinking instead of story points. Shape work to fit the sprint rather than estimating and negotiating scope. Replace backlog grooming with a betting table every 2-3 sprints. Dedicate every fourth sprint to bug fixes and tech debt instead of allocating 20% of every sprint.
Scrum principles for Shape Up teams: Add retrospectives after every cycle. Run a brief demo at the end of each bet for stakeholder alignment. Track throughput data (bets completed per quarter) for long-term forecasting. Use Kanban visualization during cooldown to make maintenance work visible.
The Verdict
Shape Up eliminates waste that Scrum tolerates: backlog grooming, estimation sessions, daily standups. Scrum provides structure that Shape Up lacks: cross-team coordination, forecasting, and regular retrospectives. Pick Shape Up if you are a product company with small, senior teams that want focused build time. Pick Scrum if you need predictable delivery cadence, external coordination, or operate at scale. The best teams borrow from both and skip the parts that do not serve them.