In this recent post from Tim Huegdon sharing some of his insights and discoveries about eliminating waste from your development process (with props to the methods introduced by the Toyota Corporation and the Poppendiecks).

Eliminating waste is the first - and most fundamental - principle of Lean Software Development; something that was introduced to me by an exceptionally talented Project Manager whom it was my pleasure to work with. Lean Software Development is a set of seven fundamental principles that really work hand in hand with agile development to improve software delivery.

He introduces the concepts behind the "lean" mentality, where it's origins came from (Toyota) and how it relates to software/web development. He points out some of the places that waste can come from in development including:

• Partially complete work
• Extra features
• Task switching
• Waiting
• Defects

For each of these (and a few more) he summarizes what they're all about and some of the things that can be done to help combat them.

Giorgio Sironi has posted a two part look at some techniques you can use to eliminate the singletons scattered through out your code (as sparked by the recent announcement that the Zend Framework project will be doing the same thing).

It is actually very simple to eliminate singletons: just force the components to ask for what they need in the constructor or via setters or via inject*() methods, instead of looking up a singleton trough a static method only to obtain a reference. Once this fundamental decoupling is achieved, the hard part is tackling the construction problem.

In the first part of the two, he looks at a Zend Framework example of how to replace a certain piece of code with injected instances of required objects. In the second part he refines it down a bit more and only inject/create the objects and resources as needed.