Exploring Risk Dimensions in the Indian Software Industry

The success of software projects is quite subjective in nature and is fettered by many risks, the perception of which varies from individual to individual and largely depends on the demographic characteristics of the executives and even the characteristics of the project. This study aims to identify and gauge the software risk dimensions and analyze the differences of perception among executives toward software risks. The contributions of this study untangle the issues underlying risks in the software industry and associates these issues with the perception of the “human” factor present in the industry.

[1]  Eileen M. Trauth,et al.  Cultural influences and globally distributed information systems development: experiences from Chinese IT professionals , 2007, SIGMIS CPR '07.

[2]  Lihong Zhou,et al.  Supporting decision making in risk management through an evidence-based information systems project risk checklist , 2008, Inf. Manag. Comput. Secur..

[3]  Márcio de Oliveira Barros,et al.  Evaluating software project portfolio risks , 2007, J. Syst. Softw..

[4]  Michael Evans,et al.  Software sizing, estimation, and risk management , 2006 .

[5]  Katja Hölttä-Otto,et al.  Estimating factors affecting project task size in product development-an empirical study , 2006, IEEE Transactions on Engineering Management.

[6]  Ashley A. Bush,et al.  Reconciling user and project manager perceptions of IT project risk: a Delphi study 1 , 2002, Inf. Syst. J..

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

[8]  Hassan Rashidi,et al.  Classification and Analysis of Risks in Software Engineering , 2009 .

[9]  A. Jansson.  Software Maintenance and Process Improvement by CMMI , 2008 .

[10]  E. Bersoff,et al.  Software Configuration Management , 1978, SIGMETRICS Perform. Evaluation Rev..

[11]  Edward H. Bersoff,et al.  Elements of Software Configuration Management , 1984, IEEE Transactions on Software Engineering.

[12]  Nicolas Anquetil,et al.  Which documentation for software maintenance? , 2010, Journal of the Brazilian Computer Society.

[13]  Susan A. Sherer,et al.  The three dimensions of software risk: technical, organizational, and environmental , 1995, Proceedings of the Twenty-Eighth Annual Hawaii International Conference on System Sciences.

[14]  Mark Keil,et al.  Reporting bad news on software projects: the effects of culturally constituted views of face‐saving , 2007, Inf. Syst. J..

[15]  Kalle Lyytinen,et al.  A framework for identifying software project risks , 1998, CACM.

[16]  June M. Verner,et al.  State of the practice: An exploratory analysis of schedule estimation and software project success prediction , 2007, Inf. Softw. Technol..

[17]  Madhuchhanda Das Aundhe,et al.  Risks in offshore IT outsourcing: A service provider perspective , 2009 .

[18]  Derek H.T. Walker,et al.  Advancing project management in learning organizations , 2004 .

[19]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

[20]  John J. Sosik,et al.  Why Information Systems Projects are Abandoned: A Leadership and Communication Theory and Exploratory Study , 2000, J. Comput. Inf. Syst..

[21]  Samer Faraj,et al.  Leadership of information systems development projects , 2006, IEEE Transactions on Engineering Management.

[22]  Uday R. Kulkarni,et al.  Critical success factors for software projects , 1998, ICIS '98.

[23]  Fiona Fui-Hoon Nah,et al.  Critical factors for successful implementation of enterprise systems , 2001, Bus. Process. Manag. J..

[24]  Mark Keil,et al.  'Why didn't somebody tell me?': climate, information asymmetry, and bad news about troubled projects , 2004, DATB.

[25]  Forrest Shull,et al.  How perspective-based reading can improve requirements inspections , 2000, Computer.

[26]  B. Schneider,et al.  Organizational climate and culture. , 2009, Annual review of psychology.

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

[28]  Craig R. Selinger,et al.  Comparison between Hardware System Timing and Project Management Critical Path Analysis Methodologies , 2001 .

[29]  Grady Booch,et al.  When bad things happen to good projects , 1994 .

