Lean Product Development is the right approach for software development
Toyota can bring new products from initial concept to the production floor in 18 months while other manufactures may take twice as long. Some software companies seem to have a knack for understanding what customers really want while others go through many versions to get something that merely works.
What is the difference? Their approach to new product development.
Toyota discovered that applying lean principles to the development and design of their products is somewhat different from lean applied to production and manufacturing. The goals are different and so the application of the tools is different, too.
Michael Kennedy describes product development as “the collective activity or system that a company uses to convert its technology and ideas into a stream of products that meet the needs of customers and the strategic goals of the company.” Product development is process of discovery. Discovering what customers desire and need and then designing product that will meet that. Indeed, perhaps 70% - 80% of a product’s cost lies in this discovery process; the production is relatively straightforward.
In this show, Alan Shalloway argues that this is also true for software development. The process of discovery of what customers desire and need is by far the largest contributor to the cost of the software product. Therefore, learning how to apply the principles of lean product development to software development is essential to an effective software development process.
Elements of Lean Product Development include:
Software lives in the larger context of the business. Lean helps set the context in which software fits in the business.
Before the how, we have to understand the why.
Recommendations - Training by Net Objectives
Recommendations - Reading
Music used on this podcast:
For more informaiton, send us an e-mail at info@netobjectives.com or visit www.netobjectives.com