6 Myths of Product Development
This is a very useful article in the HBR, by Stefan Thomke and Donald Reinertson. Reinertson is well known in the lean-agile community. It is excellent. Go here to buy it for $6. Well worth it.
Here are the myths or fallacies they mention:
1. High utilization of resources will improve performance.
By ‘resources’ they mean mainly people. Speed of delivery is much more important.
2. Processing work in large batches improves the economics of the development process.
Instead, small stories in small sprints gets fast feedback from business stakeholders.
3. Our development plan is great; we just need to stick to it.
For many reasons, during the course of ‘development’, the needed features will change. And other things will change. Hence, the plan must also change. That’s ok, or at least, that’s the nature of innovation work.
4. The sooner the project is started, the sooner it will be finished.
Reduce WIP. Stop starting, and start finishing.
5. The more features we put into a product, the more customers will like it.
Deciding what to omit is as important as deciding what to include.
6. We will be more successful if we get it right the first time.
Demanding that teams “get it right the first time” just biases them to focus on the least-risky solutions.
This article is good for helping managers see what lean-agile-scrum is all about.