[30]  June M. Verner,et al.  Stakeholder dissonance: disagreements on project outcome and its impact on team motivation across three countries , 2010, SIGMIS-CPR '10.

[31]  David Baccarini,et al.  The concept of project complexity—a review , 1996 .

[32]  Merrill Warkentin,et al.  Analysis of systems development project risks: an integrative framework , 2009, DATB.

[33]  Paul L. Bannerman,et al.  Risk and risk management in software projects: A reassessment , 2008, J. Syst. Softw..

[34]  Charalambos L. Iacovou,et al.  Biased project status reports: A survey of IS professionals , 2009, ECIS.

[35]  Chiara Francalanci,et al.  Predicting the implementation effort of ERP projects: empirical evidence on SAP/R3 , 2001, J. Inf. Technol..

[36]  Henri Barki,et al.  Rethinking the Concept of User Involvement , 1989, MIS Q..

[37]  Lars Mathiassen,et al.  Attention-shaping tools, expertise, and perceived control in IT project risk assessment , 2007, Decis. Support Syst..

[38]  Urvashi Rathod,et al.  Defining ‘success’ for software projects: An exploratory revelation , 2006 .

[39]  Derek C. Smith,et al.  Risk factors affecting software projects in South Africa , 2006 .

[40]  Gianluca Bosco,et al.  Implicit theories of "good leadership" in the open-source community , 2004 .

[41]  Kalle Lyytinen,et al.  Identifying Software Project Risks: An International Delphi Study , 2001, J. Manag. Inf. Syst..

[42]  Forrest Shull,et al.  How Perspective-Based Reading Can Improve Requirements , 2000 .

[43]  Stephen O. Ogunlana,et al.  Managing risk in software development projects: a case study , 2007, Ind. Manag. Data Syst..

[44]  A. Mursu,et al.  Toward Successful ISD in Developing Countries : First Results from a Nigerian Risk Study Using the Delphi Method , 1999 .

[45]  Carl E. Landwehr,et al.  Basic concepts and taxonomy of dependable and secure computing , 2004, IEEE Transactions on Dependable and Secure Computing.

[46]  Kalle Lyytinen,et al.  Components of Software Development Risk: How to Address Them? A Project Manager Survey , 2000, IEEE Trans. Software Eng..

[47]  Austen Rainer,et al.  Critical factors in software outsourcing: a pilot study , 2004, WISER '04.

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

[49]  Ilana Lavy,et al.  Changing Students Perception Regarding Software Documentation , 2010, MCIS.

[50]  Capers Jones,et al.  Assessment and control of software risks , 1994, Yourdon Press Computing Series.

[51]  A. Arora,et al.  The Indian Software Services Industry , 1999 .

[52]  James J. Jiang,et al.  Software Project Risks and Development Focus , 2001 .

[53]  T. Addison,et al.  Controlling software project risks: an empirical study of methods used by experienced project managers , 2002 .

[54]  Mark Keil,et al.  The effects of optimistic and pessimistic biasing on software project status reporting , 2007, Inf. Manag..

[55]  Michael R. Lyu,et al.  What is software reliability? , 1994, Proceedings of COMPASS'94 - 1994 IEEE 9th Annual Conference on Computer Assurance.

[56]  Robbie T. Nakatsu,et al.  A risk profile of offshore-outsourced development projects , 2008, CACM.

[57]  Darja Šmite,et al.  Requirements Management in Distributed Projects , .

[58]  Rajiv Sabherwal,et al.  Escalating commitment to information system projects: findings from two simulated experiments , 2003, Inf. Manag..

[59]  Merrill Warkentin,et al.  Risk Perspectives in Systems Development , 2007, AMCIS.

[60]  J.S. Reel,et al.  Critical Success Factors in Software Projects , 1999, IEEE Softw..

[61]  Kalle Lyytinen,et al.  Attention Shaping and Software Risk - A Categorical Analysis of Four Classical Risk Management Approaches , 1998, Inf. Syst. Res..