Why Web Agencies Are Moving Beyond Scrum
For over a decade, Scrum has been the default project management framework in web development. Two-week sprints, daily standups, backlog grooming sessions, sprint retrospectives — the ritual became so embedded in agency culture that questioning it felt almost heretical.
But something has shifted.
A growing number of web agencies — from boutique studios to mid-size shops — are abandoning Scrum in favor of a methodology called Shape Up. Created by Basecamp (now 37signals) and formalized by Ryan Singer in his 2019 book, Shape Up proposes a radically different way to plan, build, and ship web projects.
The reasons for the switch are practical, not ideological. Agencies are tired of sprint fatigue, pointless velocity metrics, and the constant overhead of ceremonies that consume 20–30% of a developer’s week. Shape Up promises something refreshing: fewer meetings, clearer boundaries, and more meaningful work.
Let’s break down what Shape Up actually is, how it compares to Scrum, and why it might be the right fit for your agency or your next web project.
What Is Shape Up? A Quick Overview
Shape Up is a project management methodology built around three core concepts:
- Shaping — Senior people define the work at the right level of abstraction before handing it to a team.
- Betting — Leadership “bets” on shaped pitches during a betting table session, committing resources for a fixed cycle.
- Building — A small team (typically 1 designer + 1–2 developers) works autonomously for a 6-week cycle to deliver the project.
After each 6-week cycle, there is a 2-week cooldown period. During cooldown, teams fix bugs, explore new ideas, or work on personal technical interests. This rhythm — 6 weeks on, 2 weeks off — creates a sustainable cadence that prevents burnout.
The Shaping Phase: Where Strategy Meets Design
Shaping is arguably the most important — and most misunderstood — part of Shape Up. It happens before any development work begins.
During shaping, a senior strategist, product manager, or technical lead defines:
- The problem to solve (not the solution)
- The appetite — how much time the project deserves (e.g., 6 weeks, or a smaller 2-week “small batch”)
- Rough boundaries — fat-marker sketches, not pixel-perfect mockups
- Rabbit holes — known risks and edge cases to explicitly exclude or address
The output is a pitch document — a short written artifact that gives the build team enough direction to start, but enough freedom to find the best solution.
This is a fundamental departure from Scrum, where user stories are often written in isolation and refined ad infinitum in backlog grooming sessions.
The Betting Table: No More Infinite Backlogs
In Scrum, the product backlog grows endlessly. Items pile up, priorities shift, and teams spend hours each week grooming stories that may never see a sprint.
Shape Up eliminates the backlog entirely. Instead, shaped pitches are brought to a betting table — a short meeting held before each 6-week cycle. Leadership reviews the pitches and decides which ones to bet on.
Pitches that don’t get selected are simply discarded. If an idea is important enough, it will come back. This forces discipline: only well-shaped, strategically important work gets built.
Shape Up vs. Scrum: A Detailed Comparison
Let’s put the two frameworks side by side.
| Dimension | Scrum | Shape Up |
|---|---|---|
| Cycle length | 1–4 weeks (typically 2) | 6 weeks + 2-week cooldown |
| Planning unit | User stories / story points | Shaped pitches with appetite |
| Backlog | Persistent, ever-growing | No backlog — pitches are bet or discarded |
| Daily standup | Required (15 min/day) | None — teams communicate asynchronously |
| Roles | Product Owner, Scrum Master, Dev Team | Shapers, Betters, Build Team |
| Estimation | Story points, velocity tracking | Appetite (fixed time, variable scope) |
| Scope management | Scope is fixed, time is estimated | Time is fixed, scope is flexible |
| Progress tracking | Burndown charts, sprint boards | Hill charts (uphill = figuring out, downhill = executing) |
| Autonomy | Moderate — PO prioritizes daily | High — team owns decisions within appetite |
| Meeting overhead | 20–30% of work time | < 5% of work time |
The most radical difference is the inversion of scope and time. In Scrum, you estimate how long a set of features will take. In Shape Up, you decide how much time you’re willing to spend (the appetite) and then adjust scope to fit.
This single shift eliminates the most toxic dynamic in agency work: endless negotiations about estimates that turn out to be wrong anyway.
Why Shape Up Works Better for Web Agencies
Scrum was designed for product teams working on a single product indefinitely. Web agencies operate differently. They juggle multiple clients, fixed budgets, and hard deadlines. Here’s why Shape Up aligns better with this reality.
1. Fixed Budgets Map Naturally to Appetites
When a client comes to an agency with a budget of €25,000 for a PrestaShop e-commerce store, that’s essentially an appetite. Shape Up’s model — fixed time, variable scope — mirrors how agencies already think about projects. You decide what can be delivered excellently within the budget, rather than promising everything and then negotiating scope reductions mid-sprint.
At Lueur Externe, a certified PrestaShop agency based in the Alpes-Maritimes, this appetite-driven approach has proven particularly effective for e-commerce builds where clients need reliable delivery timelines without sacrificing quality.
2. Fewer Meetings, More Building
A typical Scrum week includes:
- 5 daily standups (75 min/week)
- 1 sprint planning session (2–4 hours)
- 1 backlog grooming session (1–2 hours)
- 1 sprint review (1–2 hours)
- 1 sprint retrospective (1–1.5 hours)
That’s 7 to 12.5 hours per week spent in meetings — for a 2-week sprint. For a small agency team of 4 people, that’s potentially 50 hours of collective meeting time per sprint.
Shape Up replaces all of this with:
- A betting table meeting once every 8 weeks (~2 hours)
- Asynchronous check-ins via hill charts
- Ad hoc conversations as needed
The math is simple. More building time means faster delivery and higher margins.
3. Hill Charts Replace Burndown Anxiety
Scrum’s burndown chart creates a perverse incentive: teams optimize for closing tickets rather than solving problems. A sprint can “succeed” by its metrics while delivering a mediocre product.
Shape Up introduces hill charts — a visual metaphor where each scope of work moves along a hill. The left side (uphill) represents the figuring out phase: exploring unknowns, making key decisions. The right side (downhill) represents execution: the path is clear, and the team is cranking through known work.
Here’s what a hill chart looks like conceptually:
/\
/ \
/ \
/ \
/ Figuring\ Execution
/ it out \---------->
/ \
---/ \---------
Scopes: ● Product page redesign [====> ] (uphill, 60%)
● Checkout flow [============>] (downhill, 90%)
● Search integration [=> ] (uphill, 20%)This gives stakeholders and clients an honest, intuitive view of progress — far more useful than a percentage-complete bar.
4. Small Batch Projects for Maintenance and SEO
Not everything is a 6-week project. Shape Up accommodates this with small batch cycles — groups of smaller 1–2 week tasks that fit into the same 6-week window.
For agencies managing ongoing SEO, WordPress maintenance, or performance optimization, small batches are ideal. You can dedicate one or two developers to a small-batch cycle that includes:
- Core Web Vitals improvements
- Schema markup implementation
- Security patching
- Content migration tasks
This structure ensures maintenance work gets dedicated, focused time rather than being squeezed between sprint stories.
How to Implement Shape Up in Your Agency: A Practical Guide
Transitioning from Scrum to Shape Up doesn’t have to be a big-bang change. Here’s a phased approach.
Phase 1: Start with Shaping (Weeks 1–2)
Before changing anything about how your team builds, change how you define work. Take your next project and write a pitch instead of user stories.
A good pitch includes:
- Problem statement — What pain are we solving?
- Appetite — 6-week or small batch?
- Solution sketch — Fat-marker wireframes, not detailed mockups
- Rabbit holes — What could go wrong? What are we explicitly NOT doing?
- No-gos — Clear boundaries so the team doesn’t drift
Phase 2: Run a Pilot Cycle (Weeks 3–8)
Pick one team and one project. Run a full 6-week cycle using Shape Up principles:
- No daily standups
- No sprint planning
- Team updates via hill charts (you can use Basecamp, or simulate in Notion/Linear)
- Check-ins twice a week maximum
Measure the results: delivery quality, team satisfaction, client feedback, actual hours worked vs. Scrum equivalent.
Phase 3: Introduce Cooldown (Weeks 9–10)
After the first build cycle, give the team a genuine 2-week cooldown. Let them:
- Fix technical debt
- Experiment with new tools (e.g., testing a new deployment pipeline on AWS)
- Write documentation
- Prepare pitches for the next cycle
This cooldown period is not optional — it’s what makes Shape Up sustainable long-term.
Phase 4: Scale Across the Agency
After 2–3 successful cycles, bring other teams on board. Establish a regular betting table cadence. Train senior staff on shaping. Document your adapted version of Shape Up — because every agency will customize it to some degree.
Common Objections (and Honest Answers)
“Six weeks is too long for client projects.”
Not every project needs 6 weeks. Shape Up’s small batch cycles handle 1–2 week tasks. And for larger projects, 6 weeks with a cooldown is actually shorter than three 2-week Scrum sprints (which take 6 weeks but include 12+ hours of meetings per sprint).
”Clients want to see daily progress.”
Hill charts provide a more honest and visually intuitive progress report than a Jira board full of tickets in various states. Most clients, once they understand the hill chart model, prefer it because it answers the real question: “Are we stuck or are we shipping?"
"We need story points for billing.”
No, you need time tracking for billing — and time tracking is independent of your project methodology. Shape Up actually makes billing simpler because the appetite is set upfront. You’re billing for a 6-week engagement, not arguing about how many story points constitute a “sprint."
"What about bugs and urgent requests?”
During a build cycle, genuine emergencies are handled by an on-call rotation — not by the build team. Non-urgent bugs go into the next cooldown or small-batch cycle. This boundary protection is essential for maintaining flow.
Real-World Results: What Agencies Report After Switching
While large-scale industry surveys are still emerging, the anecdotal evidence from agencies that have adopted Shape Up is compelling:
- 30–40% reduction in meeting time, freeing developers for actual coding
- Higher team retention — developers consistently report preferring the autonomy of Shape Up
- More accurate delivery timelines — the appetite model reduces the “estimation theater” that plagues Scrum
- Better client relationships — shaping forces agencies to have strategic conversations upfront, which clients value
Lueur Externe has integrated Shape Up principles into its workflow for WordPress and PrestaShop projects, combining them with its deep technical expertise in AWS infrastructure and SEO optimization. The result is a delivery process where clients get clear commitments, and developers get the focused time they need to build excellent work.
Tools That Support Shape Up Workflows
You don’t need specialized software to run Shape Up, but some tools align better with its philosophy:
- Basecamp — The native home of Shape Up. Built-in hill charts, to-dos, and asynchronous communication.
- Linear — Modern issue tracker with cycle support that maps well to Shape Up.
- Notion — Flexible enough to build pitch templates, betting tables, and hill chart tracking.
- Shortcut (formerly Clubhouse) — Supports iterations and milestones that can mirror 6-week cycles.
- Plain documents — Honestly, a shared Google Doc for pitches and a whiteboard for hill charts can work for small teams.
The tool matters far less than the discipline of shaping, betting, and protecting build time.
Conclusion: Is Shape Up Right for Your Next Project?
Shape Up isn’t a silver bullet. It requires senior people who can shape well. It demands discipline around the betting table. And it asks teams to embrace discomfort — working without a detailed roadmap and figuring things out as they go uphill.
But for web agencies tired of Scrum’s overhead, frustrated by estimation theater, and looking for a methodology that respects both client budgets and developer sanity, Shape Up is worth serious consideration.
The framework’s core insight is profound in its simplicity: fix the time, flex the scope, and trust your team. When you combine this with strong technical shaping — understanding what’s feasible on PrestaShop, what WordPress can handle natively, how AWS infrastructure affects architecture decisions — you get projects that ship on time, on budget, and at a level of quality that keeps clients coming back.
If you’re considering adopting Shape Up for your next web project, or if you want to work with an agency that already applies these modern project management principles, Lueur Externe can help. With over 20 years of experience building e-commerce stores, WordPress sites, and custom web solutions, the team at Lueur Externe combines cutting-edge methodology with deep technical expertise.
Get in touch with Lueur Externe → to discuss your next project and discover how a smarter workflow can deliver better results.