范围管理

项目变更控制过程（二）：

2007-05-24 12:00:22　源自:　网友评论　共有( )条评论!有致内容报错

本文章地址:http://Train.xuezhishi.net/controlevent/scope/2007-05-24/14434.html [将本信息与朋友分享!]

>  Procedure（程序）
  Entry Criteria（开始条件）
  Change control board is established for the project.
  Baselined work products exist.
  The Originator has submitted a valid issue or change request with all necessary information to the CCB Chair.
  The change control tool sets the issue’s initial status to Submitted.
  已建立项目变更控制委员会。
  存在已基线化的工件。
  发起人提交正确的变更请求或将变更请求和所有必要的信息提交给变更控制委员会主席。
  变更控制工具将变更请求的初始状态设置为已提交。
  Tasks（任务）
  1. The CCB Chair assigns an Evaluator.
  1. 变更控制委员会主席指定一个评估人。
  2. The Evaluator assesses the issue as to feasibility, whether it really pertains to the indicated project, whether a reported problem can be reproduced, an estimate of the labor hours needed to implement the change, and so on. For a requirement change, use the Impact Analysis Checklist for Requirements Changes, the Effort Estimation Worksheet for a Requirement Change, and the Impact Analysis Report Template. Change status to Evaluated.
  2. 评估人对变更请求进行可行性评估，判断其是否真正符合项目特征，被报告的问题是否能被重复产生，估计实施变更所需工作量等等。对一个需求变更，用影响分析检查表，工作量估计表，以及影响分析报告模板进行评估。改变状态为已评估。
  3. The CCB decides whether the requested change should be made (or the reported problem fixed) at this time, at some point in the future, or not at all. Input should be solicited from others potentially affected by the change before making the decision.
  3. 变更控制委员会决定此次提出的变更是否应实施（或已报告的问题是否应解决），或部分变更在将来解决，或根本不解决。决定前必须从其他被变更影响的潜在方获取必要的意见。
  4. If the change was accepted, the CCB Chair assigns a Modifier, sets the status to Approved, enters any explanation in the Response attribute, and schedules the work. The Project Manager negotiates any necessary changes in project commitments with affected stakeholders. Tool sends e-mail to the assigned Modifier and the Originator.
  4. 如果接受变更请求，变更控制委员会主席会指定一个修改人，同时设置变更请求状态为已批准，并在回应属性中填入相应解释。项目经理在项目会议中同涉众协商任何必需的变更。变更控制工具发电子邮件给已指定的修改人和发起人。
  5. If the change was rejected, the CCB Chair sets the status to Rejected and enters an explanation of why in the Response attribute. Tool sends e-mail to the Originator and CCB Chair.
  5. 如果变更被拒绝，变更控制委员会主席设置变更状态为已拒绝并在回应属性中解释拒绝的原因。变更控制工具发电子邮件给发起人和变更控制委员会主席。
  6. The CCB Chair and the Originator determine whether formal verification of the change will be required, following the procedure in the Verification section. If so, they select the verification method to be used and the CCB Chair assigns a Verifier.
  6. 变更控制委员会主席和发起人决定是否需要对变更进行正式的验证，具体的步骤在下面的验证部分中描述。如果是，他们选择使用的验证方法并由变更控制委员会主席指定验证人。
  7. The Modifier makes the necessary changes in the affected work products and notifies any other affected parties if corresponding changes need to be made, such as user documentation, help screens, and tests.
  7. 修改人在受影响的工件中实施必要的变更，如果在其他方也需要实施相应变更则应通知所有其他受影响方，如用户文档、帮助屏幕、测试文档等。
  8. The Project Manager updates the project plans, task lists, and schedules to reflect the impact of the change on project work remaining to be done. The Project Manager revises any task dependencies as necessary.
  8. 项目经理更新项目计划，任务清单，和时间表，以反映变更对已做或在做工作的影响。如果需要，项目经理修订任务的依赖性。
  9. If it becomes apparent during the work that the requested change is not feasible after all, the Modifier notifies the CCB Chair, who may then set the status to Canceled. The Modifier backs out of any modifications made, restoring the work products to their previous baseline. Tool sends e-mail to the Originator, CCB Chair, Modifier, and Project Manager.
  9. 最后如果在工作期间发现需求变更是不可行的，修改人应通知变更控制委员会主席，由他作出取消决定并设置状态为已取消。修改人返回未做修改状态，恢复以前已基线化的工件。变更控制工具发电子邮件给发起人，变更控制委员会主席，修改人和项目经理。
  10. When the change is completed, the Modifier sets the status to Change Made, updates the issue in the database with appropriate notes in the Response attribute, and enters the hours of effort that were required to make the change in the Actual Hours attribute. Tool sends e-mail to the Originator and CCB Chair.
  10. 当变更完成时，修改人设置变更状态为实施变更，在回应属性中对更新的变更请求加入适当的注释，并在实际时间属性中输入实施变更所花的实际工作量。变更控制工具发电子邮件给发起人和变更控制委员会主席。
  Verification（验证）
  1. The Modifier notifies the Originator and Verifier (if one was assigned) that the change has been made and makes all modified work products available to the people responsible for verification.
  1. 修改人通知发起人和验证人（如果已经有指定的验证人）变更已经被实施，并且所有已修改的工件已经可以进行验证。
  2. The Verifier performs the agreed-upon verification steps.
  2. 验证人执行验证过程。
  3. If verification is successful, the Verifier sets the status to Verified.   Tool sends e-mail to the Originator and Modifier.
  3. 如果验证通过，验证人设置变更状态为已验证。变更控制工具发电子邮件给修改人和发起人。
  4. If verification is not successful, the Verifier sets the status back to Approved and describes the problem in the Response attribute. Tool sends e-mail to the Originator and Modifier. The process resumes with Task #7.
  4. 如果验证未通过，验证人设置变更状态为已批准并在回应属性中描述具体的问题。变更控制工具发电子邮件给修改人和发起人。此过程会从任务#7重新开始进行。
  5. For a problem report issue or an enhancement request issue, the Modifier installs the modified work product as appropriate and updates the product baseline. For requirements changes, the Modifier updates version numbers on all modified work products per the project’s version control procedure, checks them back into the version control system, updates requirements traceability information and requirements status attributes as necessary, and updates the requirements baseline.
  5. 对于一个问题报告或增加需求的发布，修改人安装已修改后的工件并更新产品基线。对于需求变更，修改人按照每个项目的版本控制程序更新所有已修改工件的版本号，如果需要应更新需求追溯信息和需求状态属性，并更新需求基线。
  6. The Modifier sets the status to Closed. Tool sends e-mail to the Originator and CCB Chair.
  6. 修改人设置变更状态为已结束。变更控制工具发电子邮件给发起人和变更控制主席。
  Change Control Status Reporting（变更控制状态报告） The CCB Chair generates a report at the end of each month summarizing the status of the contents of the change control database. These reports identify all status changes made in the previous month, list the status of all change requests that currently have a status other than Rejected or Closed, and indicate the level of change activity. The project leadership team reviews these reports to determine whether any corrective actions are necessary.
  变更控制委员会主席根据变更控制数据库的内容在月末汇总出变更控制数据的报告。这些报告表现出上一个月所有发生的变更的状态，列出当前所有需求变更的状态但已拒绝和已完成的除外，并指出变更活跃程度。项目管理组查看这些报告以确定每个活动的正确性。
  Exit Criteria（退出条件）
  o The status of the request is either Rejected or Closed.
  o The modified work products have been correctly installed into the appropriate locations.
  o The Originator, CCB Chair, and Project Manager have been notified of the current status.
  o Pertinent requirements traceability information has been updated.
  o 变更请求的状态为已拒绝或已结束。
  o 所有修改后的工件被正确安装到适当的位置。
  o 发起人、变更控制主席、和项目经理已被告知当前的状态。
  o 相关的需求追溯信息已被更新。
  Appendix（附件）: Attributes Stored for Each Issue（每个变更请求应保存的属性）

Field (字段) http://Train.xuezhishi.net/controlevent/scope/2007-05-24/14434.html

[评论][发送朋友][长点见识][放入收藏夹]

复制本文链接(URL)发送给朋友：

上一篇：如何在需求不断变化的项目中取得成功： ·下一篇：项目变更控制过程（一）：