Japan's Software Factories: A Challenge to U.S. Management

Rating:
Summary: Software factories now in India?
Review: The explanation for what happened to Japanese software factories is in Cusumano's latest book, The Business of Software, which is a more valuable read. The Japanese factories tried to solve the problem of efficiently building custom systems for Japanese customers using mainframes. Cusumano still argues that the factory approach worked well for mainframe software but Japanese programmers didn't have the skills to shift to newer platforms (PCs, workstations). I think the author over-estimated what the Japanese would be able to do. The Japanese are still struggling with old-style development techniques, despite close to zero-bugs, according to recent data from Cusumano. The Indians adopted similar practices (standard dev techniques, reuse, statistical data) but with much better trained people, more adaptable processes, and have been able to handle a wide variety of systems requirements and technologies. I still find Japan's Software Factories a useful look at how Japanese and some U.S. companies made progress in software engineering, particularly their approach to quality control and testing, and reuse. The Indians have gone a step beyond Japan, but they had to start somewhere.

Rating:
Summary: Cusumano's initial misconceptions about software
Review: This is one of the earliest in a series of books that Cusumano has written on software technology. In this book he cries "Wolf!": the Japanese are so much better at industrial strength software development than Americans, they have a "software factory", etc., etc.

In his subsequent books, especially those on Microsoft and Netscape, Cusumano slowly discovers that the traditional software development process, requirements/specifications/code, etc., e.g. the waterfall model, is *NOT* the model adopted by successful software companies (and, indeed, not the model adopted by many hardware companies). He learns that designs are not something to be churned out by a factory - indeed, if they can be churned out, then they should be reusing exactly the same software.

In some ways the packaged software industry, e.g. Microsoft, supplanted the custom software industry in this timeframe, the time of the PC; Microsoft's process, which Cusumano calls "synchronize and stabilize", may be considered to be JIT (Just In Time) software specification and development. Or, if not Just In Time, As Soon As Possible and No Earlier than Necessary.

While I cannot agree with the conclusions of this book, it is interesting to have on one's bookshelf, to see the evolution of the author's thought over time.

Rating:
Summary: Cusumano's initial misconceptions about software
Review: This is one of the earliest in a series of books that Cusumano has written on software technology. In this book he cries "Wolf!": the Japanese are so much better at industrial strength software development than Americans, they have a "software factory", etc., etc.

In his subsequent books, especially those on Microsoft and Netscape, Cusumano slowly discovers that the traditional software development process, requirements/specifications/code, etc., e.g. the waterfall model, is *NOT* the model adopted by successful software companies (and, indeed, not the model adopted by many hardware companies). He learns that designs are not something to be churned out by a factory - indeed, if they can be churned out, then they should be reusing exactly the same software.

In some ways the packaged software industry, e.g. Microsoft, supplanted the custom software industry in this timeframe, the time of the PC; Microsoft's process, which Cusumano calls "synchronize and stabilize", may be considered to be JIT (Just In Time) software specification and development. Or, if not Just In Time, As Soon As Possible and No Earlier than Necessary.

While I cannot agree with the conclusions of this book, it is interesting to have on one's bookshelf, to see the evolution of the author's thought over time.