Software process improvement through the Lean Measurement (SPI-LEAM) method

Software process improvement methods help to continuously refine and adjust the software process to improve its performance (e.g., in terms of lead-time, quality of the software product, reduction of change requests, and so forth). Lean software development propagates two important principles that help process improvement, namely identification of waste in the process and considering interactions between the individual parts of the software process from an end-to-end perspective. A large shift of thinking about the own way of working is often required to adopt lean. One of the potential main sources of failure is to try to make a too large shift about the ways of working at once. Therefore, the change to lean has to be done in a continuous and incremental way. In response to this we propose a novel approach to bring together the quality improvement paradigm and lean software development practices, the approach being called Software Process Improvement through the Lean Measurement (SPI-LEAM) Method. The method allows to assess the performance of the development process and take continuous actions to arrive at a more lean software process over time. The method is under implementation in industry and an initial evaluation of the method has been performed.

[1]  Pär Åhlström,et al.  The difficult path to lean product development , 1996 .

[2]  Onur Demirörs,et al.  Functional size measurement revisited , 2008, TSEM.

[3]  Claes Wohlin,et al.  Faults-slip-through - a concept for measuring the efficiency of the test process , 2006, Softw. Process. Improv. Pract..

[4]  Victor R. Basili,et al.  The Experience Factory and Its Relationship to Other Quality Approaches , 1995, Adv. Comput..

[5]  Gregor Scheithauer,et al.  Modern Software Engineering Concepts and Practices: Advanced Approaches , 2010 .

[6]  Paolo Donzelli,et al.  Hybrid simulation modelling of the software process , 2001, J. Syst. Softw..

[7]  Peter Middleton,et al.  Lean Software Development: Two Case Studies , 2001, Software Quality Journal.

[8]  Gunter Bolch,et al.  Queueing Networks and Markov Chains , 2005 .

[9]  Brian H. Maskell,et al.  Practical Lean Accounting: A Proven System for Measuring and Managing the Lean Enterprise , 2003 .

[10]  Jeffrey K. Liker,et al.  The Toyota Product Development System: Integrating People, Process And Technology , 2006 .

[11]  Myron Hlynka,et al.  Queueing Networks and Markov Chains (Modeling and Performance Evaluation With Computer Science Applications) , 2007, Technometrics.

[12]  Claes Wohlin,et al.  The Waterfall Model in Large-Scale Development , 2009, PROFES.

[13]  Claes Wohlin,et al.  A model for software rework reduction through a combination of anomaly metrics , 2008, J. Syst. Softw..

[14]  Victor R. Basili,et al.  Software process evolution at the SEL , 1994, IEEE Software.

[15]  Claes Wohlin,et al.  Measuring the flow in lean software development , 2011, Softw. Pract. Exp..

[16]  新郷 重夫,et al.  A study of the Toyota production system from an industrial engineering viewpoint , 1989 .

[17]  Peter Middleton,et al.  Lean Software Management Case Study: Timberline Inc , 2005, XP.

[18]  Christos G. Cassandras,et al.  Introduction to Discrete Event Systems , 1999, The Kluwer International Series on Discrete Event Dynamic Systems.

[19]  Thane Morgan Lean manufacturing techniques applied to software development , 1998 .

[20]  Mary Poppendieck,et al.  Lean Software Development: An Agile Toolkit , 2003 .

[21]  PetersenKai,et al.  Software process improvement through the Lean Measurement (SPI-LEAM) method , 2010 .

[22]  D. Earl Kline,et al.  Benchmarking performance measurement and lean manufacturing in the rough mill , 2006 .

[23]  Mike Sullivan,et al.  The Art of Lean Software Development: A Practical and Incremental Approach , 2009 .

[24]  Mary Poppendieck,et al.  Lean Software Development , 2007, 29th International Conference on Software Engineering (ICSE'07 Companion).

[25]  Isaac Pentinmaki,et al.  Review of "Lean software development: an agile tookit" by Mary and Tom Poppendieck. Addison Wesley 2003. , 2004, SOEN.

[26]  Martin Höst,et al.  Exploring bottlenecks in market-driven requirements management processes with discrete event simulation , 2001, J. Syst. Softw..

[27]  Richard Tanner Pascale,et al.  Managing on the edge : how the smartest companies use conflict to stay ahead , 1990 .

[28]  Capers Jones,et al.  Applied software measurement: assuring productivity and quality , 1991 .

[29]  James P. Womack,et al.  Lean Thinking: Banish Waste and Create Wealth in Your Corporation , 1996 .

[30]  Tony Gorschek,et al.  Requirements Abstraction Model , 2005, Requirements Engineering.

[31]  Capers Jones,et al.  Applied software measurement (2nd ed.): assuring productivity and quality , 1996 .

[32]  Donald G. Reinertsen Managing The Design Factory: A Product Developer's Toolkit , 1997 .

[33]  Bohdan W. Oppenheim,et al.  Lean product development flow , 2004, Syst. Eng..

[34]  David J. Anderson Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results , 2003 .

[35]  Li Hou,et al.  An Experience-Based Approach for Test Execution Effort Estimation , 2008, 2008 The 9th International Conference for Young Computer Scientists.

[36]  G.I.U.S. Perera,et al.  Enhanced agile software development — hybrid paradigm with LEAN practice , 2007, 2007 International Conference on Industrial and Information Systems.

[37]  Andrea De Lucia,et al.  Assessing effort estimation models for corrective maintenance through empirical studies , 2005, Inf. Softw. Technol..

[38]  G. G. Stokes "J." , 1890, The New Yale Book of Quotations.

[39]  Bohdan W. Oppenheim Lean in Product Development , 2004 .

[40]  Mikael Lindvall,et al.  Traceability aspects of impact analysis in object-oriented systems , 1998, J. Softw. Maintenance Res. Pract..

[41]  Tony Gorschek,et al.  A Model for Technology Transfer in Practice , 2006, IEEE Software.

[42]  Victor R. Basili,et al.  Quantitative Evaluation of Software Methodology , 1985 .

[43]  Inge van de Weerd,et al.  Meta-Modeling for Situational Analysis and Design Methods , 2009 .

[44]  Emma Parnell-Klabo Introducing lean principles with agile practices at a Fortune 500 company , 2006, AGILE 2006 (AGILE'06).