Page 1
169
LIST OF REFERENCES
[1] Powell et al. u 1997, Powell, T. and Micallef, A. “Information Technology as Competitive
Advantage: The Role of Human, Business, and Technology Resources‖, Strategic Management
Journal, vol. 18 no. 5, pp 375-405, 1997.
[2] Igbaria, M., Zinatelli, N., and Cavaye, A. “Analysis of Information Technology Success in
Small Firms in New Zealand”, International Journal of Information Management, vol. 18, no.2,
pp. 103-119, 1998.
[3] Shuit, D. “Companies See Gains in successful Software System Implementations‖, Workforce
Management, vol. 83, no. 1, pp.55-56, 2004.
[4] Deloitte report 2009–“Global economic slowdown and its impact on the Indian IT industry‖.
www.deloittemeet.com/files/IT%20Recession.pdf, assessed on 17th July, 2010.
[5] Li, M., and Gao, M., “Strategies for developing China’s Software Industry”, Information
Technologies and International Development, vol. 1, no. 1, pp. 61-73, Fall 2003.
[6] Nasscom – “Strategic review‖- A complete report 2009.
[7] Budhwar, R., ―Indian software industry: moving up the value chain‖,
www.fms.edu/downloads/conclub_ITinIndia-TheWayForward.pdf, assessed on 13th August 2010.
[8] Nasscom report: Nasscom: Perspective 2020,
www.nasscom.in/nasscom/templates/flagshipEvents.aspx?id=56126, assessed on 29th June 2010.
[9] Standish report - CHAOS Summary 2009,
http://www1.standishgroup.com/newsroom/chaos_2009.php, assessed on 13th July 2010.
[10] Boehm, B.W., “Software risk management principles and practices”, IEEE Software, Vol. 8,
no. 1, pp.32–41, 1991.
[11] Hamid, A.T., and Madnick, S.E.,―Software project dynamics an integrated approach”, New
Jersey, Prentice Hall, 1991.
[12] Kwak, Y.H., and Stoddard, J., “Project risk management: lessons learned from software
development environment”, Technovation, Vol. 24, pp. 915-920, 2004.
Page 2
170
[13] Mensah, E.M., and Przasnyski, Z.H., “On information systems project abandonment: an
exploratory study of organizational practices”, MIS Quarterly, vol. 15, no.1, pp. 67-85, 1991.
[14] Keil, M. “Pulling the Plug: Software Project Management and the Problem of Project
Escalation‖, MIS Quarterly, vol. 19, no. 4, pp. 421–447, 1995.
[15] Keil, M., Cule, P., Lyytinen, K., and Schmidt, R.,―A framework for identifying software
project risks‖, Communications of the ACM, vol. 41, no.11, pp. 76-83, 1998.
[16] Phan, D., Vogel, D. and Nunamaker, J., ―The Search for Perfect Project Management‖,
Computerworld, vol. 22, pp. 95-100, 1998.
[17] McFarlan, W., ―Portfolio Approach to Information Systems‖, Journal of Systems
Management, vol. 33, no. 1, pp.12–19, 1982.
[18] Brooks, Jr., F.P., ―No Silver Bullet—Essence and Accidents of Software Engineering‖,
Information Processing, vol. 86. H.J. Kugler, ed. Amsterdam: Elsevier Science Publishers B.V.
(North Holland), pp. 1069-1076, 1986.
[19] Boehm, B.W., ―Organizational Climate and Culture (ed.)‖, Jossey-Bass, CA, 1989.
[20] Nidomolu, S.R., and Goodman, S.E., ―Computing in India: an Asian elephant learning to
dance‖, Communications ACM, vol. 36, no. 4, pp. 15-22, 1993.
[21] Gopal, A., Mukhopadhyay, T., Krishnan, and M.S., Goldenson, D.R., ―Measurement
programs in software development: Determinants of success‖, IEEE Transactions of Software
Engineering, vol. 28, no. 9, pp. 863–875, 2002.
[22] Anudhe, M.D., and Mathew, S.K., “Risks in offshore IT outsourcing: A service provider
perspective‖, European management journal, vol. 27, pp. 418-428, 2009.
[23] Boehm, B.W., and DeMarco T., “Software Risk management‖, IEEE Software, vol. 14, no.
3, pp. 17-19, 1997.
[24] Costa, H.R., Barros, M.D.O., and Travassos, G.H., ―Evaluating software project portfolio
risks‖, The Journal of Systems and Software, vol.80, pp. 16-31, 2007.
[25] Hoodat, H., and Rashidi, H., “Classification and analysis of risks in software engineering‖,
World Academy of Science, Engineering and Technology. Vol. 56, pp. 446-452, 2009.
Page 3
171
[26] Ropponen J., and Lyytinen K., “Components of Software Development Risk: what influences
it- a project manager survey‖, IEEE Transactions on Software Engineering, vol. 26, no. 2, pp.
98-112, 2000.
[27] Doherty, N.F., and King, M., “From technical change to socio-technical change: towards a
proactive approach to the treatment of organizational issues”, Socio-technical and human
cognition elements of information systems, Idea Group Publishing, Hershey, PA, pp. 22-40,
2003.
[28] Faraj, S., and Sambamurthy, V., “Leadership of information systems development projects‖,
IEEE transactions of engineering management, vol.53, no.2, pp. 238-249, 2006.
[29] Mensah, E.K., and Przasnyski, Z.H., ―Factors contributing to the abandonment of
information systems development projects”, Journal of Information Technology, vol.9, pp.185-
201, 1994.
[30] Warkentin, M., Moore, R.S., Bekkering, E., and Johnston, A.C., “Analysis of systems
development project risks: an integrative framework‖, The DATA BASE for advances in
Information Systems, vol. 40, no. 2, pp. 8-26, 2009.
[31] Xu, X.X., and He, J., ―Impact of Team Attitude and Behaviour on IS Project Success‖.
Communications of the IIMA, vol.8, no.4, 41-52, 2008.
[32] Geethalakshmi, S.N., and Shanmugam, A., ―Success and Failure of Software Development:
Practitioners’ Perspective‖, Proceedings of the International Multi-Conference of Engineers and
Computer Scientists, VIMECS. No. 1, pp. 19-21, 2008.
[33] Wallace, L., Keil, M., and Rai, A., “How software project risk affects project performance:
an investigation of the dimensions of risk and an exploratory model‖, Decision Sciences, vol. 35,
no. 2, pp. 289-321, spring 2004.
[34] Masri, M.E., and Rivadry, S., “Specifying the Software Project Risk Construct‖, Americas
Conference on Information Systems (AMCIS) AMCIS 2010 Proceedings Association for
Information Systems. August 12-15, 2010.
Page 4
172
[35] Keil, M., Smith, H.J., Pawlowski, S., and Jin, L., ―Why Didn't Somebody Tell Me?': Climate,
Information Asymmetry, and Bad News About Troubled Projects‖, The DATABASE for
Advances in Information Systems, vol. 35, no. 2, pp. 65-84, 2004.
[36] Bannerman, P.L., “Risk and risk management in software projects: A reassessment”, The
Journal of Systems and Software, vol. 81, pp. 2118-2133, 2008.
[37] Baccarini, D., Salm, G., and Love, P.E.D., ―Management of risks in information technology
projects‖, Industrial Management & Data Systems, Vol. 104, No. 4, pp. 286-295, 2004.
[38] Boban, M., Pozgaj, Z., and Sertic, H., “Strategies for successful software development risk
management‖, Management, vol. 8, no. 2. pp. 77-91, 2003.
[39] Shahzad, B., and Safvi, S.A., “Risk mitigation and management scheme based on risk
priority‖, Global journal of computer science and technology, vol. 10, no.4, pp. 108-113, 2010.
[40] Arshad, N.R., Mohamed, A., and 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.
[41] Zhou, L., Vasconcelos, A., and Nunes, M., ―Supporting decision making in risk management
through an evidence-based information systems project risk checklist‖, Information Management
and Computer Security, vol. 16, no. 2, pp. 166-186, 2008.
[42] Dey, P.K., Kinch, J., and Ogunlana, S.O., “Managing risk in software development projects:
a case study‖, Industrial management and Data Systems, vol. 107, no. 2, pp. 284-303, 2007.
[43] Neumann, D.E., ―An enhanced neural network technique for software risk analysis‖, IEEE
Transactions on Software Engineering, vol. 28, no. 9, pp. 904 – 912, September 2002.
[44] Chen, J.C., and Huang, S.J., ―An empirical analysis of the impact of software development
problems factors software maintainability‖, The Journal of Systems and Software, vol. 82, no. 6,
pp. 981-992, 2009.
[45] Engel, A., and Last, M., ―Modeling software testing costs and risks using fuzzy logic
paradigm‖, Journal of Systems and Software, vol. 80, no.6, pp. 817-835, June 2007.
Page 5
173
[46] Lyytinen, K., Mathiassen, L., and Ropponen, J., ―Attention Shaping and Software Risk—A
Categorical Analysis of Four Classical Risk Management Approaches‖, Information Systems
Research, vol. 9, no. 3, pp. 233-255, September 1998.
[47] Mathiassen, L., Seewaldt, T., and Stage, J., ―Prototyping and Specifying: Principles and
Practices of a Mixed Approach‖, Scandinavian Journal of Information Systems, vol. 7, vo. 1, pp.
55–72, 1995.
[48] Woodruff, C.K., ―Managing the results: an examination of professional group perceptions
of organizational practice‖, Information and Management, vol. 19, pp.135-147, 1990.
[49] McLean, E.R., Smits, S.J., and Tanner, J.R., ―The importance of salary on job and career
attitudes of information systems professionals‖, Information and management, vol. 30, pp. 291-
299, 1996.
[50] Rasch, R. H., and Henry L. T., ―Factors Affecting Software Developers' Performance: An
Integrated Approach‖, MIS Quarterly, vol. 16, no. 3, pp. 395-413, 1992.
[51] Hoegl, M. and Gemuenden, H., “Teamwork Quality and the Success of Innovative Projects:
A Theoretical Concept and Empirical Evidence‖, Organization Science, vol. 12, no. 4, pp. 435-
449, 2001.
[52] Kendra, K., and Taplin, L., ―Project success – a cultural framework‖, Project management
journal, vol. 35, no. 1, pp. 30 - 45, 2004.
[53] Chan, C. L., Jiang, J. J., and Klein, G., ―Team task skills as a facilitator for application and
development skills‖, IEEE Transaction on Engineering Management, vol. 55, no. 3, pp. 434-441,
2008.
[54] Aladwani, A. “An Integrated Performance Model of Information Systems Projects‖, Journal
of Management Information Systems, vol. 19, no.1, pp. 185-210, 2002.
[55] Yen, H. R., Li, E. Y., and 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, vol. 45, no. 6, pp. 394-402, 2008.
[56] Krishna, S., Sahay, S., and Walsham, G., ―Managing cross-cultural issues in global
software outsourcing‖, Communications of the ACM, vol.47, no. 4, pp. 62-66, 2004.
Page 6
174
[57] Rainer, A., and Hall, T., "Identifying the Causes of Poor Progress in Software Projects,"
metrics, 10th IEEE International Symposium on Software Metrics (METRICS'04), pp. 184- 195,
2004.
[58] Sabherwal, R., ―The role of trust in outsourced IS development projects‖, Communications
of the ACM, vol. 42, no. 2, pp. 80-86, 1999.
[59] Babar, M.A., Verner J.M., and Nguyen, P.T., ―Establishing and maintaining trust in
software outsourcing relationships: An empirical investigation‖, Journal of Systems and
Software, vol. 80, no. 9, pp. 1438-1449, September 2007.
[60] Nicholson, B., and Sahay, S., ―Some political and cultural issues in the globalization of
software development: case experience from Britain and India‖, Information and Organization,
vol. 11, pp. 25-43, 2001.
[61] Tafti, M., ―Risks factors associated with offshore IT outsourcing‖, Industrial Management
and Data Systems, vol. 105, no. 5, pp. 549 – 560, 2005.
[62] Smith, M., Mitra, S. and Narasimhan, S., ―Offshore outsourcing of software development
and maintenance: A framework for issues‖, Information and Management, vol. 31, pp. 165-175,
1996
[63] Delmonte, A., and McCarthy, R., ―Offshore software development: Is the benefit worth the
risk?‖, Americas Conference on Information Systems (AMCIS) AMCIS 2003 Proceedings, pp.
1607-1613, 2003.
[64] Sharma, R., Apoorva, S.R., Madireddy, V., and Jain, V., ―Best Practices for Communication
between Client and Vendor in IT Outsourcing Projects‖. Journal of Information, Information
Technology, and Organizations, vol. 3, pp. 61-93, 2008.
[65] Arora, A., Arunachalam, V.S., Asundi, J., and Fernandes, R., ―The Indian software services
industry‖, Research Policy, vol. 30, no. 8, pp. 1267-1287, 2001.
[66] Athreye, S., “The Indian Software industry and its evolving service capability‖, Industrial
and Corporate Change, vol. 14, no. 3, pp. 393-418, 2005.
[67] Mcmanus. J., ―Risk management in software development projects‖, Elsevier Butterworth-
Heinemann, Great Britain, 2004.
Page 7
175
[68] Yong, H., Juhua, C., Zhenbag, R., Liu, M., and Kang, X., “Neural Networks Approach for
Software Risk Analysis‖, ICDMW „06 proceedings of the sixth IEEE International Conference on
Data Mining – Workshops, pp 722-725, 2006.
[69] Brooks, F.P.,―The Mythical Man –month: Essays on Software Engineering‖, Addison
Wesley Longman, 1995
[70] Mangione. C., “Software Project Failure: the Reasons, the Costs, CIO Updates‖,
http://www.cioupdate.com/reports/article.php/1563701/Software-Project-Failure-The-Reasons-
The-Costs.htm, Assessed on 20th September 2008.
[71] Jia, R., and Reich, B. H., ―IT Service Climate: An Extension to IT Service Quality
Research‖, Journal of the Association of Information Systems, vol. 9, no. 5, pp. 294-320, 2008.
[72] Baar, B.D., “Surprise, now you’re a software project manager”, Multi- media publication
Inc., 2006.
[73] Turner J.R. and Muller R., ―On the nature of the project as a temporary organization‖,
International Journal of Project Management, vol. 21, pp.1-8, 2003.
[74] Agarwal, N., and Rathod, E.U., "Defining Success for Software Projects: An Exploratory
Revelation‖, The Journal of Systems and Software, vol. 24, 2005.
[75] Wright J.N., ―Time and Budget: the twin imperatives of a project sponsor”, International
Journal of project management, vol. 15, no. 3, pp. 181-186, 1997.
[76] Atkinson R., Crawford, L., and Ward, S., ―Fundamental uncertainties in projects and the
scope of project management‖, International Journal of Project Management, vol. 24, pp. 687-
698, 2006.
[77] Watts, N., ―The Triple Constraints of project management‖, Business FFWD,
http://businessffwdblog.com/?m=200909, assessed 12th February 2010.
[78] Wateridge, J., “How Can IS/IT Projects Be Measured For Success?‖, International Journal
of Project Management, vol.16, no. 1, pp. 59- 63, 1998.
Page 8
176
[79] Procaccino, D.J., Verner, S.O., and Marvin, D., ―Case Study: Factors for Early Prediction
of Software Development Success‖, Journal of Information and Software Technology, vol. 44,
pp. 53-62, 2002.
[80] Verner, J.M., Beecham, S., and 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, pp. 25-33, 2010.
[81] Pinto, J.K., and Mantel, S.J., “The causes of project failure‖, IEEE Transactions of
Engineering Management, vol. 37, no.4, pp. 269-276, 1990.
[82] Ghasabeh, S.M., and Chabok, K.K., ―Generic Project success and project management
success criteria and factors. Literature review and survey‖, WSEAS Transactions on business
and economics, vol. 6, no. 8, pp. 456-468, 2009.
[83] Wateridge J, “IT projects: a basis for success‖, International Journal of Project
Management, vol, 13, no. 3, pp. 169-172, 1995.
[84] Linberg, K. R., “Software developer perceptions about software project failure: a case
study‖, The Journal systems and software, vol. 49, pp. 177-192, 1999.
[85] Baker, B. N., Murphy, D. C., and Fisher, D., “Factors affecting project success‖, Project
Management Handbook, second edition, New York: Van Nostrand Reinhold, pp. 902 – 909, 1988
[86] Baccarini, D., ―The logical framework method for defining project success‖, Project
Management Journal, vol. 30, no. 4, pp. 25-32, 1999.
[87] Prifling, M., “The Organizational Culture's Influence on Risks in IT Projects - a
Structuration Perspective‖, Proceedings of the Sixteenth Americas Conference on Information
Systems, Lima, Peru, August 12-15, pp. 1-9, 2010.
[88] Hidding, G. and Nicholas, J., ―Reducing I.T. Project Management Failures: A Research
Proposal‖, 42nd Hawaii International Conference on System Sciences, Big Island, Hawaii, USA,
2009.
[89] Thomas, G. and Fernandez, W., “Success in IT Projects: A Matter of Definition?‖,
International Journal of Project Management, vol. 26, pp. 733-742, 2008.
Page 9
177
[90] Pressman, R.S., “Software engineering. A practitioner’s approach‖, Sixth edition, Mc-Graw
Hill International, 2005.
[91] Stiller, E., and Leblanc, C., ―Project based- software engineering: An object-oriented
approach‖, Addison Wesley, 2002.
[92] Antonov, A., Nikolov, V., Yanakieva, Y., "Risk Simulation in Project Management
System", International Conference on Computer Systems and Technologies- Compsystech, 2006.
[93] Galorath, D.D., and Evans, M.W., "Software Sizing Estimation and Risk Management",
Auerbach Publications, United States of America, pp. 339-393, 2006.
[94] Charette R., ―Software engineering risk analysis and management‖, Mc. Graw-hill, New
York, NY, 1989.
[95] Charette, R.N., Adams K.M., and White M.B., ―Managing risk in software maintenance‖,
IEEE Software, vol. 14, no. 3, pp. 43–50, 1997.
[96] Barki, H., Rivard, S., and Talbot, J., “Toward an Assessment of Software Development
Risk‖, Journal of MIS, vol. 10, no. 2, pp. 203-225, 1993.
[97] Barki, H., Rivard, S., and Talbot, J., “An Integrative Contingency Model of Software Project
Risk Management”, Journal of MIS, vol.17, no. 4, pp. 37-69, 2001.
[98] Higuera, R. and Haimes Y., ―Software Risk Management‖, Carnegie Mellon University,
Software Engineering Institute, 1996.
[99] Madachy R., ―Heuristic risk assessment using cost factors”, IEEE Software, vol. 14, no. 3,
pp. 51–59, 1997.
[100] Benaroch M., ―Managing Information Technology Investment Risk: A Real Options
Perspective‖, Journal of MIS, vol.19, no. 2, pp. 43-84, 2002.
[101] Benaroch M., Lichtenstein Y. and Robinson K., ―Real Options in IT Risk Management: An
Empirical Validation of Risk-Option Relationships‖, MIS Quarterly, vol. 30, no. 4, pp. 827-864,
2006.
Page 10
178
[102] Purao, S., Paul, S., and Smith, S., “Understanding enterprise integration project risks: A
focus group study‖, 18th International Workshop on Database and Expert Systems Applications,
pp. 850-854, 2007.
[103] Gefen, D., Wyss, S., and Lichtenstein, Y., ―Business Familiarity as Risk Mitigation in
Software Development Outsourcing Contracts‖, MIS Quarterly, vol. 32, no. 3, pp. 531-551,
2008.
[104] Charette R.N., ―The mechanics of managing IT risk‖, Journal of information Technology,
vol. 11, no. 4, pp. 373-378, 1996.
[105] March, J.G., and Shapira, Z., ―Managerial perspectives on risk and risk taking‖,
Management science, vol. 33, no. 11, pp. 1404-1418, 1987.
[106] Zhang, H., “A redefinition of the project risk process: suing vulnerability to open up the
event –consequence link”, International journal of project management, vol. 25, no. 7, pp. 694-
701, 2007.
[107] Oz, E., and Sosik, J., ―Why information systems projects are abandoned: a leadership and
communication theory and exploratory study‖, Journal of Computer Information Systems, pp 66-
78, Fall, 2000.
[108] Dash, R., and Dash, R., ―Risk Assessment Techniques for Software Development‖,
European Journal of Scientific Research, vol. 42, no. 4, pp. 615-622.
[109] Mensah, E.K., ―Software development failures‖, The MIT press, Cambridge, MA, 2003.
[110] Doherty, N.F., and King, M., “From technical to socio-technical change: tackling the
human and organisational aspects of systems development projects‖, European Journal of
Information Systems, vol. 14, pp. 1-5, 2005.
[111] Nelson, R.R., “IT project management: infamous failures, classic mistakes and best
practices‖, MIS Quarterly Executive, vol. 6, no. 2, pp. 67-78, 2007.
[112] Snow, A. P., Keil, M., and Wallace, L., ―The Effects of Optimistic and Pessimistic Biasing
on Software Project Status Reporting‖, Information and Management, vol. 44, no. 2, pp. 130-
141, 2007.
Page 11
179
[113] Keil, M., Paul, I.M.G., and Mahring, M., ―Reporting bad news on software projects: the
effects of culturally constituted views of face-saving‖, Information of Systems Journal, vol. 17,
no.1, pp. 59-87, 2007.
[114] Genuchten M.V., ―Why is software late? An empirical study of reasons for delay in
software development‖, IEEE Transactions software engineering, vol. 17, no. 6, pp. 582-590,
1991.
[115] Swede. V.V., and Vliet. J.V., ―Consistent development: results of a first empirical study on
the relation between project scenario and success‖, proceeding sixth CAiSE conference., 1994.
[116] Sherer, S., ―The Three dimensions of software risk: Technical, Organizational, and
Environmental‖, presented in 28th Annual Hawaii International conference on system sciences,
1995.
[117] Field, T. 1997. ―When BAD things Happen to GOOD projects”, CIO, pp. 55-62.
[118] Reel, J.S., “Critical success factors in Software Projects‖, IEEE Software, May – June, 18-
23, 1999.
[119] Schmidt, R., Lyytinen, K., Keil, M., and Cule, P., ―Identifying software project risks: An
international Delphi study‖, Journal of Management Information Systems, vol. 17, no. 4, pp. 5-
36, 2001.
[120] Jiang, J., and Klein, G., “Software project risks and development focus”, Project
Management Journal, vol. 32, no. 1, pp. 20-26, 2001.
[121] Addison, T., and Vallabh, S., “Controlling software project risks: An empirical study of
methods used by experienced project managers”, Proceedings of SAICSIT. Port Elizabeth, pp.
128-140, 2002.
[122] Demarco, T., and Lister, T., “Waltsing with bears: managing risk on software projects‖,
Dorset Publishing Co. New York, 2003.
[123] Lu, X., and Ge, Y., ―Risk analysis in project of software development‖, Engineering
Management Conference, Managing Technologically Driven Organizations: The Human Side of
Innovation and Change, vol. 2, no. 4, pp. 72 – 75, 2003.
Page 12
180
[124] Smith, D., Eastcroft, M., Mahmood, N., and Rode, H., ―Risk factors affecting software
projects in South Africa‖, South African Journal of Business Management, vol. 37, no. 2, pp.55-
65, 2006.
[125] Iacovou, C.L., and Nakatsu, R., ―A risk profile of offshore-outsourced development
projects‖, Communications of the ACM, vol. 51, no. 6, pp.89-94, 2008.
[126] Verner, J.M., Evanco, W.M., and Cerpa, N., “State of the practice: An exploratory analysis
of schedule estimation and software project success prediction”, Information and Software
Technology, vol. 49, no. 2, pp. 181-193, February 2007
[127] Leitheiser, R. L., and Wetherbe, J. C. ―Service Support Levels: An Organized Approach to
End-User Computing‖, MIS Quarterly, vol.10, no.4, pp. 336-350, 1986.
[128] Barki, H., and Hartwick, J., ―Rethinking the concept of user involvement”, MIS Quarterly,
vol. 13, no.1, pp. 53-63, 1989.
[129] Gioia, J. 1996. “Twelve Reasons Why Programs Fail‖, PM Network, pp.16-20, November
1996.
[130] Nah .F., Lau, J., Kuang, J., ―Critical factors for successful implementation of enterprise
systems‖, Business Process management Journal, vol. 7, no. 3, pp. 285-296, 2001.
[131] Engming, L. and and Hsieh, C.T., ―Seven deadly risk factors of software development
projects‖, Journal of Systems Management, vol. 36, no. 6, pp. 38-42, 1994.
[132] Irani, Z., Love, P.E.D., “The propagation of technology management taxonomies for
evaluating information systems‖, Journal of management information systems, vol. 17, no. 3, pp.
161-177, 2001.
[133] Mursu, A., Soriyan, H.A., and Olufokunbi, K.C., “Toward Successful ISD in Developing
Countries: First Results from a Nigerian Risk Study Using the Delphi Method‖, 1996. Available
at: http://iris22.it.jyu.fi/iris22/pub, accessed 25 June 2009.
[134] Jones, C., “Assessment and Control of Software Risks‖, Prentice-Hall, Englewood Cliffs,
NJ., 1993.
Page 13
181
[135] Shull, F., Rus, I., and Basili, V., ―How perspective-based reading can improve
requirements inspections‖, Computer, vol. 33, no. 7, pp.73-79, 2000.
[136] King, J., ―Sketchy plans, politics stall software development”, Computer World, vol. 29 no.
24, p. 81, 1994.
[137] Clancy, T., “Chaos – IT development projects‖, 1995, available at:
www.standishgroup.com/msie.htm, (accessed 19 August 2009).
[138] Rasmussen, M., Orlov, L.M., and Bright, S., “Taking Control Of IT Risk Defining A
Comprehensive IT Risk Management Strategy‖, Forrester Research, 2006
[139] Hu, Y., Huang, J., Chen, J., Liu, M., Xie, K., ―Software Project Risk Management
Modeling with Neural Network and Support Vector Machine Approaches”, ICNC, Third
International Conference on Natural Computation (ICNC 2007), vol. 3, pp.358-362, 2007
[140] Han. W.M., and Huang, S.J., ―An empirical analysis of risk components and performance
on software projects‖, Journal of systems and software, vol. 80, no. 1, pp. 42-50, 2007.
[141] Keil, M., Tiwana, A., and Bush, A., ―Reconciling user and project manager perceptions of
IT project risk: a Delphi study‖, Information Systems Journal, vol. 12, no. 2, pp. 103-119, 2002.
[142] Krasner, H., ―Looking over the legal edge of unsuccessful software projects‖, Cutter IT
Journal, vol. 11, no. 3, pp. 11-22, 1998.
[143] Turner J.R., ―Project Management: a profession based on knowledge or faith‖,
International Journal of Project Management, vol. 17, no. 6, pp. 329-342, 1999.
[144] Hamid, A., Sengupta, T.K. and Swett, C., ―The Impact of Goals on Software Project
Management: An Experimental Investigation,‖ MIS Quarterly, vol. 23, no.4, pp. 531-555, 1999.
[145] Martin, E.W., Dehayes, D.W., Hofffer, J.A., and Perkin, W.C., ―Managing information
Technology: What managers need to know‖, 2nd Edition, Prentice Hall, New Jersey, 1994.
[146] Cunningham, M., ―It’s all about the business‖, Inform, vol. 13, no. 3, pp. 83, 1999.
[147] Lubelczyk, J., and Parra, A., ―Recommended Approach to Software Development‖,
Revision 3. Software Engineering Laboratory, NASA, June 1992.
Page 14
182
[148] Masticola S.P., ―A simple estimate of the cost of software project failures and the
breakeven effectiveness of project risk management‖, First international workshop on the
economics of software and computation, IEEE, 2007.
[149] Cadle J., and Yeate, D., ―Project management for information systems‖, Prentice-hall.
Harlow, 2001.
[150] Smite, D., ―Requirements Management in Distributed Projects‖, Journal of Universal
Knowledge Management, vol. 1, no. 2, pp. 69-76, 2006.
[151] Thomsett, R., ―Project Pathology: Causes, Patterns and Symptoms of Project Failure –
Training Notes Project Risk Management‖, Thomsett Company, London, 1995.
[152] McLeod, G. and Smith, D., “Managing IT Projects”, Boyd and Fraser Publishing,
Massachusetts, 1996
[153] Sakthivel, S., ―Managing Risk in Offshore Systems Development”, Communications of the
ACM, vol. 50, no. 4, pp.69-75, 2007.
[154] Pan, J., ―Software Reliability”, Carnegie Mellon University, 1999,
http://www.ece.cmu.edu/~koopman/des_s99/sw_reliability, assessed on 24th August 2010.
[155] Lewin, K., Lippitt, R., and White, R.K., ―Patterns of aggressive behavior in experimentally
created social climates‖, Journal of Social Psychology, vol. 10, pp. 271-299, 1939.
[156] Lewin, K., “Field Theory in Social Science‖, NY: Harper and Row, 1951.
[157] Schneider, B., ―The climate for service: An application of the climate construct ,”
Organizational Climate and Culture, Jossey-Bass, CA, pp. 383-412, 1990.
[158] Likert, R., “The Human Organization: Its Management and Value‖, New York: McGraw
Hill, 1967.
[159] Litwin, G.H. and Stringer, R.A., “Motivation and Organizational Climate‖, Harvard
University Press, Boston, MA, 1968.
[160] Schein, E.H. (2000) ―Sense and nonsense about culture and climate”, N.M. Ashkanasy,
C.P.M., 2000.
Page 15
183
[161] Carr, J.Z., Schmidt, A.M., Ford, J.K., and DeShon, R.P., “Climate Perceptions Matter: A
Meta-Analytic Path Analysis Relating Molar Climate, Cognitive and Affective States, and
Individual Level Work Outcomes,‖ Journal of Applied Psychology, vol.88, no.4, pp. 605–619,
2003.
[162] DeCotiis, T.A. and Summers, T.P., ―A path analysis of a model of the antecedents and
consequences of organizational commitment,‖ Human Relations, vol. 40, pp. 445-470, 1987.
[163] Schnake, M. E., ―An empirical assessment of the effects of affective response in the
measurement of organizational climate‖, Personnel Psychology, vol. 36, pp. 791–807, 1983.
[164] Lawler, E.E., Hall, D.T., and Oldham, G.R., ―Organizational climate: Relationship to
organizational structure, process and performance‖, Organizational Behavior and Performance,
vol. 11, pp. 139–155, 1974.
[165] Schneider, B., Parkington, J., and Buxton, V., “Employee and customer perceptions of
service in banks,‖ Administrative Science Quarterly, vol.25, pp. 252-267, 1980.
[166] Schneider, B., White, S.S., and Paul, M.C., ―Linking Service Climate and Customer
Perceptions of Service Quality: Test of a Causal Model‖, Journal of Applied Psychology, vol. 83,
no. 2, pp. 150-163, 1998.
[167] Schneider, B., Ashworth, S.D., Higgs, C., and Carr, L., ―Design, validity, and use of
strategically focused employee attitude surveys‖, Personnel Psychology, vol.49, pp. 695-705,
1996.
[168] Zohar, D., ―A group-level model of safety climate: Testing the effect of group climate on
microaccidents in manufacturing jobs,” Journal of Applied Psychology, vol. 85, pp. 587-596,
2000
[169] Lin, C., Madu, C.N., and Kuei, C.H., ―The association between organizational climate and
quality management practices: an empirical study on small-and medium-sized manufacturing
companies in Taiwan,‖ Total Quality Management, vol.10, no.6, pp. 863-868, 1999.
[170] Borucki, C.C. and Burke, M.J., ―An examination of service-related antecedents to retail
store performance,‖ Journal of Organizational Behavior, vol. 20, pp. 943-962, 1999.
Page 16
184
[171] Kopelman, R.E., Brief, A.P., and Guzzo, R.A., ―The role of climate and culture in
productivity,‖ in B. Schneider (ed.), Organizational Climate and Culture, Jossey-Bass, CA, pp.
282-318, 1990
[172] Schneider, B. and White, S.S., “Service Quality: Research Perspectives‖, Sage, CA, 2004.
[173] Denison, D.R., ―What is the difference between organizational culture and organizational
climate? A native’s point of view on a decade of paradigm wars,‖ Academy of Management
Review, vol. 21, pp. 619-654, 1996.
[174] Isaksen, S.G., Lauer, K.J., Ekvall, G., and Britz, A., ―Perceptions of the best and worst
climates for creativity: preliminary validation evidence for the situational outlook
questionnaire‖, Creativity Research Journal, vol.13, pp. 171-184, 2001
[175] Ekvall, G., ―Creative Climate‖, Encyclopedia of creativity, vol 1, New York: Academic
Press, pp. 403-413, 1999.
[176] Isaksen, S. G., and Ekvall, G., ―Assessing the context for change: A technical manual for
the Situational Outlook Questionnaire‖, Orchard Park, NY: The Creative Problem Solving
Group, 2007.
[177] Gupta A., ―The organizational climate study‖. Institute of Rural management, Anand.
June-July 2008.
[178] Campbell, J.P., Dunnette, M.D., Lawler, E.E., and Weick, K.E., “Managerial Behavior,
Performance, and Effectiveness‖, McGraw-Hill, NY, 1970.
[179] Schein, E.H., “Organizational Culture and Leadership‖, Jossey-Bass, CA, 1985
[180] Schein, E.H., “Organizational Culture and Leadership: A Dynamic View‖, Jossey-Bass,
CA, 1992.
[181] Trice, H.M. and Beyer, J.M., “The Cultures of Work Organizations‖, Prentice Hall, NJ,
1993.
[182] Ein-Dor, P. and Segev. E., ―Organizational context and MIS structure: Some empirical
evidence,‖ MIS Quarterly, pp. 55-68, 1982.
Page 17
185
[183] Boynton, A.C., Zmud, R.W., and Jacobs, G.C., “The influence of IT management practice
on IT use in large organizations‖, MIS Quarterly, vol. 18, no.3, pp. 299-318, 1994.
[184] Watts, S. and Henderson, J.C., ―Innovative IT climates: CIO perspectives,” Journal of
Strategic Information Systems, vol. 15, pp. 125–151, 2006.
[185] Hyvari I., “Success of projects in different organizational conditions”, Project management
journal, vol. 37, no.4, pp.31-41, 2006.
[186] Huang, H. and Trauth, E., “Cultural Influences and Globally Distributed Information
Systems Development: Experiences from Chinese IT Professionals”, In: Proceedings of ACM
SIGMIS-CPR Conference, St Louis, Missouri, USA, pp.36-45, April 2007.
[187] Acuna, S.T., Gomezand, M., Natalia Juristo, N., “Towards understanding the relationship
between team climate and software quality—a quasi-experimental study”. Empirical Software
Engineering, vol. 13, no. 4, pp.401-434, August, 2008.
[188] Couger, J.D., ―Measurement of the climate for creativity in I.S. organizations‖,
Proceedings of the 27th Annual Hawaii International Conference on System Sciences, pp. 351-
357, 1994.
[189] Janz, B.D., Wetherbe, J., Davis, G.B., and Noe, R.A., ―Reengineering the systems
development process: The link between autonomous teams and business process outcomes,‖
Journal of Management Information Systems, vol.14, no.1, pp. 41-68, 1997.
[190] Banerjee, D., Cronan, T.P., and Jones, T.W., ―Modeling IT ethics: A study in situational
ethics,” MIS Quarterly, vol. 22, no.1, pp. 31-60, 1998.
[191] Blanton, J.E., Schambach, T., and Trimmer, K.J., “Factors affecting professional
competence of information technology professionals,‖ Proceedings of the ACM SIGCPR
Conference, pp. 4-19, 1998.
[192] Trimmer, K.J., Blanton, J.E., and Schambach, T., ―An evaluation of factors affecting
professional obsolescence of information technology professionals,‖ Proceedings of the 31st
Hawaii International Conference on System Sciences, pp. 406-414, 1998.
[193] Tan, B.C.Y., Smith, H.J, Keil, M., and Montealegre, R., “Reporting bad news about
software projects: Impact of organizational climate and information asymmetry in an
Page 18
186
individualistic and a collectivistic culture‖, IEEE Transactions on Engineering Management, vol.
50, no.1, pp. 64-77, 2003
[194] Bock, G.W., Zmud, R.W., Kim, Y.G., and Lee, J.N., “Behavioral intention formation in
knowledge sharing: Examining the roles of extrinsic motivators, social-psychological forces, and
organizational climate‖, MIS Quarterly, vol. 29, no.1, pp. 87-111, 2005.
[195] Warkentin, M., Bekkeringy, E., Johnstonz, A.E., Moore, R., ―Risk Perspectives in Systems
Development”, Americas Conference on Information Systems (AMCIS) AMCIS 2007
Proceedings, pp. 1-12, 2007.
[196] Stephen, D., Keil, M., Mathiassen, M., Shen, Y., and Tiwana, A., ―Attention-shaping tools,
expertise, and perceived control in IT project risk assessment‖, Decision Support Systems, vol.
43, no.1, pp. 269-283, 2007.
[197] Liu, S., Zhang, J., Keil, M., Chen, T., ―Comparing senior executive and project manager
perceptions of IT project risk: a Chinese Delphi study”, Information system journal, vol. 20, no.4,
pp. 319-355, 2010.
[198] Isaac S. and Michael W. B., ―Handbook in research and evaluation (2nd ed.)‖, San Diego,
CA: EdITS Publishers, 1990.
[199] Whitman, M.E., and Woszczynski, A.B., “The handbook of information systems research”,
Idea Group Inc (IGI), 2004.
[200] Yin, R.K., “Case Study Research: Design and Methods”, Fourth Edition. SAGE
Publications. California, 2009.
[201] Rubin, A and Babbie, E., “Research methods for social work‖, Brooks/Cole Publishing
Company, Pacific Grove, Carlifornia.
[202] Kaiser H.F., ―The application of electronic computers to factor analysis‖, Educational and
Psychological Measurement, vol. 20, pp. 41-151, 1960.
[203] Gorsuch R. L., ―Factor analysis‖, 2nd ed., Hillsdale, NJ: Erlbaum, 1983.
[204] Buckingham, M., and Coffman, C., “First, Break All the Rules: What the World's Greatest
Managers Do Differently‖, Simon & Schuster, 2001
Page 19
187
[205] Bosco, G., ―Implicit theories of good leadership in the open-source community”
http://opensource.mit.edu/papers/bosco.pdf, 2004, Accessed: 12th January 2010.
[206] De-Souza, S. C., Anquetil, N., and de Oliveira, K.M., “Which documentation for software
maintenance?”, Journal of the Brazilian Computer Society, vol. 13, no. 2, pp.31-44, 2007.
[207] Mattsson, K.M., “Problems in agile trenches‖, Proceedings of the Second ACM-IEEE
international symposium on Empirical software engineering and measurement, Kaiserslautern,
Germany, October 09-10,2008, 2008.
[208] Aharon, Y., and Ilana, L., ―Changing students perception regarding software
documentation‖, MCIS 2010 Proceedings. Paper 91, 2010.
[209] Sabherwal, R., Sein, M., Marakas, G., ―Escalating Commitment to Information Systems
Projects: Findings from Two Simulated Experiments”, Information & Management, vol. 40, no.
8, pp.781-798, 2003.
[210] Jannson, A.S., “Software Maintenance and Process Improvement”, CMMI, UPTEC, pp 1-
50, November-December 2007.
[211] Avizienis, A., Laprie, J.C., Randell, B., and Landwehr, C., ―Basic Concepts and Taxonomy
of Dependable and Secure Computing‖, IEEE Transactions on Dependable and Secure
Computing, vol. 1, pp. 11-33, 2004.
[212] Thompson, R., Iacovou, C., Smith, H.J., ―Biased project status reports: A survey of IS
professionals”, 17th European conference on information systems, pp. 1 – 13, 2009.
[213] Otto, H.K., and Magee, C. L., ―Estimating Factors Affecting Project Task Size in Product
Development: An Empirical Study‖, IEEE Transactions on Engineering Management, vol. 53,
no.1, pp. 86-94, 2006.
[214] Francalanci, C., ―Predicting the implementation effort of ERP Projects: Empirical
Evidence on SAP/R3‖, Journal of Information Technology, vol. 16, pp.33-48, 2001.
[215] Laudise, T.M., and Nuara, L.T., ―How to contract for a successful e-commerce
development project: beating the odds‖, the business lawyer, vol. 58, 299-316, 2002.
Page 20
188
[216] Cornelius, E.T., ―Seven tactics to increase projects success‖, Collegiate project services,
http://www.collegiateproject.com/articles/SevenTactics.pdf, 2006, assessed 10th march 2010.
[217] Deutsch, M.S., ―An exploratory analysis relating the software project management process
to project success‖, IEEE Transactions, vol. 38, no.4, pp. 365 – 375, 1991.
[218] Renn, R., ―Moderation by goal commitment of the feedback-performance relationship:
theoretical explanation and preliminary study‖, Human Resource Management Review, vol. 13,
pp. 561-580, 2003.
[219] Hoegl, M. and Proserpio, L., ―Team member proximity and teamwork in innovative
projects‖, Research Policy, vol. 33, no.8, pp.1153-1165, 2004.
[220] Hoegl, M. and Parboteeah, K. P., “Autonomy and teamwork in innovative projects”,
Human Resource Management, vol.45, no.1, pp. 67-79, 2006.
[221] Hoegl, M. and Parboteeah, K. P., “Creativity in innovative projects: How teamwork
matters‖, Journal of Engineering and Technology Management, vol. 24, no. 1-2, pp. 148-166,
2007.
[222] Curtis, B., Krasner, H., and Iscoe, N. “A Field Study of the Software Design Process for
Large Systems," Communications of the ACM, vol. 31, no.11,pp 1268-1287, 1988.
[223] Kraut, R. E., and Streeter, L. A. “Coordination in Software Development”,
Communications of the ACM, vol.38, no.5, pp. 69-81, 1995.
[224] Crowston, K., and Kammerer, E.E. “Coordination and collective mind in software
requirements development”, IBM Systems Journal, vol. 37, no.2, pp 227-245, 1998.
[225] Adams, J. R., and Adams, L. L., ―The virtual project: managing tomorrow's team today‖,
PM Network, vol. 11, no.1, pp. 37-42, 1997.
[226] Wittenbaum, G.M., and Stasser, G., “Management of information in small groups. What’s
social about social cognition? Research on socially shared cognition in small groups”, Sage
Publications, Thousand Oaks, CA, pp. 3-28, 1996.
[227] Herbsleb, J., and Moitra, D., “Global software development”, IEEE Transactions on
Software Engineering, vol. 18, no. 2, pp. 16 – 20, 2001.
Page 21
189
[228] Espinosa, J. A., Cummings, J.N., Pearce, B.M., and Wilson, J.M., 2002, “Research on
Teams with Multiple Boundaries”, Hawaii International Conference on System Sciences, Big
Island, Hawaii, IEEE, January 2002.
[229] Espinosa, J. A., Cummings, J.N., Wilson, J.M., and Pearce, B.M., “Team Boundary Issues
Across Multiple Global Firms‖, Journal of Management Information Systems, vol. 19, no.4,
pp.157-190, 2003.
[230] 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, vol. 29, pp.219-238, 2008.
[231] Jurison, J., “Software project management: the manager’s view”, Communications of
association for information systems, vol. 2, no.17, pp. 2-57, 1999.
[232] Mensah, E.K., “Critical issues in abandoned information systems development projects‖,
Communications of the ACM, vol. 40, no.9, pp.74 – 80, 1997.
[233] Boehm B.W., “Software Engineering Economics”, Englewood Cliffs, NJ, Prentice-Hall,
1981
[234] Herzberg, F.I., “One more time: How do you motivate employees?”, Harvard Business
Review, vol. 65, no. 5, pp.109-120, Sep/Oct 1987.
[235] McConnell, S., “Rapid Development”. Redmond, WA: Microsoft Press, 1996.
[236] Procaccino, J.D., “Quantitative models for early prediction of software development
success: a practitioner’s perspective” Ph.D Dissertation, 2006.
[237] Ginzberg, M.J., “Early diagnosis of MIS implementation failure promising results and
unanswered questions‖, Management Science, vol. 27, no.4, pp. 459-478, 1981.
[238] Jiang, J., Klein G., Means, T.L., “Project risk impact on software development teams
performance”, Project Management Journal, vol. 31, no.4, pp.19-26, 2000.
[239] Kahn, R. L., “Conflict, Ambiguity, and Overload: Three Elements in Job
Stress”, Occupational Mental Health, vol.3, pp.2-9, 1973.
Page 22
190
[240] Whitmaker, B., McKinney, J., “Role clarity, social skills and the feedback seeking job
satisfaction link”, International Journal of Organizational Behavior, vol.14, no.1, pp.54-68, 2009.
[241] Braun, F., and 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, 1-11, 2007.
[242] Rizzo, J., House, R., and Lirtzman, S., “Role conflict and ambiguity in complex
organizations”, Administrative Science Quarterly, vol.15, pp.150-163, 1970.
[243] Abramis, D., “Work role ambiguity, job satisfaction, and job performance: Meta-analyses
and review”, Psychological Reports, vol. 75, pp. 1411-1433, 1994.
[244] Glisson, C., and Durick, M., “Predictors of job satisfaction and organizational commitment
in human service organizations‖, Administrative Science Quarterly, vol. 33, no.1, pp. 61-81.,
1988.
[245] Organ, D., and Greene, C., “Role ambiguity, locus of control, and work satisfaction”,
Journal of Applied Psychology, vol.59, pp.101-102, 1974.
[246] Sawyer, J., “Goal and process clarity: Specification of multiple constructs of role
ambiguity and a structural equation model of their antecedents and consequences”, Journal of
Applied Psychology, vol. 77, pp. 69-86, 1992.
[247] Louis, M., Posner, B., and Powell, G., “The availability and helpfulness of socialization
practices‖, Personnel Psychology, vol. 36, pp. 857-866, 1983.
[248] Morrison, E., “Longitudinal study of the effects of information seeking on newcomer
socialization‖, Journal of Applied Psychology, vol. 78, pp.173-183, 1993.
[249] London, M., and Smither, J., “Can working with an executive coach improve multisource
feedback ratings over time? A quasi-experimental field study‖, Personnel Psychology, vol. 56,
pp. 23-46, 2002.
[250] Belbin, R. M., “Management Teams‖, John Wiley & Sons, New York, 1981
[251] Schneidewind, N., “Software reliability engineering process‖ , Innovations in Systems and
Software Engineering, vol. 2, no. 3-4, pp. 179-190, 2006.