- Hardcover: 320 pages
- Publisher: Wiley; 2 edition (October 10, 1997)
- Language: English
- ISBN-10: 0471292524
- ISBN-13: 978-0471292524
- Product Dimensions: 6.3 x 1.1 x 9.1 inches
- Shipping Weight: 1.2 pounds (View shipping rates and policies)
- Average Customer Review: 3.9 out of 5 stars See all reviews (15 customer reviews)
- Amazon Best Sellers Rank: #126,906 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Other Sellers on Amazon
+ $4.57 shipping
+ Free Shipping
Developing Products in Half the Time: New Rules, New Tools, 2nd Edition Hardcover – October 10, 1997
Frequently bought together
Customers who bought this item also bought
From the Inside Flap
Developing Products in Half the Time Second Edition New Rules, New Tools Preston G. Smith * Donald G. Reinertsen In this era of global competition and accelerating product life cycles, the need to get new products to market faster is more compelling than ever. What was once considered fast development is now commonplace. In 1991, the original edition of this book became an instant hit as the leading guide to reducing product development cycle time. The expanded set of tools in this new edition meets the needs of today's more demanding times. The book's premise remains solid: time is worth money, and if you quantify this value you can buy time wisely, often to enormous advantage. Rather than pursuing development speed at any price, the authors emphasize subjecting time-to-market decisions to the same hard-nosed business logic used for other management decisions. Developing Products is unique in providing tools for trading off schedule against other business objectives. It integrates powerful methods to manage risk and use resources effectively with proven techniques to accelerate product development. Smith and Reinertsen discuss hundreds of practical tools for reducing cycle time, describing each one's application and limitations. Countless examples including Black & Decker, Hewlett-Packard, Honda, Motorola, and others illustrate how real companies use the tools. With six more years of implementation experience and responses from readers of the original 60,000 copies, the authors have sharpened the original tools and added new ones. New topics include:
* Advanced tools for calculating the cost of delay
* A process for shortening the Fuzzy Front End
* Alternatives to co-locating a team
* How to effectively involve customers in developing product specifications
* The role of advanced technology tools in r apid development
* Metrics for projects and processes
* New methods for managing risk
* How to continuously learn from your development projects
The strategies in Developing Products in Half the Time apply to all companies and industries including software and electronics, medical devices, machinery and vehicles, and consumer goods. The authors show how leading companies no longer depend on only a few isolated tools but now integrate a broad array of methods to gain synergy and greater competitive advantage. This is the guide you will need in the trenches if time to market is important to you-or if you are wondering if it should be. It will be equally valuable to new readers and to those who must move beyond the original edition.
From the Back Cover
Advance praise for Developing Products in Half the Time Second Edition New Rules, New Tools Preston G. Smith * Donald G. Reinertsen "This is an exceptional book! Get a new highlighter before you start. There are so many 'ah ha's' in each chapter you will never make it through with an old one." Don LaCombe, Ford Motor Company, Product Development Process Leadership "An excellent book with a strong treatment of the cycle-time consequences of overloading your development capacity. It provides powerful and practical concepts for dealing with this issue." Andrew Aquart, Director Product Development, Cordis, a Johnson & Johnson Company "This is practical, useful stuff for people competing in highly competitive fast moving business." Dr. Paul Borrill, Chief Scientist, Sun Microsystems "3M has absorbed many of the tools from the original edition, and this new one will be even more useful. The topic of incremental innovation is crucial to us, and I really appreciate its balanced treatment." Ronald H. Kubinski, Manager New Product Commercialization Services, 3M Company "As the authors correctly point out, the Fuzzy Front End is the least expensive place to reduce cycle time. This book is one of the only sources of concepts, methods, and metrics for compressing this critical portion of the development process." David M. Lewis, Product Manager, Eastman Kodak Co. "Using these tools we've more than cut our time to market in half. The new edition of this classic crystallizes the synergy of the fast-to-market techniques, and the icons in the margins highlight the opportunities and pitfalls." Mike Brennan , Vice President of Product Development, Black & Decker
If you are a seller for this product, would you like to suggest updates through seller support?
Top customer reviews
I appreciated the books organization and approach because each of the tools can be consider by itself and at the same time the reader can consider the synergy between the tools. The explenations for the tools and their impacts are clearly explained, well researched, and where possible supported by quantitative data. For example when exploring the benefits of co-location there is a graph from a research project that shows how the amount of communication between team members decreases as the distance between them increases. With the tools and their potential impact so clearly laid out is easy to envision their practical application.
Preston Smith and Donald Reinertsen start the book by tackling some important misconceptions about fast development. Their opinion is that it's not per definition good and you really need to have a good reason to speed up the development. They continue this theme in their second chapter which gives a basic financial model that they will use during the rest of the book. It explains what trade-off will be made when saving time in a particular way. The rest of the book provides practices to save development time: starting with "the fuzzy front end". In power of incremental innovation they argue that most products can probably be developed incrementally, which reduces development time and risk a lot.
Chapter 7 and 8 are key to the book, they provide motivation for using cross-functional development teams. How to create these, how do they fit within the organization and where should you locate them. This concept is repeated probably most throughout the book.
Developing in half time is an excellent read. It's full of small ideas which can help your development process to deliver faster and explains the trade-offs well. The only criticism to this book would be that all topics are discussed only shortly. Recommended reading.
Keep an eye open specially to the tools listed below(number is the corresponding chapter) and watch the link with agile processes:
2. Putting a Price Tag on Time --> how to convince upper management to do small releases and work in an iterative and incremental mindset.
4. The Power and Pitfalls of Incremental Innovation --> Why to be agile and how to mitigate risks described in the disadvantages section.
5. Capturing Customer Needs --> Why to work jointly with all stakeholders and stay focused in minimal and iterative specifications.
6. Using System Design to Compress Schedules --> Why software architecture is an important activity and why projects must be planned based on architecture.
8. Organizing for Communication --> Why Co-location brings benefits most of the times.
10. Controlling the Process --> why insitute essential metrics and which are these. Aligned with information radiators practice of agile software development teams.
11. Preventing Overloads --> One of the best in the set. With great empirical evidence the authors explain why most managers do the wrong thing and try to mantain 100% people allocation. In this chapter he gives light to why is not a good thing to split people between various projects and what to do: control the project list religiously! The agile methodologies also say: Control the feature list of each project religiously :-) !
Read this book, if you want to understand why agile and iterative development processes are the way to build most software products out there!
Most recent customer reviews
Probably the worst text I've encountered for a course, never mind lacking useful information for...Read more