The impact of software process standardization on software flexibility and project management performance: Control theory perspective

It has been assumed for years that process standardization in the development of software will improve the efficiency of the development project by the virtues of applying a learned procedure and tight controls. Past research, however, is inconclusive in the elements that must be in place to achieve the benefits. In this study, we employ the software quality principle of flexibility as a mediator variable to determine if certain design aspects play a key role in achieving the benefits to the project of process standardization. A survey of computer professionals indicates that software flexibility is a positive influence. System designers should apply standard processes but with an eye toward quality design principles.

[1]  Gary Klein,et al.  An exploration of the relationship between software development process maturity and project performance , 2004, Inf. Manag..

[2]  Mauri Laitinen,et al.  Thinking objectively: software process improvement in the small , 2001, CACM.

[3]  K. Peterson,et al.  Mechanisms of Administrative Control Over Managers in Educational Organizations , 1984 .

[4]  C. Fornell,et al.  Evaluating structural equation models with unobservable variables and measurement error. , 1981 .

[5]  Sasa M. Dekleva,et al.  The Influence of the Information Systems Development Approach on Maintenance , 1992, MIS Q..

[6]  Jan-Bernd Lohmöller,et al.  Latent Variable Path Modeling with Partial Least Squares , 1989 .

[7]  John P. Campbell,et al.  Measurement Theory for the Behavioral Sciences. , 1983 .

[8]  Hareton K. N. Leung.  Organizational Factors for Successful Management of Software Development , 2002, J. Comput. Inf. Syst..

[9]  Wanda J. Orlikowski,et al.  CASE Tools as Organizational Change: Investigating Incremental and Radical Changes in Systems Development , 1993, MIS Q..

[10]  Lars Mathiassen,et al.  Agility : How to Navigate Improvement Projects Research Section , 2007 .

[11]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[12]  Watts S. Humphrey,et al.  Results of Applying the Personal Software Process , 1997, Computer.

[13]  Mohamed E. Fayad,et al.  Software process improvement in the small. , 2001 .

[14]  Jeremy Rose,et al.  Prescription, description, reflection: the shape of the software process improvement field , 2004, Int. J. Inf. Manag..

[15]  Bill Curtis,et al.  Process modeling , 1992, CACM.

[16]  Ian Sommerville,et al.  Managing Process Inconsistency Using Viewpoints , 1999, IEEE Trans. Software Eng..

[17]  Mary C. Jones,et al.  IS project team performance: An empirical assessment , 1996, Inf. Manag..

[18]  Derek L. Nazareth,et al.  Assessing the cost-effectiveness of software reuse: A model for planned reuse , 2004, J. Syst. Softw..

[19]  Ioannis Stamelos,et al.  An empirical investigation of an object-oriented design heuristic for maintainability , 2003, J. Syst. Softw..

[20]  Ioannis Stamelos,et al.  Open source software development should strive for even greater code maintainability , 2004, CACM.

[21]  George M. Wyner,et al.  Process Coordination Requirements: Implications for the Design of Knowledge Management Systems , 2006, J. Comput. Inf. Syst..

[22]  Howard B. Lee,et al.  Foundations of Behavioral Research , 1973 .

[23]  Fatemeh Zahedi,et al.  Quality Information Systems , 1994, Encyclopedia of Information Systems.

[24]  Uday Kumar,et al.  Design and development of product support and maintenance concepts for industrial systems , 2003 .

[25]  W. Ouchi.  The Relationship Between Organizational Structure and Organizational Control. , 1977 .

[26]  Christof Ebert.  Technical controlling and software process improvement , 1999, J. Syst. Softw..

[27]  Sarma R. Nidumolu.  Standardization, requirements uncertainty and software project performance , 1996, Inf. Manag..

[28]  John M. Jermier,et al.  Substitutes for leadership: Their meaning and measurement , 1978 .

[29]  Kathleen M. Eisenhardt,et al.  Control: Organizational and Economic Approaches , 1985 .

[30]  Reidar Conradi,et al.  Improving Software Process Improvement , 2002, IEEE Softw..

[31]  Daniel Robey,et al.  Perceptions of Conflict and Success in Information Systems Development Projects , 1993, J. Manag. Inf. Syst..

[32]  J. C. Henderson,et al.  Managing I/S Design Teams: A Control Theories Perspective , 1992 .

[33]  Keith Goffin,et al.  Design for Supportability: Essential Component of New Product Development , 2000 .

[34]  Mark C. Paulk,et al.  How ISO 9001 Compares With The CMM , 1995, IEEE Softw..

[35]  Harlan D. Mills,et al.  Engineering software under statistical quality control , 1990, IEEE Software.

[36]  J. Scott Armstrong,et al.  Estimating nonresponse bias in mail surveys. , 1977 .

[37]  Gordon B. Davis,et al.  Reengineering the Systems Development Process: The Link Between Autonomous Teams and Business Process Outcomes , 1997, J. Manag. Inf. Syst..

[38]  Stephanie Watts,et al.  Antidotes for high complexity and ambiguity in software development , 1999, Inf. Manag..

[39]  Chris F. Kemerer,et al.  The assimilation of software process innovations: an organizational learning perspective , 1997 .

[40]  Judith G. Brodman,et al.  Applying CMM Project Planning Practices to Diverse Environments , 2000, IEEE Softw..

[41]  Edward Yourdon,et al.  Modern structured analysis , 1989 .

