图1：在每个迭代的开始，敏捷团队会与客户商谈来确定新的特性或变更请求。
Figure 1: at the start of each iteration, agile teams negotiate with the customer to define new features or change requests.
它还提供了追踪特性，可以帮助测试团队确定测试计划涉及了所有的需求。
It also provides traceability features that can help test teams ensure that test plans are covering all requirements.
包含这些特性的核心环境组件是团队空间。
The core component of the environment that includes these features is team places.
如果您的交付率已经非常缓慢了，那么您不可以期望团队交付大的特性。
If your delivery rate is already very slow, you can't expect the team to deliver the big features.
在这个会议上，产品所有者会阐述即将到来的冲刺最需要的特性，描述它们，这样团队才会明白接下来他们要做什么。
At this meeting, the product owner presents the features most desired for the upcoming sprint, describing them so that the team can grasp what is expected.
它们还提供一些帮助团队更有效地协作的附加特性。
They also provide some additional features that help a team collaborate more effectively.
这些应用程序可以集成团队空间的内容库特性。
These applications integrate with the content library feature of team places.
特性团队应该有权对平台组件进行回归测试，这样他们就可以在提交更改前在本地针就不同的配置环境生成产品。
Feature teams should have access to the regression tests of the platform components so that they can build locally against different configurations before they commit their changes.
通过使用这个新特性，可以增强团队对部署的控制能力，更好地控制云资源的使用和虚拟机命名。
You can use this new feature to give teams more control over their deployments in terms of cloud resource usage and virtual machine naming.
通过权衡使用帮助你快速打开模型的特性，你的团队就能更好地有效率合作了。
By leveraging features that help you quickly open models, your team is better able to work more productively.
这两个特性帮助测试团队开发和文档化可重复的测试结果，从而满足“高可见性”的挑战。
These two features helped the test team develop and document repeatable test results, meeting the high-visibility challenge.
团队总是为产品中新的或修改了的特性撰写新的测试。
And the team was always writing new tests for new or modified features in their product.
团队可以通过使用工作项评论特性来进行协作，然后完成或者如有需要则重新分配工作。
The team can collaborate on the blockers by using the work item commenting feature, and then finish or reassign the work as needed.
我想部署特性将会被那些频繁更新程序的团队广泛接受。
I think the Deployments features will be really appreciated by teams that are updating their applications frequently.
开发团队在同样的进度中继续处理次要的特性。
The development team continues to work on the secondary features within the same schedule.
在本文中，我们会集中讨论五个主要问题，即：特性团队、团队自主管理、业务价值、代码所有权以及稳定性。
In this article, we focus on five main issues, namely: feature teams, team autonomy, business value, code ownership, and stability.
特性团队对平台组件所作的任何修改和扩展，都必须经过主管该部分的平台团队的审核。
All changes by feature teams need to be audited by the platform team owning the part that needs to be changed or extended.
这个特性使得团队能够追踪器进程。
为了交付应用级特性，特性团队通常承担着端到端的职责。
Feature teams usually assume end-to-end responsibilities to deliver application level features.
有些时候，特性团队所要求的改动，可能与使用平台的其他产品产生无法解决的冲突。
Certain change requests coming from the feature teams can sometimes create irresolvable conflicts with other products that use the platform.
在给定系统中，特性团队通常承担端到端职责，围绕特性(也就是所谓的故事)展开工作。
Feature teams usually assume end-to-end responsibilities in a given system by orienting their work around features (aka. stories).
该特性让您能够创建基于兴趣或团队的广播社区。
This feature will help you create interest - or team-based broadcast communities.
特性团队所作的决定要经过该名成员确认方能生效。
This member will validate the decisions made by the feature team before they actually take place.
应该允许特性团队填补平台的欠缺之处，视需要还允许新添一些组件。
Feature teams should be able to fill in the missing parts in the platform and possibly add new parts when needed.
有时候需要另外一些与应用层有密切互动的组件团队来与特性团队更紧密地合作，以理解他们的需求。
Other component teams that have a closer interaction with the application layer may need to collaborate more closely with feature teams in order to understand their requirements.
与能够和客户进行第一手交流的特性团队相比，可能会错误的认为专注开发并且持续完善核心服务的团队贡献的价值较小。
Teams who work on developing and continuously improving core services may be wrongly perceived as delivering less value than feature teams that have a firsthand interaction with their customers.
那么我们如何在分布式团队中开促进这种特性的开发呢？
How can we promote these characteristics in distributed teams?
敏捷的开发周期的迭代特性令系统测试团队以较小的且更容易消费的规模在较长的时间内理解产品。
The iterative nature of the agile development cycle allowed the system test team to understand the product over a longer timeframe in smaller, more readily consumable pieces.
开普勒团队的器械不能测量大气或是地质特性。
The Kepler instruments cannot measure atmospheric or geological properties.
正如艾萨克提到的，CentralDesktop聚焦于团队层次，它的特性包括协同文件编辑、网络音频会议，想法的讨论及文件版本跟踪。
Central Desktop has what Isaac referred to as a "team level focus" and its features include collaborative document editing, Web and audio conferencing, discussion threads and versioned file tracking.
应用推荐