技巧1：参与建立变更请求过程。
Tip 1: Participate in Establishing a Change Request process.
确保资助人认可范围变更请求。
需求和变更请求决定系统的最终范围。
Requirements and change requests determine the system's final scope.
容易接受，评估，以及管理变更请求。
图2显示了变更请求记录的通用状态流程。
Figure 2 shows a general state flow for a change request record.
变更请求从问题开始。
谁分配到了由分类会议中引出的最近的变更请求？
Who has been assigned the latest change request introduced in the triage meeting?
所有的变更请求都被关闭了或者合并进入需求了吗？
Were all change requests either closed or incorporated into the requirements?
您可以使用创建对话框，来提交一些新的变更请求。
但是，某些企业只指派一两个人来定期复审变更请求。
However, some organizations designate just one or two people to review change requests periodically.
简单地说，任何变更请求在被接受之前都应该经过确认。
Simply put, any requests for change should be validated before they are accepted.
我们每周持续汇报进度，异常值将按照变更请求来处理。
Progress is being reported weekly, and that outliers will be handled as change requests.
软件配置管理：缺陷和变更请求跟踪、基线进度、活动管理。
Software configuration management: Defect and change request tracking, baseline progress, activity management.
变更请求之下的水平是分配给个人的实际活动，如图2所示。
A level below the change request is the actual activity assigned to an individual, as shown in Figure 2.
变更请求的工作流是什么，在整个工作流中会涉及到哪些用户？
What's the workflow of the change requests and what users will be involved throughout the workflow?
变更请求通常被分为以下三个类型：缺陷、增强，以及新功能。
Change requests are generally considered to fall into one of three types: defects, enhancements, and new functionality.
作为开发人员，您在成功建立变更请求过程中扮演了关键角色。
As a developer, you can play a critical role in making the change request process work for your team.
1也称作变更请求管理(CRM)，不要与客户关系管理混淆。
Also known as change request management (CRM), not to be confused with customer relationship management.
技巧2：在加强已建立的变更请求过程中学会说“No ”。
Tip 2: Enforce the Change Request Process by Just Saying no.
建立变更请求过程的第一步是确定您的团队如何收集和管理变更请求。
The first step in establishing a change request process is to determine how your team will collect and manage change requests.
两个站点还需要浏览、创建以及修正变更请求，增加需求以及缺陷报告。
Both sites will also need to view, create, and modify change requests, enhancement requests, and defect reports.
对特定发布的问题、风险、缺陷、部署请求和变更请求有更详细的见解。
Have a more granular view of issues, risks, defects, deployment requests and change requests to a given release.
将ClearQuest变更请求中的关键属性映射为Jazz工作项。
Map the key attributes in the ClearQuest change request with the Jazz work item.
ClearQuest和Jazz工具中的变更请求记录可能需要重构。
The Change Request records in ClearQuest and Jazz tools might need to be refactored.
打开状态的高优先级的变更请求：当前打开状态的高优先级的变更请求数量。
Open high-priority change requests: The number of high-priority change requests that are currently open.
您可以看到资产的所有变更请求查询，还可以为某个资产提交新的变更请求。
You can see all of the change request queries that are related to the asset or submit a new change request for a specific asset.
变更请求记录类型会应用模型与映射其他的ClearQuest记录类型。
Model and map additional ClearQuest record types referenced by the change request record type.
图1：在每个迭代的开始，敏捷团队会与客户商谈来确定新的特性或变更请求。
Figure 1: at the start of each iteration, agile teams negotiate with the customer to define new features or change requests.
工作项目包括缺陷、特性、变更请求和软件开发过程中所使用的一些类似任务。
Work items include defects, features, change requests, and similar tasks that are used as part of the software development process.
当变更请求到来时，要对变更进行考察，看其是否与现有的需求有潜在的冲突。
When change requests come in, they need to be scrutinized for potential conflicts with existing requirements.
应用推荐