Build Less Deliver More

Stop Building Mansions When All They Need Is a Cottage

Agile taught us something powerful: Deliver value early. Deliver iteratively. Let users tell us when enough is enough.

Yet, with the rise of Spec-Driven Development (SDD), think GitHub’s Spec Kit, I see a risk of sliding back into a waterfall mindset, where we build everything users ask for just because AI makes it fast and easy.

The Reality Check

Here’s the reality:

• Most users only need 80% of the features they request.
• Building the other 20% adds complexity, bugs, and maintenance that nobody wants.
• Speed should never override value-driven prioritization.

The beauty of agile is in deployable sprints:

• Ship the core features first.
• Let users validate.
• Stop when the real need is met.

AI as an Accelerator, Not a License to Overbuild

Now, don’t get me wrong, I support Spec-Driven Development with AI agents. It’s a great accelerator. But here’s the key: break the spec into deployable sprints and work like a real development team would. Specs should guide us, not trap us in a “deliver everything upfront” mindset.

Just because AI can help us build faster doesn’t mean we should build more. Efficiency isn’t about doing everything; it’s about doing the right things. If we ignore this, we’ll end up with bloated tools that cost more to maintain and deliver less value.

AI should accelerate iterative delivery, not kill it.

The Question We Should Keep Asking

Let’s keep asking: What’s the smallest thing we can build that solves the problem?

How do you balance AI speed with agile discipline? Would love to hear your thoughts.