← All articlesProject delivery

Short iterations: clients get to know a system by touching it

The most expensive surprise in a project is the one that appears at the end. That is why I work in short iterations and show working features every week or two. Here is what that looks like and why a change of scope along the way is not a problem but information.

An iteration is one or two weeks

I split a project into short stages, usually one or two weeks long. Each ends with something that works and that the client can check for themselves: a new screen, a process, an integration. Not a presentation or a progress report, but a piece of the system.

Why so often? Because quick feedback immediately shows whether the work is heading in the right direction. If we understood something differently from what the client had in mind, we lose a few days on it, not a few months.

You get to know a system by touching it

My projects show one recurring pattern: clients often start to “feel the system” only when they can use it. It does not have to be the finished whole. The first working features already show where we are heading and raise questions nobody asked at the specification stage.

That is not the client’s fault. A system described on paper and a system you click through are two different things. Short iterations simply use this effect instead of postponing it to the end of the project.

A change of scope is information, not a problem

Changes along the way are possible and normal. Thanks to short iterations we learn about them quickly, before the team builds something that will have to be reworked. This applies to both sides: the team also discovers things along the way that could not be foreseen at the start.

After each iteration we agree together on what matters most in the next one. The client decides the priorities, the team says how much can be done. This way the budget goes to features that are really needed, not to those that seemed important six months earlier.

What one iteration looks like

  1. Planning: we pick the tasks for the next week or two and agree on what should work at the end.
  2. Team work: a short daily meeting helps catch obstacles quickly.
  3. Demo: we show the client working features in a test environment.
  4. Takeaways: feedback from the demo goes into the plan for the next iteration.

Let’s talk about your project

Tell us briefly what you want to build or fix.