Run a Shape Up style 6-week cycle kickoff

Why Shape Up Replaces Sprint Theater

Two-week sprints optimize for predictability at the cost of depth — teams produce shallow work and spend disproportionate time on ceremonies. Basecamp's Shape Up replaces the cadence with 6-week cycles framed around shaped pitches and strict appetites. Atlassian's sprint planning writing documents the cost of over-refined backlogs; Shape Up's response is to refuse granular decomposition up front and trust the team to discover scope while building. Getting Real made the original case: appetite is the budget, not the estimate.

How the Run a Shape Up style 6-week cycle kickoff Prompt Works

The prompt validates the pitch shape before any assignment, sets the hill-chart baseline so status is visible without stand-ups, and enforces the circuit breaker — ship what works at week 6 or shelve, never extend. The no-swapping rule on team composition is the forcing function: cycles work only when the team holds context for the full six weeks.

When to Use It

• Sprint ceremonies consume >20% of engineering time.
• Shipped work is reliably shallow despite good individual contributors.
• The roadmap has 2-3 projects worth 6 weeks of focused attention.
• A new engineering leader wants a cadence reset.
• Teams are burnt out from constant reprioritization.

Common Pitfalls

• Treating the pitch as a spec. Shape Up pitches are fat-marker sketches, not specs. Over-specification collapses the team's ownership.
• Swapping team members mid-cycle. Context switches kill cycles. If you must swap, restart the cycle clock.
• Extending past week 6. Unfinished at week 6 is a signal, not a problem. Ship partial or shelve — never extend.

Sources

• Shape Up — Basecamp
• Getting Real — Basecamp
• Sprint Planning — Atlassian
• Embracing Agile — Harvard Business Review