Why SPI Initiative Failed: Contextual Factors and Changing Software Development Environment

For today's software business and its productivity, software process improvement (SPI) plays a significant role. Organizations that produce software face challenges with the productivity and effectiveness of their operation. The literature lists numerous methods to make the operation better. Critical success factors are defined in order to make the successful improvement procedures more certain. However, these methodologies need to be adjusted to match the organizational context. All organizations and their environments are different, and thus the solution that is the most suitable for individual needs must be modified or localized to fit the case-specific contextual demands. This paper studies the importance of these contextual demands in SPI. In the paper, a framework is presented through which the software improvement process can be better under-stood and studied. The framework offers a view to understanding the change process describing eight change paths that may be observed when software process improvement is regarded.

[1]  Judy L. Wynekoop,et al.  Studying system development methodologies: an examination of research methods , 1997, Inf. Syst. J..

[2]  Jyoti Choudrie,et al.  Managing organisational learning through continuous information systems development: tacit knowledge diffusion and meta-abilities perspectives , 2005, Int. J. Knowl. Learn..

[3]  Petra Bosch-Sijtsema,et al.  Knowledge work productivity in distributed teams , 2009, J. Knowl. Manag..

[4]  Didar Zowghi,et al.  Critical success factors for software process improvement implementation: an empirical study , 2006, Softw. Process. Improv. Pract..

[5]  Tracy Hall,et al.  De-motivators for software process improvement: an analysis of practitioners' views , 2003, J. Syst. Softw..

[6]  Daniel T. ones.  Lantech achieved unimaginable results by applying lean thinking to every aspect of its business . Beyond Toyota : How to Root Out Waste and Pursue Perfection , 2006 .

[7]  Tero Päivärinta,et al.  Towards a Framework for Building Theory from ISD Practices , 2010, ISD.

[8]  Lucas D. Introna,et al.  Against method-ism: Exploring the limits of method , 1997, Inf. Technol. People.

[9]  S. Goldfinch,et al.  Pessimism, Computer Failure, and Information Systems Development in the Public Sector , 2007 .

[10]  Austen Rainer,et al.  Implementing software process improvement: an empirical study , 2002, Softw. Process. Improv. Pract..

[11]  Kalle Lyytinen,et al.  Learning failure in information systems development , 1999, Inf. Syst. J..

[12]  R. van Solingen.  A Follow-Up Reflection on Software Process Improvement ROI , 2009, IEEE Software.

[13]  Tero Päivärinta,et al.  A model for analyzing changes in systems development practices , 2012 .

[14]  Michael Eisenbarth,et al.  Implementing Requirements Engineering Processes: Using Cooperative Self-Assessment and Improvement , 2008, IEEE Software.

[15]  Petra M. Bosch-Sijtsema,et al.  Multi-Locational Knowledge Workers in the Office: Navigation, Disturbances and Effectiveness , 2010 .

[16]  Sami Zahran.  Software process improvement - practical guidelines for business success , 1998 .

[17]  Karlheinz Kautz,et al.  Persistent problems and practices in information systems development , 2007, Inf. Syst. J..

[18]  Martha E. Myers.  The I.S. profession and the I.S. professional: fit of mis-fit? , 1992, SIGCPR '92.

[19]  Tero Päivärinta,et al.  From ideals towards practice: paradigmatic mismatches and drifts in method deployment , 2007, Inf. Syst. J..

[20]  Juhani Iivari,et al.  The user – the great unknown of systems development: reasons, forms, challenges, experiences and intellectual contributions of user involvement , 2010, Inf. Syst. J..

[21]  Juhani Iivari,et al.  The Relationship Between Organisational Culture and the Deployment of Systems Development Methodologies , 2001, CAiSE.

[22]  Ivar Jacobson,et al.  Software Reuse: Architecture, Process And Organization For Business Success , 1998, Proceedings. Technology of Object-Oriented Languages. TOOLS 26 (Cat. No.98EX176).

[23]  Karma Sherif,et al.  Resources and incentives for the adoption of systematic software reuse , 2006, Int. J. Inf. Manag..

[24]  Jianwei Yin,et al.  A Component Management System for Mass Customization , 2006, First International Multi-Symposiums on Computer and Computational Sciences (IMSCCS'06).

[25]  Tore Dybå,et al.  An empirical investigation of the key factors for success in software process improvement , 2005, IEEE Transactions on Software Engineering.

[26]  Pekka Abrahamsson,et al.  Commitment Nets in Software Process Improvement , 2002, Ann. Softw. Eng..

[27]  Peter Axel Nielsen,et al.  Success Factors and Motivators in SPI , 2011, Int. J. Hum. Cap. Inf. Technol. Prof..

[28]  Brian Fitzgerald,et al.  An empirically-grounded framework for the information systems development process , 1998, ICIS '98.

[29]  Tracy Hall,et al.  Practitioner roles in software process improvement: an analysis using grid technique , 2002, Softw. Process. Improv. Pract..

[30]  William B. Frakes,et al.  Software reuse research: status and future , 2005, IEEE Transactions on Software Engineering.

[31]  Austen Rainer,et al.  Key success factors for implementing software process improvement: a maturity-based analysis , 2002, J. Syst. Softw..

[32]  Pär J. Ågerfalk,et al.  Flexible and distributed information systems development , 2006 .

[33]  Erik Stolterman,et al.  How System Designers Think about Design and Methods: Some Reflections Based on an Interview Study , 1992, Scand. J. Inf. Syst..

[34]  B. Craig Meyers,et al.  Managing Software Acquisition: Open Systems and COTS Products , 2001 .

[35]  Pär J. Ågerfalk,et al.  Introduction to the Special Issue - Flexible and Distributed Information Systems Development: State of the Art and Research Challenges , 2009, Inf. Syst. Res..

[36]  Peter Schuh.  Integrating Agile Development In The Real World , 2004 .