No.032 <Soft Examination> "(Advanced) Examination Preparation Encyclopedia" [Chapter 16] Project Change Management

1 chapter related

1.1 Exam related

This part is generally scored 1-2 points in the morning, and case papers may be involved, which is the key chapter for review

2 Basic concepts of change management

1. Project change management refers to the changes made to the function, performance, structure, technical indicators, integration methods, project progress, etc. of the project due to the project environment or other reasons during the implementation of the information system engineering construction project . 2. The essence of change management is to meet the project needs to the greatest extent
according to the increasingly rich project cognition during the project promotion process . 3. Common reasons for changes: ① fault or negligence in product scope (results) definition; ② fault or negligence in project scope (work) definition; ③ value-added changes; Passive adjustments caused by inconsistent benchmark requirements; ⑥ external events. 4. Classification of changes : ◆ According to : change, change and change. ◆ According to can be divided into: change, change. ◆ Others: According to the field and stage of the change, it can be divided into different categories; 5. Change management is a set of management methods to deal with project changes in order to make them consistent with the project. The two possible outcomes are , or .不断调整项目努力方向和资源配置提升项目价值


变更性质重大重要一般通过不同审批权限控制
变更迫切性紧急非紧急通过不同变更处理流程进行
进度变更、成本变更、质量变更、设计变更、实施变更和工作(产品)范围变更
项目基准项目实际执行情况拒绝变化调整项目基准

3 Principles of Project Change Management

1. The principle of change management is project benchmarking and change management process standardization. include:①基准管理、②变更控制流程化、③明确组织分工、④评估变更的可能影响、⑤妥善保存变更产生的相关文档

(1) Benchmark management: Benchmark is the basis for change. During project implementation, after the baseline plan is determined and reviewed (usually users should participate in part of the review), an initial baseline is established. 此后每次变更通过评审后,都应重新确定基准.
(2) Change control process: establish or select a change management process that meets the needs of the project, and all changes must be controlled in accordance with this control process.
(3) Clear organizational division of labor: 至少应明确变更相关工作的评估、评审、执行 的职能.
(4) Assess the possible impact of changes: There are various sources of changes. It is necessary to complete change operations such as results and delivery dates that are visible to customers, as well as changes to the internal work of projects that are invisible to customers.
(5) Properly preserve the relevant documents generated by the changes to ensure that they are complete, timely, accurate and clear 适当时可以引入配置管理工具.

insert image description here

4 Change management organizational structure and engineering procedures

1. The Project Control Board or Configuration Control Board (CCB) , or similar organization with relevant functions, is the representative of the project's ownership interests 负责裁定接受哪些变更. The CCB is composed of those involved in the project 多方人员共同, usually including users and decision makers of the implementing party. CCB is 决策机构,不是作业机构; usually the work of CCB is done through evaluation means. 决定项目基准是否能变更,但不提出变更方案
2. The project manager is entrusted by the owner to be responsible for the project operation process, and its formal rights are 项目章程obtained by the authority, while the power of resource scheduling is usually specified in the benchmark. 基准中不包括的储备资源需经授权人批准后方可使用.
 The project manager's role in the change: 响应变更提出者的需求,评估变更对项目的影响及应对方案,将需求由技术要求转化为资源需求,供授权人决策;并据评审结果实施即调整基准。确保项目基准反映项目实施情况. Recite
3. Changed work procedures: 1.提出与接受变更申请2.对变更的初审3.变更方案论证4.项目管理委员会审查5.发出变更通知并组织实施6.变更实施的监控7.变更效果的评估8.判断发生变更后的项目是否已纳入正常轨道Recite

Change testing:
1. Some changes are small, and the customer is in a hurry. Can they be modified directly without going through the change procedure? 2. The project manager cannot approve the change? 3. The project manager or team members cannot raise the change? 4. The scope change can only evaluate the
scope 5. After the change is approved, the benchmark or document should be updated before it can be implemented?
6. Unapproved change requests do not need to be recorded in the change log. , team members implement as soon as possible? 8. The project manager is usually the team leader of the CCB? 9. All changes must be approved by the CCB?
10. The change control system must be a software system, which cannot be managed manually

