Impact of organisational climate and demographics on project specific risks in context to Indian software industry

International Journal of Project Management

Volumn 30, Issue 2, 2012, Pages 176-187

  Sharma, Arpita ^a   Gupta, Aayushi ^a  

^a JAYPEE INSTITUTE OF INFORMATION TECHNOLOGY   (India)

Author keywords

Managing projects; Organisation climate; Perspectives; Project specific software risks; Strategy

Indexed keywords

MANAGING PROJECTS; ORGANISATION CLIMATE; PERSPECTIVES; PROJECT SPECIFIC SOFTWARE RISKS; STRATEGY;

POPULATION STATISTICS; REGRESSION ANALYSIS; SOFTWARE DESIGN;

RISKS;

DEMOGRAPHY; EMPIRICAL ANALYSIS; HIGH TECHNOLOGY INDUSTRY; RISK FACTOR; SOFTWARE;

EID: 84655162108     PISSN: 02637863     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.ijproman.2011.05.003     Document Type: Article

References (90)

1. Abramis D. Work role ambiguity, job satisfaction, and job performance: meta-analyses and review. Psychological Reports 1994, 75:1411-1433.
2. Adams J.R., Adams L.L. The virtual project: managing tomorrow's team today. PM Netw. 1997, 11(1):37-42.
3. Addison T., Vallabh S. Controlling software project risks: an empirical study of methods used by experienced project managers. Proceedings of SAICSIT. Port Elizabeth 2002, 128-140.
4. Aladwani A. An integrated performance model of information systems projects. Journal of Management Information Systems 2002, 19(1):185-210.
5. Anudhe M.D., Mathew S.K. Risks in offshore IT outsourcing: a service provider perspective. European management journal 2009, 27:418-428.
6. Arora A., Athreye S. The Software Industry and India's Economic Development 2001, UN WIDER.
7. Arshad N.R., Mohamed A., Matnor Z. Risk factors in software development projects. Proceedings of the 6th WSEAS international conference on software engineering, parallel and distributed systems Corfu island, Greece, February 16-19 2007.
8. Athreye S. The Indian software industry and its evolving service capability. Industrial and Corporate Change 2005, 14(3):393-418.
9. Avizienis A., Laprie J.C., Randell B., Landwehr C. Basic concepts and taxonomy of dependable and secure computing. IEEE Transactions on Dependable and Secure Computing 2004, 1:11-33.
10. Babar M.A., Verner J.M., Nguyen P.T. Establishing and maintaining trust in software outsourcing relationships: an empirical investigation. Journal of Systems and Software 2007, 80(9):1438-1449.
11. Baccarini D., Salm G., Love P.E.D. Management of risks in information technology projects. Industrial Management & Data Systems 2004, 104(4):286-295.
12. Bannerman P.L. Risk and risk management in software projects: a reassessment. The Journal of Systems and Software 2008, 81:2118-2133.
13. Barki H., Hartwick J. Rethinking the concept of user involvement. MIS Q. 1989, 13(1):53-63.
14. Belbin R.M. Management Teams 1981, John Wiley & Sons, New York.
15. Boban M., Pozgaj Z., Sertic H. Strategies for successful software development risk management. Management 2003, 8(2):77-91.
16. Boehm B.W. Software Engineering Economics 1981, Englewood Cliffs, NJ, Prentice-Hall.
17. Organisational Climate and Culture 1989, 383-412. Jossey-Bass, CA. Boehm (Ed.).
18. Bosco G. Implicit theories of good leadership in the open-source community Accessed: 22.08.2010. http://*http://opensource.mit.edu/papers/bosco.pdf.
19. Braun F., Avital M. Good project management practices drive more than project success: learning, knowledge sharing and job satisfaction in it project teams. Proceedings of the 13th Americas Conference on Information Systems at Colorado, August 9-12 2007, 1-11.
20. Budhwar R. Indian software industry: moving up the value chain Assessed on 13th August 2010. http://www.fms.edu/downloads/conclub_ITinIndia-TheWayForward.pdf.
21. Chan C.L., Jiang J.J., Klein G. Team task skills as a facilitator for application and development skills. IEEE Transaction on Engineering Management 2008, 55(3):434-441.
22. Charette R.N., Adams K.M., White M.B. Managing risk in software maintenance. IEEE Softw. 1997, 14(3):43-50.
23. Chen J.C., Huang S.J. An empirical analysis of the impact of software development problems factors software maintainability. The Journal of Systems and Software 2009, 82(6):981-992.
24. Cornelius E.T. Seven tactics to increase projects success. Collegiate project services assessed 10th march 2010. http://www.collegiateproject.com/articles/SevenTactics.pdf.
25. Costa H.R., Barros M.D.O., Travassos G.H. Evaluating software project portfolio risks. The Journal of Systems and Software 2007, 80:16-31.
26. Crowston K., Kammerer E.E. Coordination and collective mind in software requirements development. IBM Syst. J. 1998, 37(2):227-245.
27. Delmonte A., McCarthy R. Offshore software development: is the benefit worth the risk?. Americas Conference on Information Systems (AMCIS) AMCIS 2003 Proceedings 2003, 1607-1613.
28. Demarco T., Lister T. Waltsing with Bears: Managing Risk on Software Projects 2003, Dorset Publishing Co, New York.
29. Dey P.K., Kinch J., Ogunlana S.O. Managing risk in software development projects: a case study. Industrial management and Data Systems 2007, 107(2):284-303.
30. Doherty N.F., King M. From technical change to socio-technical change: towards a proactive approach to the treatment of organisational issues. Socio-technical and Human Cognition Elements of Information Systems 2003, 22-40. Idea Group Publishing, Hershey, PA.
31. Engel A., Last M. Modeling software testing costs and risks using fuzzy logic paradigm. Journal of Systems and Software 2007, 80(6):817-835.
32. Espinosa J.A., DeLone W., Lee G. Global boundaries, task processes and IS project success: a field study. Information Technology & People 2006, 19(4):345-370.
33. Faraj S., Sambamurthy V. Leadership of information systems development projects. IEEE Trans. Eng. Manag. 2006, 53(2):238-249.
34. Geethalakshmi S.N., Shanmugam A. Success and failure of software development: practitioners' perspective. Proceedings of the International Multi-Conference of Engineers and Computer Scientists, VIMECS 2008, 1:19-21.
35. Gopal A., Mukhopadhyay T., Krishnan M.S., Goldenson D.R. Measurement programs in software development: determinants of success. IEEE Trans. Softw. Eng. 2002, 28(9):863-875.
36. Gorsuch R.L. Factor Analysis 1983, Erlbaum, Hillsdale, NJ. 2nd ed.
37. Hoegl M., Ernst H., Proserpio L. How teamwork matters more as team member dispersion increases. Journal of Product Innovation Management 2007, 24(2):156-165.
38. Hoodat H., Rashidi H. Classification and analysis of risks in software engineering. World Academy of Science, Engineering and Technology 2009, 56:446-452.
39. Iacovou C.L., Nakatsu R. A risk profile of offshore-outsourced development projects. Commun. ACM 2008, 51(6):89-94.
40. Jiang J., Klein G. Software development risks to project effectiveness. Journal of Systems and Software 2000, 52(1):3-10.
41. Jiang J., Klein G. Software project risks and development focus. Project Management Journal 2001, 32(1):20-26.
42. Kahn R.L. Conflict, ambiguity, and overload: three elements in job stress. Occupational Mental Health. 1973, 3:2-9.
43. Kaiser H.F. The application of electronic computers to factor analysis. Educational and Psychological Measurement 1960, 20:41-151.
44. Keil M., Smith H.J., Pawlowski S., Jin L. 'Why didn't somebody tell me?': climate, information asymmetry, and bad news about troubled projects. The DATA BASE for Advances in Information Systems. 2004, 35(2):65-84.
45. Keil M., Paul I.M.G., Mahring M. Reporting bad news on software projects: the effects of culturally constituted views of face-saving. Information of Systems Journal 2007, 17(1):59-87. 2007.
46. Krasner H. Looking over the legal edge of unsuccessful software projects. Cutter IT Journal. 1998, 11(3):11-22.
47. Krishna S., Sahay S., Walsham G. Managing cross-cultural issues in global software outsourcing. Commun. ACM 2004, 47(4):62-66.
48. Kwak Y.H., Stoddard J. Project risk management: lessons learned from software development environment. Technovation 2004, 24:915-920.
49. Litwin G.H., Stringer R.A. Motivation and Organizational Climate 1968, Harvard University Press, Boston, MA.
50. London M., Smither J. Can working with an executive coach improve multisource feedback ratings over time? A quasi-experimental field study. Personnel Psychology 2002, 56:23-46.
51. Luthans F., Norman S.M., Avolio B.J., Avey J.B. The mediating role of psychological capital in the supportive organizational climate-employee performance relationship. Journal of Organizational Behavior 2008, 29:219-238.
52. Lyytinen K., Mathiassen L., Ropponen J. Attention shaping and software risk-a categorical analysis of four classical risk management approaches. Information Systems Research 1998, 9(3):233-255.
53. Masri M.E., Rivadry S. Specifying the software project risk construct. Americas Conference on Information Systems (AMCIS) AMCIS 2010 Proceedings Association for Information Systems 2010, August 12-15.
54. Mathiassen L., Seewaldt T., Stage J. Prototyping and specifying: principles and practices of a mixed approach. Scand. J. Inf. Syst. 1995, 7(1):55-72.
55. McConnell S. Rapid Development 1996, Microsoft Press, Redmond, WA.
56. McLean E.R., Smits S.J., Tanner J.R. The importance of salary on job and career attitudes of information systems professionals. Information and management 1996, 30:291-299.
57. Morrison E. Longitudinal study of the effects of information seeking on newcomer socialization. Journal of Applied Psychology 1993, 78:173-183.
58. Nah F., Lau J., Kuang J. Critical factors for successful implementation of enterprise systems. Business Process Management Journal 2001, 7(3):285-296.
59. Nasscom Strategic Review - A Complete Report 2009 2009.
60. Neumann D.E. An enhanced neural network technique for software risk analysis. IEEE Trans. Softw. Eng. 2002, 28(9):904-912.
61. Nicholson B., Sahay S. Some political and cultural issues in the globalization of software development: case experience from Britain and India. Information and Organization 2001, 11:25-43.
62. Nidomolu S.R., Goodman S.E. Computing in India: an Asian elephant learning to dance. Commun. ACM 1993, 36(4):15-22.
63. Oz E., Sosik J. Why information systems projects are abandoned: a leadership and communication theory and exploratory study. Journal of Computer Information Systems 2000, 66-78. Fall.
64. Oza, N., 2006. An empirical evaluation of client-vendor relationships in Indian software outsourcing companies. PhD. Dissertation.
65. Pan J. "Software Reliability", Carnegie Mellon University assessed on 24th August 2010. http://www.ece.cmu.edu/~koopman/des_s99/sw_reliability.
66. Paul A.K., Anantharaman R.N. Influence of HRM practices on organizational commitment: a study among software professionals in India. Human resources development quarterly 2004, vol. 15(1):77-88. Spring 2004.
67. Procaccino J.D. Quantitative Models for Early Prediction of Software Development Success: A Practitioner's Perspective 2006, Ph.D Dissertation.
68. Procaccino D.J., Verner S.O., Marvin D. Case study: factors for early prediction of software development success. Journal of Information & Software Technology 2002, 44:53-62.
69. Rainer A., Hall T. Identifying the causes of poor progress in software projects metrics. 10th IEEE International Symposium on Software Metrics (METRICS'04) 2004, 184-195.
70. Rasch R.H., Henry L.T. Factors affecting software developers' performance: an integrated approach. MIS Q. 1992, 16(3):395-413.
71. Renn R. Moderation by goal commitment of the feedback-performance relationship: theoretical explanation and preliminary study. Human Resource Management Review 2003, 13:561-580.
72. Ropponen J., Lyytinen K. Components of software development risk: what influences it-a project manager survey. IEEE Trans. Softw. Eng. 2000, 26(2):98-112.
73. Rubin A., Babbie E. Research Methods for Social Work 2002, Brooks/Cole Publishing Company, Pacific Grove, Carlifornia.
74. Sabherwal R., Sein M., Marakas G. Escalating commitment to information systems projects: findings from two simulated experiments. Information & Management 2003, 40(8):781-798.
75. Schmidt R., Lyytinen K., Keil M., Cule P. Identifying software project risks: an international Delphi study. Journal of Management Information Systems 2001, 17(4):5-36.
76. Schneidewind N. Software reliability engineering process. Innov. Syst. Softw. Eng. 2006, 2(3-4):179-190.
77. Shahzad B., Safvi S.A. Risk mitigation and management scheme based on risk priority. Global journal of computer science and technology 2010, 10(4):108-113.
78. Smite D. Requirements management in distributed projects. Journal of Universal Knowledge Management 2006, 1(2):69-76.
79. Smith D., Eastcroft M., Mahmood N., Rode H. Risk factors affecting software projects in South Africa. South African Journal of Business Management 2006, 37(2):55-65.
80. Snow A.P., Keil M., Wallace L. The effects of optimistic and pessimistic biasing on software project status reporting. Information and Management 2007, 44(2):130-141.
81. Tafti M. Risks factors associated with offshore IT outsourcing. Industrial Management and Data Systems 2005, 105(5):549-560.
82. Verner J.M., Evanco W.M., Cerpa N. State of the practice: an exploratory analysis of schedule estimation and software project success prediction. Information and Software Technology 2007, 49(2):181-193.
83. Verner J.M., Beecham S., Cerpa N. Stakeholder Dissonance: disagreements on project outcome and its impact on team motivation across three countries. SIGMIS-CPR'10, May 20-22, 2010, Vancouver, BC, Canada 2010, 25-33.
84. Wallace L., Keil M., Rai A. How software project risk affects project performance: an investigation of the dimensions of risk and an exploratory model. Decis. Sci. 2004, 35(2):289-321.
85. Warkentin M., Moore R.S., Bekkering E., Johnston A.C. Analysis of systems development project risks: an integrative framework. The DATA BASE for advances in Information Systems 2009, 40(2):8-26.
86. Whitmaker B., McKinney J. Role clarity, social skills and the feedback seeking job satisfaction link. International Journal of Organizational Behavior 2009, 14(1):54-68.
87. Woodruff C.K. Managing the results: an examination of professional group perceptions of organizational practice. Information and Management 1990, 19:135-147.
88. Xu X.X., He J. Impact of team attitude and behaviour on is project success. Communications of the IIMA 2008, 8(4):41-52.
89. Yen H.R., Li E.Y., Niehoff B.P. Do organizational citizenship behaviors lead to information system success? Testing the mediation effects of integration climate and project management. Information and Management 2008, 45(6):394-402.
90. Zhou L., Vasconcelos A., Nunes M. Supporting decision making in risk management through an evidence-based information systems project risk checklist. Information Management and Computer Security 2008, 16(2):166-186.