[The links in this recap all point to previous entries. It is a recap after all.]
The Problem is that software projects still deliver an unacceptable level of quality and responsiveness. Part of the reason for this is the industrial-era Scientific Management approach. Part of the reason for this is the progamming culture that grows up around a language.
Lean software development provides information-era Lean management: Reduce Cycle-time and start expecting zero defects.
But the cultural issues and organizational structures remain extraordinarily difficult to deal with. Some hope may be appearing in a new programming language (and more importantly programming culture) Ruby. Which includes in it's libraries and way of development, new technologies that are merely bolted onto J2EE (and .NET).
The promise of applying Lean-Thinking to Software development is available now. It consists of a Lean Business Model, combined with Agile Processes and a deeply Object Oriented environment and culture. All these parts are currently available.
Knocking the competition for a loop, only requires putting them all together.
How hard can that be ?
