Managing the Effects of Rapid Technological Change on Complex Information Technology Projects

被引：5
作者：
Durney C.P. [1 ]
Donnelly R.G. [2 ]
机构：
[1] Phase One Consulting Group, 10111 Chickadee Lane, Adelphi, 20783, MD
[2] Department of Information Systems & Technology Management, School of Business, The George Washington University, 2201 G St NW Ste 515, Washington, 20052, DC
来源：
Journal of the Knowledge Economy | 2015年 / 6卷 / 4期
关键词：
Project Manager; Project Team; Absorptive Capacity; Enterprise Architecture; Project Renew;
D O I：
10.1007/s13132-012-0099-2
中图分类号：
学科分类号：
摘要：
A contributing cause to the too-frequent failures of large, complex information technology (IT) projects is the inability of standard project management practices to deal with the effects of rapid technological change. Rapid change creates significant uncertainties that can blindside the most cautious project managers. Based on a long history of working with these kinds of projects, we examine the characteristics that make some projects susceptible to these effects. Then, using illustrations drawn from Project Renew, a multiyear US federal agency IT modernization effort, we present some techniques that go beyond traditional project management practices to help managers of large, complex IT projects deal more successfully with the effects of rapid technological change. © 2012, Springer Science+Business Media, LLC.
引用
收藏
页码：641 / 664
页数：23
相关论文
共 52 条
  • [1] Charette R.N., Why software fails, IEEE Spectrum Online, (2005)
  • [2] Goldstein H., Who killed the virtual case file?, IEEE Spectrum Online, (2005)
  • [3] Stamati T., Kanellis P., Martakos D., Challenges of complex information technology projects: the MAC initiative, J Cases Inf Technol, 7, 4, pp. 46-64, (2004)
  • [4] Standish Group International, Inc, The CHAOS report, (1995)
  • [5] Eveleens J.L., Verhoef C., The rise and fall of the chaos report figures, IEEE Softw, 27, 1, pp. 30-36, (2010)
  • [6] Glass R.L., The Standish report
  • [7] does it really describe a software crisis?, Commun ACM, 49, 8, (2006)
  • [8] Young R., Jordan E., Top management support: mantra or necessity?, Int J Proj Manag, 26, 7, pp. 713-725, (2008)
  • [9] Barki H., Rivard S., Talbot J., An integrative contingency model of software project risk management, J Manag Inf Syst, 17, 4, pp. 37-69, (2001)
  • [10] Cherpa N., Verner J., Why did your project fail, Commun ACM, 52, 12, pp. 130-134, (2009)
123456