10 March 2009

Iterations and the value payoff

A simple presentation on the increased value you get fron iteative approaches to software development.

This is not a deep, evidence based moel - it's more a simple principle based view of how value is earned faster. (It's part of the agile dogma, in fact.)

It's posted here because it's a potentially useful communicatio tool when arguing for iterative development.


  1. Anonymous8:31 am

    This approach of course requires the business be able to accept the incremental and iterative releases from the agile time.
    In our experiences in enterprise IT this is problamatic in many instances. Billing is one example. On the other hand Enterprise Customer Service is a natural for incremental releases. Claims process is on the opposite end - fixed verified and validated releases.
    The conjecture - and its a credible conjecture - that agile provides increased value over macro-level point releases needs a context and a domain.

  2. Like any Agile advocate, I'm a big believer in the short iteration cycle. I like to think of it as closing the feedback loop to accelerate learning how best to satisfy the need. As to what galleman said about getting acceptance, you might want to take a look at this lecture that I gave at Brooklyn College.

  3. Glenn

    You are right; there are some tough issues - around billing as a vendor and budgeting for in house projects.

    It's a process change that has some fundamental affects on the sponsors and senior mangement as well as the developer team.

    We are (I am) still wrapping it with a formal business case, set of estimates and broad scope statement.

    I think in the second budgeted year we might test their responiveness to a more incremental budgeting approach.

  4. Plone (Glenn?)

    I liked your presentaion. Some interesting thoughts.

    Would you care to post it up to slideshare and I'll post/comment here.

  5. See this post by Rowan Bunning on budgeting for scrum within standard financial processes