am 9. Dezember 1998
This is a treatise on management techniques, not process improvement. The first two chapters detail the decision of which projects to speed up, implying that a manager can only speed up a project by overstaffing it and clearing its path of the usual bureaucracy. Therefore, there is no permanent process gain to be had. But it is a great guide for decision makers looking to cut some time off any (or every) project. The fundamental tenets are these:
1) Make the decision to develop a new product idea quickly.
2) Staff all functions to the project immediately and keep them on throughout (no ramp-up, no handoffs)
3) Specify it simply and quickly and do not change the spec (3 days, 3 pages).
4) Spend a little time on the product architecture, designing for modularity and quick development.
5) User overlapping development techniques (work on multiple modules simultaneously)
6) Make a successful transition to manufacturing to complete the project.
You can halve the development time of most projects just by changing the way you manage your projects, without doing a lot of overtime or increasing the cost of development. Many of the answers are in this book. Again, this is a must read book for all development managers.
am 6. Januar 2000
Over 14 years of software experience confirmed alot of what this book offered. It's well written, chalked full of great facts and gives you a perspective on the possibilities for software development. Let's face-it, software development has almost zero manufacturing issues. So, if your looking for the real reason to implement processes and methodolgies into your development processes, this book will take you there.