4.1 Change response analysis

了解变更变更申请 评估影响 变更审批 更新计划及文件,通知相关方 变更执行 监控变更执行 先了解,沟通、 施加(积极)影响。 提交变更(要书面)。 评估变更 影响(范 围、成本 、进度、质 量、风险 等)。通知相 关方 项目经理 (非基准) 或CCB审 批(基准变 更) 更新变更日志 更新项目计划 更新其他项目 文件 通知相关方 执行批准 的变更 记录并监 控变更验 证变更归 档总结 了解变更变更申请 评估影响 变更审批 更新计划及文件,通知相关方 变更执行 监控变更执行

insert image description here
Change management work procedures:
1. Propose and accept change application
2. Preliminary review of change
3. Change plan demonstration
4. Project management committee review
5. Issue change notice and organize implementation
6. Change implementation monitoring
7. Change effect evaluation
8 .Judging whether the changed project has been brought into the normal track...

If the case short answer or thesis writing asks about the change control work procedure, please click here to answer directly, P509-510

4.2 Change process

insert image description here

5 Work content of project change management

1、在项目整体压力较大的情况下,更需强调变更的提出、处理应当规范化,可以使用分批处理、分优先级等方式提高效率。
2、项目规模小,与其他项目的关联度小时,变更的提出与处理过程可在操作上力求简便、高效,但关于小项目变更仍应注意以下几点:
①对变更产生的因素施加影响:防止不必要的变更,减少无谓的评估,提高必要变更的通过效率
②对变更的确认应当正式化
③变更的操作过程应当规范化
3、变更申请的提交,首先应当确保覆盖所有变更操作,这意味着如果变更申请操作可以被绕过则此处的严格便毫无意义;但应根据变更的影响和代价提高变更流程的效率。
4、变更管理,是项目整体管理的一部分,属于项目整体变更控制的范畴。涉及范围、进度、成本、质量、人力资源、合同管理等多个方面。
5、变更管理与配置管理为相关联的两套机制,变更管理由项目交付或基准配置调整时,由配置管理系统调用,变更管理最终应将对项目的调整结果反馈给配置管理系统,以确保项目执行与对项目的账目相一致

6 版本发布和回退计划

1、项目变更就必需做相应的版本发布,并制订相应的应急回退方案。为确保版本发布的成功,在版本发布前应对每次版本发布进行管理,并做好发布失败后的回退方案
2、为确保版本发布的成功,在版本发布前应对每次版本发布的风险做相应的评估,对版本发布的过程Check list做严格的评审。在评审发布内容时对存在风险的发布项做重点评估,确定相应的回退范围,制定相应的回退策略。为确保每次版本发布风险的可防可控,特准备回退方案
3、回退步骤
(1)通知相关用户系统开始回退。
(2)通知各关联系统进行版本回退。
(3)回退存储过程等数据对象。
(4)配置数据回退。
(5)应用程序、接口程序、工作流等版本回退。
(6)回退完成通知各周边关联系统。
(7)回退后进行相关测试,保证回退系统能够正常运行
(8)通知用户回退完成。

7 练习题

【例1-17下】依据变更的重要性分类,变更一般分为()、重要变更和一般变更。
A.紧急变更 B.重大变更 C.标准变更 D.特殊变更

【例2-18上】关于变更申请的描述,不正确的是()。
A.实施整体变更控制过程贯穿项目始终
B.变更请求可能包括纠正措施、预防措施和缺陷补救
C.变更请求必须由CCB来负责审查、评价、批准或否决
D.实施整体变更过程中涉及到的配置管理活动包括配置识别、配置状态记录、配置核实与审计

【例3-18下】 A公司承接了某海外信息系统集咸项目,项目进行中,项目经理获悉因天气和汇率原因,预计设备到场的运费比预算高出30%。接下来他应该首先()。
A.项目还没有结束,暂时不做处理
B.给主管领导打电话,汇报情况,寻求解决方案
C.填写项目变更申倩,启动变更流程
D.寻找新的承运商,评估变更影响,提交合同变更申请

