The Devil's Guide to iT™ » agile

build an impression with version one

oldnick — Mon, 21 Jun 2010 15:07:25 +0000

Good developers understand the importance of building quality and functionality into a robust first release, while others regard version one simply as a public extension of the beta testing process; their strategy being: ship early/ often and fix on fail. The obvious weakness in such a ‘disposable’ product approach is that of ignoring the conjoint risks of poor first impressions and making a mess for valuable customers – risks that have grown since the advent of so-called ‘agile’ computing, which has simply formalised the practice of releasing under-developed software.

A free gift from the Devil: members of the Outer Circles can see a terrific illustration of this scenario, join the Outer Circles today at no cost

Do you want to make iT simpler and see more about this topic? I can help you but to protect the innocent minds of Wandering Souls, this enfermation can only be seen by registered members - try the Outer Circles to reveal a little more or join the Inner Circles to see everything.

make sure benefits are delivered

oldnick — Tue, 09 Feb 2010 17:00:38 +0000

Regardless of whether your programme/ project is working to either the traditional ‘waterfall’ or to the trendier ‘agile’ methodology, make sure that all contracted benefits are delivered.

agile

oldnick — Thu, 24 Sep 2009 19:55:25 +0000

a buzz-word, I’m afraid. Implies lots of jumping about and short attention spans. Proponents of so-called Agile development methods are evangelistic about the benefits of agile techniques. If you need time to think about your own agility, ask them: how many bridges are constructed using agile methods? That should buy you some breathing space. Of course. agile business is a reasonable ambition – so long as it is not achieved at the expense of resilience and rigour.