Rolling Rocks Downhill - in Installments

Posted by Deborah Hartmann Preuss on May 29, 2006

Sections

Process & Practices,

Architecture & Design

Topics

Quality ,

Software Craftsmanship ,

Stories & Case Studies ,

Leadership ,

Agile ,

TOC ,

Management

Clarke Ching's book-in-progress, Rolling Rocks Downhill explains why working in and managing software projects often feels like pushing rocks uphill, and shows how to use Lean, Quality and Agile techniques to make them easier, more productive and predictable.

Clarke's been very busy, he's published no less than seven chapters this month! Why is Clarke working so hard? Because he wants you to know that rolling rocks downhill is far easier than pushing them uphill.

In chapter 20 Steve discovers that software requirements are like forecasts. Forecasts - whether they be weather or sales forecasts - are invariably invariable (i.e. wrong). He learns about the shockingly high costs of building anything - be it cars or software - based on long distance forecasts. Waste, waste, waste.

In chapter 21 Steve contemplates working iteratively from the start of the project - just like they do in product development. But he's got one great big niggling doubt ...

As have other Agile authors, for example: Mike Cohn and Jim Coplien, Ching is building his book iteratively in public view. So, after reading a chapter or two, you can offer him feedback and join discussions with other readers.

Clarke is also the author of the article: What Software Development Projects Can Learn from the Quality Revolution.