项目团队需求理解项目取人们之间是如何互相影响的。
The team needs to understand how the project affects people and how people affect the project.
在大多数的场景中，自动化开发团队都会设计只满足一个测试团队需求的工具。
In the majority of scenarios, automation development teams design the tool which satisfies the requirements of only one test team.
IBMRationalBuildForge提供了满足大型开发团队需求的自动的构建管理和软件交付过程。
IBM Rational build Forge provides an automated build management and software delivery process that scales to meet the needs of large development teams.
在不需要医疗团队参与的情况下，这些使我们的健康需求可以进行不同类型的交互。
These allow for different kinds of interactions about our health needs without involving the medical team.
这些政策引发经常需要团队合作的资金需求。
These policies underlie funding requirements that often require teamwork.
他们的工程师团队留下来了，使他们成为“人才并购”中的两名成员。大公司就是用人才并购手段来满足对技术人才的巨大需求的。
Their teams of engineers stayed on, making them two of the many "acqui-hires" that the biggest companies have used to feed their great hunger for tech talent.
然后该团队将分析那些需求。
在微小迭代结束时，团队应当回顾需求是如何被组织和文档化的，并识别要改进的区域。
At the end of the mini iteration, the team should review how requirements were organized and documented, and identify areas for improvement.
一旦需求团队收到了这些改进建议，他们就会立刻将改进应用到下一次迭代。
Once requirements teams receive these improvement Suggestions, they can immediately apply improvements to the next iteration.
IBM拥有一系列的您可以直接使用的测试自动化产品，或者您可以使用它来满足大多数测试自动化团队的需求。
IBM has a line of test automation products that you can use directly, or extend to satisfy the requirements of most test automation teams.
通过预先计划，我们可以真正地开始了解需求团队的能力了。
By planning this up front, we can really start to understand our requirements team's capability.
在计划阶段，SR候选列表会确定，而且开发团队会对这些需求确立初步的规模估计。
In plan phase, the SR candidate list is firmed up, and the development team builds low-level sizings for these requirements.
不要不切实际的期望IT项目交付团队在需求范围不断变更的情况下还能够遵守进度和预算。
It is unreasonable to expect the it project delivery team to commit to schedule and budget if the requirements scope is continually changing underneath them.
当需求团队在处理基线bl1 时，他们给它贴上了 RQ_BL1 的标签。
When the requirements team is done with the baseline bl1, they label it RQ_BL1.
用户描述描述了团队要实现产品需求而必须完成的工作。
User stories represent the work the team must accomplish to meet the requirements of the product.
一个程序会转化为拥有少量开发构件的支持团队，例如需求，设计和测试。
An application is transitioned to a support team with few of the development artifacts, such as requirements, designs and tests.
迭代开发方法典型地将架构师作为项目的开发点，辅助开发团队完成需求阶段，并进行早期的少量编码。
Iterative development methods typically place architects at the beginning of a project, partnering with development teams through requirements and early bits of coding.
该产品的若干可用工具和定制选项使其能够满足任何团队的需求。
The multiple tools and customization options available with the product allow it to meet any team's needs.
这样的团队鼓励在需求、技术以及项目生命周期内项目其他方面的改变。
Such teams welcome change in requirements, technology, and any other aspect of a project at any point in the project's life cycle.
开发环境升级的时间取决于开发团队的需求。
When the development environment gets upgraded depends on the development team's requirements.
团队根本没有理解需求，很多细节没有深入讨论。
Requirements were not well understood, more precisely were not discussed in depth.
您必须裁减过程，使之满足团队的确切需求。
如果需求定义得到了涉众的确认，那么项目团队就会交付需求基线，并在项目生命周期阶段管理它。
When the requirement definition gets confirmation from stakeholders, the project team delivers the requirement baseline and then manages it during the project life cycle.
谁创建项目需求，团队中的哪个人需要使用这些需求？
Who creates project requirements, and who on the team needs to have access to these requirements?
soa治理流程应当确保qa团队的需求得到满足。
SOA Governance process should ensure that needs of the QA team are met.
真正的好方法就是利用这点在各各任务、团队、队员的需求之间实现平衡。
The real skill, though, is being able to use this knowledge to balance the needs of the task, the team, and the team members.
需求团队可以查看什么需求被转化为运行，测试代码(参见图7)。
Requirements teams can see which of their requirements have been turned into running, tested code (see Figure 7).
原始需求与分支需求之间的追溯关系，可以帮助您对其他团队对需求所做的变更能保持一致。
A trace relationship between the original requirement and the branch requirement can help you stay in touch with changes that are made to requirements by other teams.
在一些我所观察的使用OI方法的团队中，需求人员开始接受变更请求或进行会面以澄清第一次迭代需求中的问题。
With a few teams I've observed that used an OI approach, the requirements people began to receive change requests or meeting invitations to help clarify problems with the first iteration requirements.
需求不再是“被”交接给团队，相反，团队成员是需求的共同作者。
Requirements are no longer handed off to the team; the team members coauthor them.
应用推荐