How It Differs from Agile, Scrum, and Shape Up

Build First sits in the same general family as modern iterative methodologies, but it takes a more radical stance on speed, structure, and what counts as real progress. To understand Build First, it’s useful to see where it diverges from the approaches that came before it

Compared to Agile

Agile was born as a rebellion against heavy, up-front planning. But over time, Agile in practice often became the very thing it was trying to replace: an ecosystem of rituals, roles, tickets, and ceremonies.

Where Build First diverges:

• No ritual overhead. Agile encourages fast iteration, but the real-world implementation often includes meetings, grooming, sprint planning, pointing, and workflows that slow small teams down. Build First removes these entirely.
• The build—not the user story—is the anchor. Agile orients around abstractions (stories, points, acceptance criteria). Build First orients around working software as the primary artifact.
• Fewer roles, fewer handoffs. Agile distributes responsibility across multiple specialized roles. Build First thrives with small, multi-disciplinary teams where design and engineering collaborate inside the build itself.
• Momentum over process. Agile optimizes predictability. Build First optimizes progress.

Compared to Scrum

Scrum formalizes Agile into a rigid operating system: sprints, backlogs, planning events, retros, velocity metrics. This works for large organizations that need coordination. It’s a tax for small teams.

Where Build First diverges:

• No sprints. Build First doesn’t time-box work into arbitrary cycles. Iteration happens continuously inside the product.
• No backlogs. The team focuses on what they’re building now, not managing an ever-growing list of ideas.
• No estimations or velocity tracking. Instead of predicting complexity, Build First reduces complexity by building the simplest version first.
• No role hierarchy. There are no product owners or scrum masters. The team owns the build together.

Scrum is great for organizing 40 people. Build First is great for moving 4 people.

Compared to Shape Up

Shape Up shares some DNA with Build First—especially around shipping meaningful slices of product and trusting small teams. But Build First takes a more fluid, hands-on approach.

Where Build First diverges:

• Build First starts with the build, not the pitch. Shape Up begins with a shaped pitch, followed by a 6-week cycle. Build First begins by building the thinnest possible working version immediately.
• Cycles are shorter and more flexible. Shape Up’s 6-week cycles and cooldowns are great for structured product teams. Build First favors quick iteration loops measured in days, not weeks.
• Design happens inside the working build. Shape Up encourages “fat marker” sketches up front. Build First encourages shaping through the product itself.
• Less ceremony around shaping. Shape Up prescribes a specific process for deciding what to build. Build First focuses on momentum and real-time decision-making.
• Geared for tiny teams. Shape Up works best when there’s a shaping layer (strategic thinkers) and a building layer (the team). Build First works when those layers are the same people.

In short:

• Agile is iterative, but often heavy.
• Scrum is structured, but slow for small teams.
• Shape Up is empowering, but still front-loaded.
• Build First is the simplest path to working software, with the least ceremony, optimized for teams who need clarity through building.

It’s a product methodology stripped down to its essentials:

start building, learn quickly, improve relentlessly.