[42]  Kay M. Nelson,et al.  International Conference on Information Systems ( ICIS ) 1993 THE CONTRIBUTION OF SHARED KNOWLEDGE TO IS GROUP PERFORMANCE , 2017 .

[43]  Jean-Pierre Kuilboer,et al.  Software process and product improvement: an empirical assessment , 2000, Inf. Softw. Technol..

[44]  Richard E. Zultner,et al.  TQM for technical teams , 1993, CACM.

[45]  M. Sobol,et al.  Barriers to and Measurements of the Diffusion of Technology from the University to Industry , 2003 .

[46]  Warren Harrison.  High-Tech Disasters , 2005, IEEE Softw..

[47]  Mark C. Paulk,et al.  Capability Maturity Model , 1991 .

[48]  Patricia J. Guinan,et al.  Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach , 1998, Inf. Syst. Res..

[49]  James J. Jiang,et al.  The impacts of charismatic leadership style on team cohesiveness and overall performance during ERP implementation , 2005 .

[50]  Kurt R. Linberg.  Software developer perceptions about software project failure: a case study , 1999, J. Syst. Softw..

[51]  Victor Kuperman.  Productivity in the Internet mailing lists: A bibliometric analysis , 2006 .

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

[53]  Cynthia Mathis Beath,et al.  Strategies for Managing MIS Projects: A Transaction Cost Approach , 1983, ICIS.

[54]  Reza Khorramshahgol,et al.  The Open Software Intensive System Strategy: An Integrative Approach for Building Software Intensive Systems , 2006, J. Comput. Inf. Syst..

[55]  Christopher P. Holland,et al.  On the architecture and form of flexible process support , 2007, Softw. Process. Improv. Pract..

[56]  Les Hatton,et al.  Does OO Sync with How We Think? , 1998, IEEE Softw..

[57]  Victor R. Basili,et al.  Improve Software Quality by Reusing Knowledge and Experience , 1995 .

[58]  D. A. Kenny,et al.  The moderator-mediator variable distinction in social psychological research: conceptual, strategic, and statistical considerations. , 1986, Journal of personality and social psychology.

[59]  W. Ouchi.  A Conceptual Framework for the Design of Organizational Control Mechanisms , 1979 .

[60]  Rudy Hirschheim,et al.  User Experience with and Assessment of Participative Systems Design , 1985, MIS Q..

[61]  Sarma R. Nidumolu.  The Effect of Coordination and Uncertainty on Software Project Performance: Residual Performance Risk as an Intervening Variable , 1995, Inf. Syst. Res..

[62]  Akhilesh Bajaj,et al.  An estimation of the decision models of senior IS managers when evaluating the external quality of organizational software , 2002, J. Syst. Softw..

[63]  Lars Mathiassen,et al.  A Conceptual MAP of Software Process Improvement , 2001, Scand. J. Inf. Syst..

[64]  Robert L. Glass.  IT Failure Rates--70% or 10-15%? , 2005, IEEE Softw..

[65]  M. Hammer,et al.  REENGINEERING THE CORPORATION: A MANIFESTO FOR BUSINESS REVOLUTION , 1995 .

[66]  Jill Smith Slater,et al.  SIM Paper Competition: The Application Software Factory: Applying Total Quality Techniques to Systems Development , 1991, MIS Q..

[67]  K. Jöreskog,et al.  Intraclass Reliability Estimates: Testing Structural Assumptions , 1974 .

[68]  Watts S. Humphrey,et al.  Software process improvement at Hughes Aircraft , 1991, IEEE Software.

[69]  J. S. Long,et al.  Testing Structural Equation Models , 1993 .

[70]  Sasa M. Dekleva,et al.  Measuring Software Engineering Evolution: A Rasch Calibration , 1997, Inf. Syst. Res..

[71]  John Wateridge,et al.  IT projects: a basis for success , 1995 .

[72]  Noushin Ashrafi,et al.  The impact of software process improvement on quality: in theory and practice , 2003, Inf. Manag..

[73]  John Hulland,et al.  Use of partial least squares (PLS) in strategic management research: a review of four recent studies , 1999 .

[74]  Stan Rifkin.  Is Process Improvement Irrelevant to Produce New Era Software? , 2002, ECSQ.

[75]  Magne Jørgensen,et al.  How large are software cost overruns? A review of the 1994 CHAOS report , 2006, Inf. Softw. Technol..

[76]  Hesham El-Rewini,et al.  Keeping Pace with an Information Society , 1997, Computer.

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

[78]  Michael A. Cusumano,et al.  Shifting economies: From craft production to flexible systems and software factories , 1992 .

[79]  Stephen R. Schach,et al.  Categorization of common coupling and its application to the maintainability of the Linux kernel , 2004, IEEE Transactions on Software Engineering.

[80]  Timo Varkoi,et al.  Standard based software process assessments in small companies , 2006, Softw. Process. Improv. Pract..

[81]  Barry Katz,et al.  Building a three dimensional work breakdown structure , 1985, DATB.

[82]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[83]  E. A. Locke,et al.  Goal setting and task performance: 1969–1980. , 1981 .

[84]  F. W. McFarlan,et al.  Portfolio approach to information systems , 1989 .

[85]  Susan Rosenbaum,et al.  Software improvements in an international company , 1993, Proceedings of 1993 15th International Conference on Software Engineering.

[86]  Tridas Mukhopadhyay,et al.  Software Processes and Project Performance , 1995, J. Manag. Inf. Syst..