Collaboration & Process › Agile & Delivery Process

Shape Up

Basecamp's six-week cycles with shaped, fixed-time bets.

Shape Up is a product-development method associated with Basecamp that organizes work around shaped proposals and fixed-length cycles. A proposal describes a problem, appetite (how much time the team is willing to spend), boundaries, and a possible solution direction before a team takes it on.

The method tries to reduce open-ended projects by setting a time budget and allowing scope to be cut while protecting the core outcome. For example, a team might agree to spend one cycle on a dependable import path, leaving advanced mapping controls outside the bet. The team needs enough autonomy to make those scope decisions during implementation.

Shape Up is not a universal fit or a guarantee that a project will finish inside its cycle. It can be difficult when work has external deadlines, regulatory gates, uncertain research, or dependencies the team cannot control. The shaping step also takes real product and engineering effort; vague proposals just move uncertainty into the cycle.

Backend, frontend, and data engineers should identify enabling work and cross-team dependencies before a bet is accepted. Preserve quality and operational requirements when trimming scope. See MVP, iterative delivery, and scope creep.

Check the workflow with a recent piece of work rather than relying on an abstract rule. If the practice adds a queue or hides blocked work, adjust it; if it helps the team finish and learn, keep it. Backend developers can flag service constraints, frontend developers can check user-facing behavior, and data engineers can surface pipeline or data-quality dependencies.

After trying it, review several completed items and adjust the practice if it created a queue, hid a blocker, or failed to produce a useful outcome.