Agile Development: Embracing Change

By · April 17, 2013 · Filed in Agile and Project Management Series

I cannot say whether things will get better if we change; what I can say is that they must change if they are to get better.

Georg C. Lichtenberg (scientist, satirist)


The heart of Agile development is change

If you can only change one thing about the way your organization develops and delivers products (and you can!) change the mindset that projects will be successful if we just get better at defining our big up front requirements and tightening our management of change. It not only can’t be done … it shouldn’t be done.

The time when you know the least about what is required in order to have a successful product is at the beginning of the project; when you are first articulating requirements.

If change is to be avoided at all cost, what should you do with the knowledge gained throughout the course of the project?

  • Learn something about your users/customers…just ignore it?
  • Find a more efficient way to complete a task…oh well?
  • Surprised by a competitor’s cool new feature…good for them?

Nonsense! So why do we let our legacy governance models stop us from doing the right thing, the smart thing, the only thing worth doing with new, important information…i.e. responding as soon as we can?

So rather than have your internal processes throttle, impede or even prevent change you should, for the good of your organization, modify those processes so that they nurture, support and even invite change. This is the heart of any good agile methodology.

Need help getting started? There’s a contact form right over there in the sidebar…