I’ve been thinking a lot lately about Mike Moran‘s most recent book, Do It Wrong Quickly (Quick note – I haven’t yet read the book, just a number of posts and reviews about it. It’s on my list, ok?). You can read the gist of the book on his site, but in 1 sentence taken from the description at Amazon:
“Moran shows how to quickly transition from plan then execute to a non-stop cycle of refinement.”
I have been noodling on something even before finding out there is a book all about it. Over the past few months I have been heavily involved in some large website development projects. This is a rather new thing for me – up until now I have been entirely in the Online marketing world where the development is quick and dirty.
What I have been thinking is that there is a lot to be said about developing and delivering a shiny, polished, finished product. On the other hand there is a whole lot more to be said about delivering finished components of a product in smaller, self-contained, working parts. You know why delivering the bits and pieces along the way is so great? Because they make you money. Oh, and they actually get done.
With those smaller components rolling out, you can start to glean the benefits much sooner than if you had to wait for the entire development cycle. At the very least you can get real working data. Yay data! Now you can find out what has to be incorporated in the future by actually using the product. You might even find out that the piece that was delivered was all that you needed, and you can stop working on useless features that creep in to big projects.
Whenever a project is finished or hits a major milestone I like to have an event to mark the accomplishment. Not much – a lunch, donuts in the morning, an afternoon off, that sort of thing. I find that these activities are much appreciated and are a great time to get closer to your team. When you break the large project up into say, 5 deliverable products – you get to have 5 lunches!
This is kind of the basis of Agile Development, right? Not lunches – easier communication with “the business” (that’s how my developers have started referring to me, quotes and all – sounds pretty mafia), quicker releases of smaller products, etc. So far I have seen great things come from this method.
What do you think? What are the benefits & drawbacks you have seen?
If you haven’t checked out Mike Moran’s Blog Biznology, please do. It’s well worth your time.