首页> 外文会议>Information Resources Management Association International Conference >Virtual Project risk vs. Traditional Project risk in Software Projects
【24h】

Virtual Project risk vs. Traditional Project risk in Software Projects

机译:虚拟项目风险与传统项目风险软件项目

获取原文

摘要

This research is designed to distinguish virtual and traditional project risks and specifically to identify the critical risks in virtual software projects. The resulting list of critical risks will provide guidance on managing risks for project leaders working in a virtual team environment. Three areas are important to the discussion of virtual software project risk: virtual software project teams, project failure and project risk. Virtual software project teams are a growing phenomenon. They are called virtual because team members are not co-located. "Virtual teams are groups of geographically, organizationally and/or time dispersed workers brought together by information and telecommunication technologies to accomplish one or more organizational tasks (Powell et al., 2004)". Many driving forces are causing increased dependence on these teams, including off-shoring, outsourcing, reduced business travel due to security concerns, and improvements in collaborative tools. A task force study on globalization and off-shoring indicated information technology (IT) has essentially become "a global field, business, and industry" (ACM, 2006). Therefore, there is a need to study how the unique aspects of virtual projects relate to their success. The Standish Group over the years has measured the incidence of software project failure in corporations with their well-known CHAOS reports. They conduct surveys with industry practitioners in the United States and Europe. The 2000 CHAOS report indicated 23% of projects failed while 49% were challenged (Standish Group International, 2001). The 2004 CHAOS report for the third quarter indicated 18% of projects failed and 53% of projects were challenged (Standish Group International, 2004). A one percent decrease in the number of troubled projects shows little improvement over a four years period. These numbers reinforce the need to investigate causes of project failure and identify the most critical project risks. This need is not just for projects in general, but particularly for the rapidly growing case of virtual projects. Critical project risks are those factors that will have the greatest impact on the success or failure of a project. Boehm indicates critical risks should be the main focus of a project manager, instead of the entire pool of identified risks (Boehm, 1991). Some risk management advocates are proponents of identifying and analyzing "threats to success", which allows appropriate actions to be taken to "reduce the chance of failure" (Wallace et al., 2004).
机译:本研究旨在区分虚拟和传统项目风险,并专门用于确定虚拟软件项目中的危急风险。由此产生的危急风险清单将为管理在虚拟团队环境中工作的项目领导者的风险提供指导。三个区域对虚拟软件项目风险的讨论很重要:虚拟软件项目团队,项目故障和项目风险。虚拟软件项目团队是一种不断增长的现象。它们被称为虚拟,因为团队成员不共同定位。 “虚拟团队是地理上,组织和/或时间分散工人通过信息和电信技术组合在一起,以完成一个或多个组织任务(Powell等,2004)”。许多驱动力导致对这些团队的依赖性增加,包括脱离支撑,外包,由于安全问题而降低了业务旅行,以及协作工具的改进。关于全球化和离岸的特遣部队研究表明信息技术(IT)基本上成为“全球领域,商业和行业”(ACM,2006)。因此,需要研究虚拟项目的独特方面如何与其成功相关。多年来的独立组织已经测量了公司在公司的众所周知的混乱报告中的软件项目失败的发病率。他们与美国和欧洲的行业从业者进行调查。 2000年的混乱报告表明,23%的项目失败,而49%受到挑战(独立集团国际,2001年)。第三季度的2004年混乱报告表明了18%的项目未成计,53%的项目受到挑战(独立集团国际,2004年)。陷入困境项目的数量下降一个百分之一点在四年内显示出很少的改善。这些数字加强了调查项目失败的原因并确定最关键的项目风险。这一需求不仅仅适用于一般的项目,但特别是对于虚拟项目的快速增长案例。关键项目风险是对项目成功或失败产生最大影响的因素。 Boehm表示关键风险应该是项目经理的主要重点,而不是整个识别的风险池(Boehm,1991)。一些风险管理倡导者是识别和分析“成功威胁”的支持者,这允许采取适当的行动“减少失败的机会”(华莱士等,2004)。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号