There has been a tendency to translate the seven wastes of manufacturing into wastes of software development. Not a bad start, but just that - a start. There are several things about software development that is not at all like product development in the physical world. These include:
The point is, we need a new list of wastes for software development. Here is a first cut:
Much of the source of the problem is doing too much work. There are two general ways of managing the work of a team:
Waterfall and pre-agile planning uses the first. All Agile methods use the second. The challenge is how does one get executives to understand that there is an inherent capacity of the teams and that this must be respected? From their perspective we need to provide the following information:
We’re trying to learn a better way. Undergoing a change can be hard on us, as well as the people we are providing services too. In situations like this, exposure into ones methods is always a good idea. Both for the teams to learn how to better work and for others to understand why the changes represent a true opportunity for improvement.
Note; The above is an excerpt from tomorrow's upcoming Product Portfolio Management: Why It is Critical for Agile at Scale - the second webinar of our Lean-Agile at Scale and at the Team: The Value Stream Series which, is itself, based on our Lean-Agile Software Development training.
CEO, Net Objectives