Abstract
This paper shows how the concepts of lean manufacturing can be successfully transferred from the manufacture of cars and electrical goods to software development. The key lean concept is to minimize work in progress, so quickly forcing any production problems into the open. Production is then halted to allow each problem with the system producing the goods, to be permanently corrected. While frustrating at first, the end result is very high levels of productivity and quality.
Large industrial companies are beginning to transfer their lean production expertise to their in-house software development projects. The two case studies reported here confirm that lean software development can produce rapid quality and productivity gains. A major implementation issue is that lean software development may require deep changes in the way an organization is managed.
Similar content being viewed by others
References
Abegglen, J.C. and Stalk, G. 1985. Kaisha, The Japanese Corporation, New York, Basic Books.
Boehm, B. 1981. Software Engineering Economics, Englewood Cliffs, New York, Prentice-Hall.
Collins, J.C. and Porras, J.I. 1998. Built to Last: Successful Habits of Visionary Companies, London, Century.
Cunningham, J.B. 1993. Action Research and Organizational Development, Westport, CT, Praeger.
Fagan, M.E. 1976. Design and code inspections to reduce errors in program development, IBM Systems J. 15(3): 182-211.
Gilb, T. 1988. Principles of Software Engineering Management, Wokingham, England, Addison-Wesley.
Gilb, T. and Graham, D. 1993. Software Inspection, Wokingham, England, Addison-Wesley.
Hamilton, T. 1999. A Lean Software Engineering System for the Department of Defense, Massachusetts Institute of Technology, MSc Thesis.
Hou, A.C. 1995. Toward Lean Hardware/Software System Development: Evaluation of Selected Complex Electronic System Development Methodologies, Report—Lean 95-01, Lean Aircraft Initiative, Center for Technology, Policy and Industrial Development, Massachusetts Institute of Technology. http://lean.mit.edu/public/index.html.
Humphrey, W.S. 1998. Why don't they practice what we preach? Annals of Software Eng. 6: 201-222.
Lee, A.S. and Baskerville, R.L. 2001. Generalizing Generalizability in Information Systems Research, seminar paper presented at The Queen's University of Belfast, 2 May.
Morgan, T. 1998. Lean Manufacturing Techniques Applied to Software Development, MSc Thesis, Massachusetts Institute of Technology.
Ohno, T. 1988. Toyota Production System: Beyond Large-Scale Production, Cambridge, MA Productivity Press.
Pascale, R.T. 1990. Managing on the Edge, London, Viking.
Paulk, M.C., Curtis, B., Chrissis, M.B., and Weber, C.V. 1993. Capability maturity model, version 1.1, IEEE Software 10(4): 18-27.
Raman, S. 1998. Lean software development: Is it feasible? 17th Digital Avionics Systems Conf., New York, IEEE, pp. 13-18.
Robinson, A.G. and Stern, S. 1998. Corporate Creativity: How Innovation and Improvement Actually Happen, San Francisco, CA, Berrett-Koehler.
Schonberger, R.J. 1986. World Class Manufacturing, New York, The Free Press.
Schulmeyer, G. 1990. Zero Defect Software, New York, McGraw-Hill.
Seddon, J. 1997. In Pursuit of Quality: The Case Against ISO 9000, London, Oaktree Press.
Sutton, J.M. 1996. Lean software for lean aircraft, 15th Digital Avionics Systems Conference, New York, IEEE, pp. 49-54.
Tierney, J. 1993. Eradicating mistakes from your software process through Poka Yoke, Proc. 6th Inte. Software Quality Week, Software Research Institute, San Francisco, CA, May, pp. 300-307.
Whyte, William F. 1991. Participatory Action Research, London, Sage.
Womack, J.P. and Jones, D.T. 1997. Lean Thinking, London, Touchstone Books.
Womack, J.P. and Jones, D.T. 1994. From lean production to the lean enterprise, Harvard Business Rev. 72(2): 93-103.
Womack, J.P., Jones D.T., and Ross, D. 1990. The Machine that Changed the World, New York, Rawson Associates.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Middleton, P. Lean Software Development: Two Case Studies. Software Quality Journal 9, 241–252 (2001). https://doi.org/10.1023/A:1013754402981
Issue Date:
DOI: https://doi.org/10.1023/A:1013754402981