Defining 'success' for software projects: An exploratory revelation

被引：158
作者：
Agarwal, Nitin [1 ]
Rathod, Urvashi [2 ]
机构：
[1] Indian Institute of Management Indore, Tahsil: MHOW, Indore, MP 453 331, Pigdamber, Rau
[2] ICFAI Business School Indore, Rajiv Gandhi Chouraha, Indore, MP 452 017, Piplyapala
来源：
International Journal of Project Management | 2006年 / 24卷 / 04期
关键词：
Managing projects; Software project success criteria; Success and strategy;
D O I：
10.1016/j.ijproman.2005.11.009
中图分类号：
学科分类号：
摘要：
Success is found relatively rare in the world of software projects. One possible reason may be the difference in the perception of the meaning of 'success' in the minds of people who evaluate the project performance. Usually, stakeholders external to the project organization use target cost and time for inferring 'project success' while those internal to project agree that the attainment of 'scope' of development decides the 'project success'. Hence, project success criteria, as believed by different groups of stakeholders, do not match. In this study, we examine the views of one such internal set of stakeholders: Programmer/Developers, Project Managers and Customer Account Managers. We conducted an exploratory survey to determine their view of a successful project. We found surprising uniformity in different constituents of this particular group of stakeholders and all of them overwhelmingly considered meeting the 'scope' of software projects, which comprises the functionality and quality of the project outcome, as the highest determinant of success. We believe that this view of software project success in the eyes of software professionals should be studied further to build a comprehensive project evaluation framework and should be utilized effectively to achieve success in terms of external objectives like customer satisfaction and customer happiness. © 2005 Elsevier Ltd and IPMA.
引用
收藏
页码：358 / 370
页数：12
相关论文
共 18 条
  • [1] Lyytenin K., Expectation failure concept and systems analyst's view of information systems failures: results of an exploratory study, Informat Manage, 14, 1, pp. 45-56, (1988)
  • [2] Paulk M.C., Weber C.V., Curtis B., Chrissis M.B., : guidelines for improving the software process, (1994)
  • [3] Hoch D.J., Roeding C.R., Purkert G., Lindner S.K., Secrets of software success, (2000)
  • [4] Brooks F.P., No silver bullet: essence and accidents of software engineering, IEEE Comput, 20, 4, pp. 10-19, (1987)
  • [5] de Wit A., Measurement of project success, Int J Project Manage, 6, 3, pp. 164-170, (1988)
  • [6] Deane R.H., Clark T.B., Creating a learning project environment, Informat Syst Manage, 14, 3, pp. 54-61, (1997)
  • [7] Shenhar A.J., Levy O., Mapping the dimensions of project success, Project Manage J, 28, 2, pp. 8756-9728, (1997)
  • [8] Atkinson R., Project management: cost, time and quality, two best guesses and a phenomenon, its time to accept other success criteria, Int J Project Manage, 17, 6, pp. 337-342, (1999)
  • [9] Turner J.R., Project management: a profession based on knowledge or faith, Int J Project Manage, 17, 6, pp. 329-330, (1999)
  • [10] Pinto J.K., Mantel Jr. S.J., The causes of project failure, IEEE Trans Eng Manage, 37, 4, pp. 269-276, (1990)
12