Agile means building software in small, finished slices and showing them to you every week or two, so the plan can change while changing it is still cheap. That is the entire idea. Everything else, the standups, sprints, backlogs, story points, is machinery in service of that one goal: short feedback loops instead of a big reveal at the end.
The vocabulary, translated
- Sprint: a fixed work period, usually one or two weeks, ending in something you can see working.
- Backlog: the ordered to-do list. The top is what happens next; the bottom is honest maybes.
- Standup: a short daily sync on progress and blockers. Fifteen minutes, not a meeting.
- Demo or review: the team shows you working software. Not slides. Software.
- Retrospective: the team asks what to do differently next sprint.
Why agile exists: the failure it prevents
The old model gathered every requirement upfront, disappeared for eight months, and delivered exactly what you asked for in January, which is never what you need in September. Agile assumes the plan is partly wrong on day one and builds in the correction: every demo is a chance to steer. For a founder, the practical benefit is enormous: you find out in week two, not month eight, that the developers understood something differently than you meant it.
What agile is NOT
Agile is not "no plan, we will figure it out," and it is not a license for endless open-ended billing. This matters when you are the buyer: "we work agile" is sometimes used to mean "we cannot tell you what it costs or when it ships." A competent team can work in agile slices inside a fixed scope and budget: the slices change order, the destination does not drift unexamined.
The warning signs, from the buyer's chair
- Weeks pass with no demo of working software. The loop is broken; you are back to the big reveal.
- Every conversation adds scope and no conversation removes any. Healthy agile trades: something in, something out.
- You hear about velocity and story points but cannot answer "what can a user do today that they could not do last month?"
- The team resists writing anything down. Agile values working software over exhaustive documents, but decisions and scope still get written down by professionals.
What to actually ask for as the client
Ask for a demo every week, a visible backlog you can read, and a definition of done for the current milestone. Attend the demos and be decisive in them: the whole method depends on your feedback arriving while it is cheap to act on. Skip the ceremonies if you like, but never skip the demos. A founder who watches fifteen minutes of working software each Friday cannot be surprised at the end, and that is the entire point.