Effective software project teams are composed of people fulfilling a variety of roles.
有效的软件项目团队由担当各种角色的人员所组成。
Project teams stored all of their software artifacts in one repository and used proprietary vendor tools to work on them.
项目小组把所有关于他们软件产物储存于一个资源库中，并使用专门的工具处理他们。
Selecting the best technique or combination of estimation methods to apply to a project has become a large problem for software teams.
对于软件团队来说，一个很大的问题是在项目中选择哪些最佳的技术或者评估方法的组合。
If you are doing offshore software development, even having able, English-speaking teams on both sides of the globe does not guarantee that your project will run smoothly.
如果您正在做海外的软件开发，那么甚至在地球两侧您有能干的，说英语的团队，也不能保证项目会顺利进行。
BPI project teams working on tight schedules may feel they need to resort to a manual workaround in order to avoid a complex software design point.
BPI项目团队在紧张的工作安排中可能会感到他们需要求助于手动工作区来避免复杂的软件设计问题。
Rather than prescribing a plan-build-assemble sequence of activities for a software project, they describe an iterative, incremental process that steers development teams toward results.
它们描述了一个迭代的，递增的，引导开发团队实现结果的过程，而不是为一个软件项目指示一个计划-建立-组装的活动序列。
Another potential issue is that software development teams do not have the time to assemble advanced project portals where they can consolidate and visualize that kind of information.
另一个潜在的问题是软件开发团队并没有时间，去收集可以加强和查看这些信息的高级项目部分。
Traceability of requirements through the software development lifecycle is one of the major issues faced by most development project teams.
在整个软件开发生命周期中实现需求的追踪性，是大多数开发项目团队所面临的主要问题之一。
Test teams write and execute hundreds or even thousands of test script documents for a given software project.
测试团队为已知的软件项目书写并执行成百甚至上千的测试脚本文档。
Enable teams across an organization to collaborate more effectively, reduce software project failures, and save time and money with proven, flexible process guidance.
用已证实的灵活的过程指导，使跨组织的团队更有效的协作，减少软件项目的失败，并节省实践和金钱。
Next month we'll continue to consider the analogies between art and software development by looking at how highly talented software "artists" fit in on software development project teams.
下月，我们将通过研究杰出的软件“艺术”如何适合于软件开发项目团队，继续考虑艺术和软件开发之间的相似之处。
When software development teams move to agile methods, experienced project managers often struggle — doubtful about the new approach and uncertain about their new roles and responsibilities.
当软件开发小组转向敏捷方法时，有经验的项目管理人员通常与他们斗争——怀疑新的方法以及不确定他们新的角色和职责。
Reuse engineers become a channel and a conduit for project teams to bring forward opportunities for creation of reusable software assets in the form of services.
重用工程师成为了一个通道，项目团队可以通过他/她获得以服务的形式创建可重用软件资产的机会。
That's what the XP practices represent — a different way to run projects that gives your teams a better chance of delivering software real people end up wanting when the project is over.
这就是XP实践的含义—一种不同的项目运作方法，使您的团队在项目结束时更有可能交付出人们真正想要的软件。
In the latter environment, the software test team has to start from scratch to define its role and establish those social contracts with other project teams.
在后一种情况下，软件测试团队必须从起草它的角色并与其他项目团队建立社会契约开始。
Finally, as the software architect works closely with the project manager, the structure of the architecture is used to assign work to teams.
最后，当软件架构师与项目管理人员紧密地协同工作时，将根据体系结构的结构为不同的团队分配相应的工作。
This approach to continuously ensuring quality builds success into the project rather than making teams gamble with the unpredictability inherent in software development efforts.
不断使项目逼近质量保障达到成功，而不是使团队迷失在不可预期的软件开发事物中。
The IBM Software development Platform unifies project teams by providing common access to development assets, communication alerts, and workflow processes.
IBM软件开发平台通过提供公用的开发资产权限，通讯报警，和工作流过程使项目团队成为一体。
With UML, software professionals can visually model their analysis and design artifacts in a uniform and consistent manner, so teams have a common approach for communication and project documentation.
利用UML，软件专业人员可以以一种统一一致的方式对他们的分析和设计部件进行可视化建模，这样团队就有了一种处理沟通和项目文档的公共方法。
Organized into a series of four project phases — Inception, Elaboration, Construction, and Transition — RUP 2 guides project teams through an iterative approach to software development.
RUP2包括一系列共四个项目阶段：初始阶段，细化阶段，构建阶段，和产品化阶段。它指导项目团队通过迭代方法完成软件开发。
My experience is that a clear, concise architectural description, developed incrementally as the project progresses, provides a useful context for software development teams, agile or otherwise.
我的经验很清楚，不管是敏捷还是其他，简明的架构描述，并随着项目的进度进行增量开发能给开发团队提供一个有用的背景环境。
Wikis have been around for a while, often used by software development teams as a crude project management and communications tool.
Wikis已经存在有一段时间，软件开发团队通常将其作为一种粗糙的项目管理和交流工具。
The following key ideas will allow teams to manage requirements for their software project.
下面这些观念将帮助团队管理他们软件项目的需求。
Rational team Concert allows project teams to define, automate, and govern software delivery projects.
RationalTeam Concert允许项目团队去定义、自动化和管理软件交付项目。
Software Configuration Management (SCM) can help even the largest, most complex project teams manage change, so they can deliver higher-quality products faster.
Illustration软件配置管理(Soft ware Configuration Management,SCM)有助于大型、复杂的项目团队管理变更，这样，他们就可以更快地交付更高质量的产品。
In the fast pace of agile software development, increasing Numbers of teams are adopting Rational team Concert as their project management tool.
在敏捷软件开发的快节奏中，越来越多的团队开始采用RationalTeamConcert来作为他们的项目管理工具。
In the fast pace of agile software development, increasing Numbers of teams are adopting Rational team Concert as their project management tool.
在敏捷软件开发的快节奏中，越来越多的团队开始采用RationalTeamConcert来作为他们的项目管理工具。
应用推荐