by oneafrikan on July 20, 2005
In mid 2002 I was asked if I wanted to do a couple of days consulting for a client who wanted to create a small e-learning tool using Microsoft Content Management Server. I%u2019d just finished working on two consecutive MS CMS projects, so I didn%u2019t think a third would really hurt. The term a %u201Ccouple of days%u201D is almost legendary now; as the project actually lasted 18 months and mutated from a %u201Csmall e-learning tool%u201D to a large localised e-learning tool that had tens of thousands of users and was deployed globally. It was a tough gig, but ultimately one of the most rewarding projects I%u2019ve ever worked on and possibly the one that has the fondest memories.
This is a really good view of what an Agile project could and should look like, although obviously at the time it wasn’t called that. A good read if you’re looking for real world examples / descriptions of Agile development, as well as what it should look like from a developers point of view. Take home is the importance of having business buy in to ensure that the project succeeds, and managers that know how to let developers develop without getting in the way.