Agile Project Planning

ExtremePlanner: Agile Project Management for Distributed Software Teams
Click For Your Free Online Trial

Monday, March 05, 2007

Small Wins: Agile Psychology

There are many theories as to why Agile methods work.

I'd like to suggest that a very small core element is responsible for much of the energy and ultimately the success of Agile development projects:

Small wins create momentum. Continous small wins create tremendous momentum.

OK, but what kinds of small wins are important in software projects?

  • How about early positive feedback from customers?

  • Or early clarification of an important feature (that leads positive feedback later)

  • Early detection and resolution of defects before they lead to not-so-positive feedback.

  • Early proof that you can build and deploy the software somewhere other than your own machine

These types of small wins have a subtle, but critical effect on everyone on the project team. Developers feel valued and are motivated to continue satisfying the customer. Customers feel heard and in control, and begin to develop trust for the development team. Stakeholders see regular progress, and begin to feel less anxious about project outcomes. Testers get an early look at the software, and are able to add value much earlier than in typical projects.

I went on a hike a few months ago that was basically an entirely uphill climb. There were no real twists or turns, just a straight incline. After about an hour on continuous climbing, I just gave up. This was partly because I was exhausted, but also because I had no idea how much further it was to the top. There were no clear indicators of progress, nothing to feel good about, just more turns of the road, and nothing but up to look forward to.

Similarly, software projects that offer no short-term wins can be depressing. Even the best team can feel unmotivated and lose steam when the project drags on and on without feedback, interim releases, or other signs of progress.

Agile methods promote frequent delivery and rapid feedback. For me, this isn't just a nice-to-have side effect, it's the only sustainable way to create great software.

Labels: ,

Get your copy of the new book! Agile Thinking: Leading Successful Software Project and Teams

3 Comments:

  • I agree 100%.

    Having sorted out technical reasons for team failure, the motivation is probably the one most important. There's nothing worse than going home for a weekend and think about having to continue next week the "same crappy job". The feeling of achievement is indispensable. In the "divide and conquer" paradigm we always recall divide, but rarely really conquer :-)

    By Blogger wheelREinventor, at 12:09 AM  

  • Great description of the multi-faceted importance of frequent review and retrospect. One of the reasons I frequently take the time to "look back" when I am on a hike - to see where I have come and give me that positive feedback - similar to a sprint retrospective.

    However, if the "trees" are preventing you from seeing where you have come, if you create a simple roadmap (release burn down)and frequently review progress towards it, it may help give visibility when there is no other outside feedback.

    Thanks for the post.
    Pete

    By Anonymous Pete Behrens, at 12:31 PM  

  • i agree. Especially when the client is happy and pleased with the work done

    By Anonymous Andreas, at 7:15 AM  

Post a Comment

Links to this post:

Create a Link

<< Home