【例4-18上】做好变更管理可以使项目的质量、进度、成本管理更加有效。关于变更工作程序的描述,不正确的是()。
①及时,正式的提出变更,且留下书面记录
②变更初审的常见方式为变更申请文档的格式校验
③变更方案论证首先是对变更请求是否可行实现进行论证
④审查过程中,客户根据变更申请及评估方案,决定是否变更项目基准
⑤发出变更通知并组织实施
⑥变更实施的工程监控,配置管理员负责基准的监控
⑦变更效果评估中的首要评估依据是项目的基准
⑧基准调整后,需要判断项目是否已纳入正轨
A.②③⑤ B.②④⑥ C.①②③④ D.⑤⑥⑦⑧

【例5-19上】项目执行期间,客户提出增加一项功能,但它并没有包括在项目预算之内。不过对于一个几百万美元的项目而言,该项工作涉及的开发工作量较小。作为项目经理应该()。
A.拒绝用户请求,原因是该项工作不在项目预算之内
B.同意并免费完成这项工作,帮助维护客户关系
C.同意增加新功能,但是需要客户承担相应的费用
D.评估新功能对项目的影响,提交变更申请

【例6-19下】某公司接了一个小型软件研发的项目,测试过程中,程序员发现某处算法需要进行更改,则()。
A.项目经理可决定是否进行变更
B.研发人员可直接进行更改
C.项目不大,变更只需口头提出即可
D.变更处理要力求简化,操作无需规范

【例7-19下】关于变更管理的描述,不正确的是()。
A.每次变更通过评审后,都应重新确定基准 B.必须采用变更管理工具
C.明确变更工作中评估、评审、执行的职责 D.评估变更的可能影响

【例8-19下】关于变更管理工作程序,正确的步骤是()。
①变更实施监控与效果评估②发出变更通知并组织实施③提出与接受变更申请④对变更的初审和方案论证⑤CCB审查
A.③①②④⑤ B.④③⑤②① C.③④⑤②① D.④⑤③②①

【例9-20下】 ()的目的是确认变更的必要性,确保变更是有价值的。
A.提出变更申请 B.变更效果评估 C.变更初审 D.变更实施

【例10-21上】变更管理是为了使得()与项目实际执行情况相一致,是应对项目套管理方法。
A.项目资源 B.项目报告 C.项目基准 D.项目目标

【例11-21上】关于变更管理工作程序描述,不正确的是()。
A.项目的干系人都可以提出变更申请
B.CCB是执行机构,负责提出变更申请
C.变更实施的过程监控,通常由项目经理负责基准监控
D.涉及项目目标及交付成果的变更,客户意见应放在核心

[Example 12-21 below] Project changes are divided into major changes, important changes and general changes according to the nature of the changes, and are realized through different ().
A. Change processing flow B. Change content C. Approval authority control D. Change reason handling

[Example 13-21 below] Change the work procedures of the management organization in chronological order, the correct one is ().
①Change effect evaluation ②Project engineer submits change application ③Project manager approves change application ④Issue change notice and organize implementation ⑤Change application document review and circulation ⑥Change plan demonstration ⑦Project management committee review ⑧Project manager and supervision unit monitor implementation A.②⑤③④⑥⑧⑦①
B .②⑤④③⑦①⑥⑧⑧ C.②③⑤⑦⑥④①⑧ D.②③⑤⑥⑦④⑧①

[Example 14-22] The essence of project change management is ().
A. Meet the requirements of Party A’s managers
B. Adjust project benchmarks or resource allocation to enhance project value
C. Effectively deal with the lack of experience of project managers
D. Understand and monitor project progress in real time

[Example 15-22 above] Regarding the description of changing work procedures, the correct one is ().
A. The change application in the project should be proposed by the project team members
B. The supervisory unit can monitor the main change results and change progress milestones
C. Changes involving project objectives and deliverables should be based on expert opinions
D. Before the change is confirmed, it should be Publicity of project implementation benchmark adjustments

reference answer

insert image description here

Guess you like

Origin blog.csdn.net/tangcoolcole/article/details/129981171