Why is iterative development motivating?

If you ask a handful agile developers why they work in iterations or sprints, most of them will tell you that they help them predict how long their work will take. While that's true, it isn't necessarily the most important benefit. To put it bluntly, I get more done when I work in iterations.

It's about commitment.

When planning a new iteration I only include as much work as "yesterday's weather" suggests I ought to be able to complete. In other words, I schedule as much work as I completed in the previous iteration.

If your estimates are consistently accurate (or consistently inaccurate, which is just as good) then your iteration represents a feasible goal; I know I can achieve it. I make a private commitment (just to myself) to deliver it.

The feeling that I really ought to be able to get everything done helps to keep me going. It also keeps me focussed and on track; when I'm working on my own there's nobody looking over my shoulder to point out when I'm about to disappear down a rabbit hole. Being aware of my progress through the iteration provides a good substitute.

Some might suggest that I'm using iterations like todo lists, but there's an important difference.

A traditional to-do list is not a commitment. It may feel safe to add every potential activity there, including things that other people push on you. The list is long, and the continuous inward flow ensures that all activities can't possibly ever be done. Without commitment, there is less motivation. It's really not an achievement to complete and remove one line from an inventory that is still enormous. -- Staffan Nöteberg

The quote is from Pomodoro Technique Illustrated from the Pragmatic Programmers. The Pomodoro technique has a lot in common with agile development. I use Pomodoros to keep my days focussed, and iterations to keep me working towards the bigger picture.

As a lone startup founder it can be difficult to sustain your motivation, but once you've felt the satisfaction of doing a solid day's work you'll want to repeat it tomorrow. It's the same with iterations; after delivering a solid fortnight's work I can see my progress. It's real. It's tangible. And I want to repeat it...

About the author

Graham Ashton

Graham Ashton is an experienced agile team leader and project manager, and the founder of Agile Planner. You can follow him at @grahamashton on Twitter.