Lean Software Development: Two Case Studies

Software Quality Journal

Volumn 9, Issue 4, 2001, Pages 241-252

  Middleton, Peter ^a,b,c,d  

^a QUEEN'S UNIVERSITY BELFAST   (United Kingdom)

^b UNIVERSITY OF MANCHESTER   (United Kingdom)

^c UNIVERSITY OF ULSTER   (United Kingdom)

^d IMPERIAL COLLEGE LONDON   (United Kingdom)

Author keywords

Just in time; Lean software development; Management; Mistake proofing; Organizational change; Productivity; Quality; Zero defects

Indexed keywords

AUTOMOBILE MANUFACTURE; IMAGE QUALITY; MANAGEMENT; PRODUCTIVITY;

JUST IN TIME; LEAN SOFTWARE DEVELOPMENT; MISTAKE-PROOFING; ORGANIZATIONAL CHANGE; ZERO-DEFECTS;

SOFTWARE DESIGN;

EID: 1542780736     PISSN: 09639314     EISSN: 15731367     Source Type: Journal    
DOI: 10.1023/A:1013754402981     Document Type: Article

References (26)

1. Abegglen, J.C. and Stalk, G. 1985. Kaisha, The Japanese Corporation, New York, Basic Books.
2. Boehm, B. 1981. Software Engineering Economics, Englewood Cliffs, New York, Prentice-Hall.
3. Collins, J.C. and Porras, J.I. 1998. Built to Last: Successful Habits of Visionary Companies, London, Century.
4. Cunningham, J.B. 1993. Action Research and Organizational Development, Westport, CT, Praeger.
5. Fagan, M.E. 1976. Design and code inspections to reduce errors in program development, IBM Systems J. 15(3): 182-211.
6. Gilb, T. 1988. Principles of Software Engineering Management, Wokingham, England, Addison-Wesley.
7. Gilb, T. and Graham, D. 1993. Software Inspection, Wokingham, England, Addison-Wesley.
8. Hamilton, T. 1999. A Lean Software Engineering System for the Department of Defense, Massachusetts Institute of Technology, MSc Thesis.
9. 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.
10. Humphrey, W.S. 1998. Why don't they practice what we preach? Annals of Software Eng. 6: 201-222.
11. 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.
12. Morgan, T 1998. Lean Manufacturing Techniques Applied to Software Development, MSc Thesis, Massachusetts Institute of Technology.
13. Ohno, T 1988. Toyota Production System: Beyond Large-Scale Production, Cambridge, MA Productivity Press.
14. Pascale, R.T. 1990. Managing on the Edge, London, Viking.
15. 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.
16. Raman, S. 1998. Lean software development: Is it feasible? 17th Digital Avionics Systems Conf., New York, IEEE, pp. 13-18.
17. Robinson, A.G. and Stern, S. 1998. Corporate Creativity: How Innovation and Improvement Actually Happen, San Francisco, CA, Berrett-Koehler.
18. Schonberger, R.J. 1986. World Class Manufacturing, New York, The Free Press.
19. Schulmeyer, G. 1990. Zero Defect Software, New York, McGraw-Hill.
20. Seddon, J. 1997. In Pursuit of Quality: The Case Against ISO 9000, London, Oaktree Press.
21. Sutton, J.M. 1996. Lean software for lean aircraft, 15th Digital Avionics Systems Conference, New York, IEEE, pp. 49-54.
22. 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.
23. Whyte, William F. 1991. Participatory Action Research, London, Sage.
24. Womack, J.P. and Jones, D.T. 1997. Lean Thinking, London, Touchstone Books.
25. Womack, J.P. and Jones, D.T. 1994. From lean production to the lean enterprise, Harvard Business Rev. 72(2): 93-103.
26. Womack, J.P., Jones D.T., and Ross, D. 1990. The Machine that Changed the World, New York, Rawson Associates.