Critical success factors for GDD.
GDD的关键的成功因素。
Figure 2: Benefits and challenges of GDD.
图2：gdd的好处和挑战。
The reality of geographically distributed development (GDD)
区域分布式开发（GDD）的现实性
In many GDD scenarios, both local and remote development resources are involved.
在许多GDD场景中，同时关联着本地以及远程开发资源。
As companies move to GDD, they face certain inherent risks that must be attacked head-on.
随着公司采用了GDD，风险会迎面而至。
GDD has become the standard way of doing business for most companies that depend on software.
GDD已经成为大多数依赖于软件的公司经营的标准方式。
Without robust, secure asset management capability, most GDD projects would be too risky to undertake.
没有健壮的、安全的资产管理能力，大部分GDD项目都会承担很大的风险。
And the process will be robust enough to support effective GDD (geographically distributed development).
这个流程将会足够健壮以支持有效的GDD(地域分布式开发)。
Part I also touched on key strategic considerations like what projects are best-suited to a GDD approach.
第一部分同时还论述了核心战略的考虑，例如什么样的项目最适合于一个GDD解决方案。
Indeed, poorly defined or inadequately communicated requirements are among the most common reasons why GDD projects fail.
确实，不良的定义和不充分的需求沟通是导致GDD项目失败的最常见原因之一。
In a GDD model, the development staffing may be distributed across town, across a state or provincial border, or overseas.
在GDD模型中，开发人员配置分布可能是跨城镇的、跨州或省边界的，或是在海外的。
Project management requires a way to effectively plan, track, and manage all aspects of GDD project and resource portfolios.
项目管理需要一种有效的方法进行计划、追踪并对GDD项目所有方面及资源组合进行管理。
As we've discussed above, companies now adopt GDD with the intent of capitalizing on the many potential benefits, including.
如我们前面所讨论的，公司现在采取GDD，想要利用许多潜在的好处，包括。
This series of articles is based on their recent work targeting GDD approaches and Rational support for distributed development.
本系列文章基于他们最近的针对GDD方法和Rational对分布的开发的支持的工作。
Other GDD approaches that our customers frequently employ include componentized team development and tightly coupled co-development.
我们其它的客户经常使用的GDD解决方案包括模块化团队开发以及紧密连接的联合开发。
Additional factors like network topologies and security policies can further complicate the configuration and deployment of GDD tools.
另外，例如网络拓扑以及安全策略会进一步使得配置及开发gdd工具变得更复杂。
Business needs and infrastructure capabilities will combine to help shape the optimal tools deployment for a specific GDD environment.
业务需求及基础结构性能将联合起来帮助对一个特定的GDD环境进行最优化的工具配置。
The GDD deployment scenario described here illustrates just one of many ways that IBM Rational tools can support a distributed team today.
在这里所描述的GDD配置场景举例说明了今天IBMRational工具对分布式团队支持方法中的一种。
The GDD scenario we've worked through in this article is one of the more common models that organizations are using or contemplating today.
本文中所讨论的GDD场景是各个组织今天正在使用或考虑使用的更加常规的模型。
This need to keep requirements, design, and implementation in sync has always been a challenge, and is only exasperated in the context of GDD.
保持需求、设计和实现同步的这一需要已经成为一个挑战，并且只在GDD的环境系中触及。
Now, in Part II, I present an example scenario that illustrates some of the many possibilities for applying IBM Rational tools to support GDD.
现在，在第二部分，我用一个示例场景举例展示了关于应用IBMRational工具以支持GDD的一些可能性。
By some estimates, productivity in a GDD project can drop up to 50 percent, with rework two to five times greater than for a collocated project.
据估计，返工二到五次，GDD项目的生产力会下降到50%以上，比集中的项目多。
Performance is important when working in a GDD environment, and many factors affect it. To maximize your performance, keep these points in mind.
当在GDD环境中工作时，性能是重要的，并且许多因素会影响性能。
Network performance and server infrastructure is also a big factor in deciding how best to organize a GDD project. GDD project managers need to consider.
网络性能以及服务器基础结构也在很大程度上决定了是否能够良好的对一个GDD项目进行组织。
These strongly partitioned roles allow Alcrohm to gain experience with GDD in general, and its off-site partner in particular, with comparatively low risk.
这些强有力的任务划分允许Alcrohm以相对低的风险得到GDD的常规经验，特别是其非现场的合作伙伴。
Many times GDD happens through mergers and acquisitions: Companies don't instantly relocate and co-locate people or shut down one operation and/or merge them.
很多次GDD通过合并和收购发生：公司不是马上重新部署和共同部署员工或者关闭一项业务并且/或者将他们合并。
These are special forms of GDD where development is distributed not across the sponsoring organization but to outside parties often located far distances away.
这些是GDD的特殊形式，开发分布不是跨越主持研究计划的组织，而是分布到通常距离较远的外部人员。
In addition to having your finger on the pulse of project status it is equally important to determine if expected returns were recognized during a GDD project.
除了关心项目的状态，确定GDD项目过程中预期收益是否实现也是同样重要的。
IllustrationThis is the first in a series of articles exploring various aspects of global development and delivery (GDD) as it pertains to software development.
插图本文是探究当全球化开发和交付(globaldevelopment and delivery,GDD)应用于软件开发时，它的各种方面的系列文章中的第一篇。
IllustrationThis is the first in a series of articles exploring various aspects of global development and delivery (GDD) as it pertains to software development.
插图本文是探究当全球化开发和交付(globaldevelopment and delivery,GDD)应用于软件开发时，它的各种方面的系列文章中的第一篇。
应用推荐