将请求的变更的全部影响记录在案。
许多时候，整体变更控制过程包括一个负责批准或否决变更请求的变更控制委员会。
Many times, the integrated change control process includes a change control board responsible for approving and rejecting the requested changes.
在这种环境中工作的组织通过令变更请求工作流可以让每个项目来配置而取得成功。
Organizations working with such environments have been successful by allowing the change request workflow to be configurable by each project.
举个例子，在图3中，单个的改进变更请求可能被识别为两个工作项，每一个都由构件团队所有并追踪。
As an example, in Figure 3., a single enhancement change request might be identified as two work items, each owned and tracked by a component team.
变更请求的工作流是什么，在整个工作流中会涉及到哪些用户？
What's the workflow of the change requests and what users will be involved throughout the workflow?
为了防止这一切，我们应该跟踪所有的用例到每一个存在的SOW需求或者变更请求。
To prevent that, we traced all use cases to either existing SOW requirements or change requests.
不管他的论据看上去多么充分，您和开发团队都必须表现出坚定的原则，并礼貌地将这些请求者引导到您已建立的变更控制过程中。
No matter what arguments people use, you and your development team have to exhibit strong discipline and politely direct these people to the proper change request process.
变更不能被容易的关联到集成与测试（I&T）的问题或者软件的变更请求上。
Changes couldn.t easily be associated with integration and test (I&T) issues or software change requests.
同样，变更请求记录的拥有权在多个团队不同的团队成员之间传递时，您可以选择Connector。
Also, choose the Connector when ownership of the change request record is passed among team members across multiple platforms.
增加、缺陷及其他由ClearQuest管理的变更请求记录存储在名为“用户数据库”的关系数据库中。
Enhancements, defects, and other change request records managed by ClearQuest are stored in a relational database called the "user database."
RETAIN RATLC Bridge 将两个追踪系统的各自变更请求之间的连接自动化。
The RETAIN RATLC Bridge automates the connection between the two tracking systems' respective change requests.
IBMRationalProjectConsole——用于跨越开发周期，对项目从需求定义直至变更请求的统计数据进行自动化的跟踪。
IBM Rational ProjectConsole — For automated tracking of project metrics across the development lifecycle, from requirements definition to change requests to defect reporting.
为了避免这一点，敏捷项目实现轻量级的或可定制的ClearQuest变更请求工作流。
To avoid this, agile projects typically implement a lightweight or customizable ClearQuest change request workflow.
此外，ClearQuest也可以帮助我们跟踪那些系统中可变的部分—在这些可变的部分中，变更请求却是极其的偏高。
In addition, ClearQuest helped us track volatile parts of the system — those parts in which change requests were disproportionately high.
当开发者到达SiteB开始他们的工作日时，他们使用本地的Windows界面登陆IBMRationalClearQuest以检查他们的对新变更请求任务的“to do”列表。
As developers arrive at Site B to begin their work day, they log into IBM Rational ClearQuest using its native Windows interface to scan their "to do" lists for new change requests assignments.
默认的ClearQuest所有者(可能是客户组)得到关于新变更请求提交的自动邮件通知。
Default ClearQuest owners (which may be groups or lists of users) get automatic email notification regarding the new change request submission.
有希望地是，这与被等待实现的需求或请求变更的数量变得越来越小形成对比。
This is contrasted with the, hopefully, ever smaller number of requirements and change requests waiting to be implemented.
有效的管理以及对开发资产缺陷、增强请求、新需求的响应和其他进行变更的追踪能力在GDD项目中都是极为关键的。
The ability to efficiently manage and track ongoing change to development assets in response to defects, enhancement requests, new requirements, and so forth is especially critical on GDD projects.
与变更请求联合的工作流程应该加强这个过程，通过这个工程您地组织就可以跟踪并管理变更。
The workflow associated with a change request should enforce the process by which your organization intends to track and manage change.
图1：在每个迭代的开始，敏捷团队会与客户商谈来确定新的特性或变更请求。
Figure 1: at the start of each iteration, agile teams negotiate with the customer to define new features or change requests.
为传统的变更管理方法配置互操作性，需要变更请求在不同的储存库及其关键属性和请求状态之间得到同步化。
Configuring interoperability for a traditional change management approach requires the change request to be synchronized across the repositories, along with its key properties and request state.
由于新的变更请求有高的优先级，并且将对他正在进行中的其它工作产生影响，开发者决定立即对其进行工作。
Since the new change request has a high priority and will affect other work he is doing, the developer decides to work on it immediately.
例如，如果您知道某个来自市场部门的软件变更请求会使销售部门使用的某部分软件过时，您需要以简单的术语解释这种情况。
For example, if you know that a software change request from marketing will make a piece of software used in sales obsolete, then you need to explain that in those simple terms.
更加无缝的变更请求过程几乎会为控制范围的增长、产生更好的系统和更高的和约价值带来的更多的机会。
A more seamless change request process would most likely have introduced more opportunities for controlled scope growth, resulting in a better overall system and a higher contract value.
我们不断的提高工作的重点是更快地响应客户对产品中变更的请求，不论该请求是一个问题，还是增强的请求。
The focus of our continuous improvement efforts is to respond faster to customer requests for change in the product, whether the request is a problem or a request for enhancement.
建立变更请求过程的第一步是确定您的团队如何收集和管理变更请求。
The first step in establishing a change request process is to determine how your team will collect and manage change requests.
ADM需求管理处理所有类型的需求，包括显著的业务推动者、关系，及新的功能和变更请求。
ADM requirements management deals with all kinds of requirements, including most notably business drivers, concerns, and new functionality and change requests.
对特定发布的问题、风险、缺陷、部署请求和变更请求有更详细的见解。
Have a more granular view of issues, risks, defects, deployment requests and change requests to a given release.
它组成了一种末端到末端的工作流程，以确保变更请求的控制通过了定义的生命周期。
It institutes an end-to-end workflow that ensures the control of change requests through the defined lifecycle.
重要的需求以及变更请求列表经常会在产品堆积中被找到，4——这代表了等待被完成的堆积的工作。
This list of outstanding requirements and change requests is often referred to as the product backlog, 4 as it represents the backlog of work waiting to be done.
应用推荐