Lean Software Strategies: Proven Techniques for Managers and...

Features

• Cover Type: Hard Cover with 468 pages
• Published by: Productivity Press
• Edition: 1st Edition May 27, 2005
• Written in: English
• ISBN 10 Number: 1563273055
• ISBN 13 Number: 978-1563273056
• Book Dimensions: 9.1 x 6.3 x 1 inches
• Weighs: 1.6 pounds

Product Review
--Richard S. McCabe, Principle Member Technical Staff,, Systems and software Consortium, Inc. 03/18/05



Outstanding! A must read for software practitioners and technical leaders concerned with incorporating integrity and positive attributes into integrated systems design.



Middleton and Sutton offer an innovative treatment of lean production for software, describing how several development teams have effectively integrated many advanced techniques of software engineering. This provocative interpretation of lean thinking should interest anyone who is trying to improve software development for complex systems.

Review by Lisa Crispin: "This book is a soup-to-nuts explanation of lean production, why it should be applied to software production, and how to apply it." -- StickyMinds.com, February, 2007

Product Description

Winner Of The 2007 Shingo Prize For Excellence In Manufacturing Research!

Lean production, which has radically benefited traditional manufacturing, can greatly improve the software industry with similar methods and results. This transformation is possible because the same overarching principles that apply in other industries work equally well in software development. The software industry follows the same industrial concepts of production as those applied in manufacturing; however, the software industry perceives itself as being fundamentally different and has largely ignored what other industries have gained through the application of lean techniques.

Lean software Strategies: Proven Techniques for Managers and Developers, shows how the most advanced concepts of lean production can be applied to software development and how current software development practices are inadequate.

Written for software engineers, developers, and leaders who need help creating lean software processes and executing genuinely lean projects, this book draws on the personal experiences of the two authors as well as research on various software companies applying lean production to software development programs.

Reader Reviews
It would be pure gold like this one. This book won the Shingo Award: http://bigblue.usu.edu/shingoprize/AboutUs/index.htm. The selection committee clearly knew what it was doing. The author has created an excellent exposition of how lean manufacturing methods can be applied to create abstract intellectual assets such as software and, by implication, systems engineering plans and designs. Overall the book is an excellent, well written discourse on lean methodology with numerous examples of its application. The authors explain in clear detail how best to apply several lean tools to plan and to perform major systems and software projects, e.g., TRIZ, Analytic Hierarchy Process, SCR, Blitz QFD, Theory of Constraints, Agile practices, high integrity UML, language selection to support lean production (SPARC Ada), load leveling, and Kano Modeling. The cases where this approach was used provide consistent evidence of success; software productivity was significantly improved over previous practice by roughly a factor of four even though the requirements churn in those same contracts was significantly higher than in other successful projects. It is critical to note that software production was stabilized against serious requirements instability by the lean practices being described. Further, that stabilization was a major contributor to successful completion of the contracts! In the first few chapters, the author spends some time explaining the niche in which lean methods live and work most effectively. In chapter 5 the author analyzes the SEI's Software CMM model to determine the manufacturing paradigm for software. One should note that, since the publication of the book, the Software CMM has been replaced by a newer model, the Software/System/etc CMMI that addresses several of the lean concerns: http://www.sei.cmu.edu/cmmi/. After some thought it is clear that the fundamental criticism of the Software CMM is that the implementation of any business model by practitioners of the manufacturing paradigm is the principle problem. Such practitioners will likely take a relatively low risk, evolutionary, incremental approach to introduce change. They will therefore initially implement a set of organizational processes that promote and support the manufacturing paradigm in a way that minimizes necessary change, the nearest "as is" state. Such processes should not be expected to be particularly lean until after performance needs drive significant changes to support a leaner approach, the "to be" state. This incremental approach, while fairly smooth and stable can take a decade or more to reach a lean paradigm even if that is the intended end state. If the authors choose to write a second edition it would be useful to discuss how the CMMI model that has come into use since the writing of this book provides potential synergy with the lean approach. To understand what is improved over the software CMM, one should note that the new CMMI model includes systems engineering process areas rather than being focused exclusively on software. Like its predecessor the CMMI is a process framework and is thus process and performance agnostic. The model is not quite paradigm agnostic; it clearly votes against the craft paradigm by labeling such practices "initial" or "capability level 1". One might speculate that a fully integrated lean approach would garner capability level 5 ratings for the relevant process areas. Further, there is no performance aspect to the CMMI SCAMPI appraisal as there would be with a company performance audit model such as the (Malcolm) Baldridge National Quality Award: http://baldrige.nist.gov/. The CMMI SCAMPI asks if there are specific and generic practices (documented processes) in place to address a set of basic business capability questions (goals), but it does not ask how well those processes perform. It is left entirely up to company management to track and manage process performance. In that respect the CMMI model is independent of the lean manufacturing approach. Synergy with lean methods is both possible and desirable. If the authors choose to write a second addition, it would be valuable to devote a chapter or two on how to develop such a synergistic approach in building and maintaining a comprehensive set of organizational business process assets.