How can weeks of coding can save hours of planning?
Learn how identifying the causes of waste can lead to a more successful project overall.
In the context of Lean manufacturing there have been numerous studies that estimate that the proportion of value adding time in a production cycle is around 5%. The other 95% is deemed to be waste. These studies also conclude that by far the biggest waste is overproduction.
Anecdotally I think it is a very similar story in Software development although my fear is that the proportion of value adding time is even lower.
Waste takes many forms but broadly speaking effort as a team/company fall in to three areas:
- Valuable Effort – Value adding activities, these activities cost time and money, and there is a consequential opportunity cost but they add some value. However, the value may be able to be realized more effectively.
- Obvious Waste – Non-value adding activities that are evident. These activities cost time and money (and opportunity cost) but add no value to the product being created. Examples are vacation, breaks, sickness.
- Valueless Effort – Non-value adding activities masquerading as Valuable Effort, they cost time, money and have an opportunity cost but add no value to the product being delivered.
Waste reduction is not your goal
I will be covering the wastes in more detail, but it is very important that waste reduction is NOT the focus of your efforts, Waste Identification is a supporting activity for the Theory of Constraints, any efforts to improve a part of your system that is not the bottleneck is a waste in itself. But identifying waste can aid in your efforts to improve your bottleneck so is a great tool to support your other activities.
The 7 deadly sins
Lean identifies 7 wastes (recently adding an 8th Waste)
- Wasted Potential of People
Overproduction is considered the worst of the wastes and ultimately it is this particular waste that is the basis of much of the Agile Manifesto for Software Development. Which is why systems thinking is a topic I keep coming back to.
Agile is founded on the premise that at the start of the product we know the least and lack of flexibility is the biggest constraint in the success of software development. Traditional methods plan, create, test and support endless features that were unnecessary, the cost of this waste is unfathomable and big enough to trigger the Agile movement and challenge the way we work.
Overproduction was also the primary waste identified in the book “The Goal” by Eli Goldratt, and if you haven’t read that book I would heartily recommend it. The book is . great primer for the Theory of Constraints and for understanding Lean thinking.
Planning is waste?
But Agile has not completely fixed this problem, and in my experience development teams regular and persistently develop unnecessary features. With many teams choosing to work without sufficient time spent planning; story writing; prioritizing; and without consideration for whether the work they are doing adds any value now or more significantly adds the most value next.
Road mapping, planning and even story writing are often incorrectly perceived as ‘waste’ and the avoidance of waste is used as a justification to get back to coding on something that is likely not valuable and almost certainly not the most valuable activity to be worked on next, which is a far more insidious waste than the planning ever could be .
Features “not needed yet” are implemented on the basis that it will save time later, or features are added because “We know we will need it later” – (7 words I dread to hear.)
We work to look or feel busy, in our minds we translate activity as being productivity when there is little correlation between the two in the context of software development. In software, creativity; problem solving and planning are far more valuable efforts than unfocused coding.
In most cases features have no value until they are in the hands of a user and being used for productive effort. So any activity not spent getting the next most valuable feature into the hands of a user quickly is just waste.
Writing extra features that are not used or rarely used extends the production time but brings little or no value, it also compounds all of the other wastes because by it’s nature production of something of little value needs to go through the system thus exposing an unnecessary feature to all the other wastes.
When you next start work on something ask yourself: “Is this the next most valuable activity for our customer?” If you cannot confidently answer that question then maybe you need to spend more time planning so you can spend less time coding something that is not needed.
The worst case scenario
In software the biggest risk to any project is that it will be cancelled or obsolete prior to being used by your customers. This may sound obvious but if a project is cancelled ALL of the features are/were waste. All that effort produced no value for anyone. That time, effort and money could have been spent elsewhere. So getting your product right is only any good if you get your product delivered.
Delivering value to your customer quickly is the best way to mitigate the risk of your efforts being wasted, and "Done" is not really done unless it is in the hands of a customer and actually being used for a productive purpose.
Overproduction is a big topic and deserves a little extra focus, so I’ll delve deeper into the other wastes another time.