Chapter 4 - HW_AngelicaGarcia

.pdf

School

Marshall University *

*We aren’t endorsed by this school

Course

660

Subject

Industrial Engineering

Date

Oct 30, 2023

Type

pdf

Pages

Uploaded by ChefTree12545

Performing Integrated Change Control As a project manager in a predictive project life cycle, it should come as no surprise that changes often enter the project scope. When a change happens it can have a ripple effect on the remainder of the project. What seems like a tiny addition to the project scope can result in changes to the project costs, the project schedule, risks, procurement, and other areas of the project. Integrated change control is a monitoring and controlling process to ensure that all project changes are thoroughly reviewed for their full effect on the project. This includes the preferred documented, proposed, and then implemented change request and those change requests that bypass the change control system. Consider a project team member that adds things to the project scope as she’s working on the project activities. These unapproved changes need to be considered and managed just as proposed, documented change requests are managed. Scope creep, also known as project poison, are the tiny, undocumented changes that sneak into a project. Rely on communication and ground rules with the project team and the project stakeholders to attempt to prevent this problem. Scope creep happens, often, when stakeholders approach project team members and ask for tiny favors and additions to the project instead of following the prescribed change control processes. The reason scope creep is also known as project poison is that time and monies are given to the tiny scope additions and this robs the project’s budget and schedule from the time and budget for the project scope. EM 660 - Homework #4

Often a Change Control Board, rather than the project manager, makes the decision and provides direction on the proposed changes. All changes are then passed through the key project management process for this section: integrated change control. Integrated change control reviews the entire project to determine and document a change’s effect on each of these project knowledge areas:  Scope How does the proposed change affect the already approved project scope?  Schedule What will this change do to the project schedule?  Cost How much will the proposed change cost the project?  Quality What new requirements are there for the features and functions and expected quality?  Resources Will the change require new skills, training, additional labor, materials, equipment?  Communications What stakeholder need to be informed of this change request?  Risk How can this proposed change threaten or improve the project objectives?  Procurement What new purchases will be needed as a result of this proposed change? If the change stems from the scope, there’s an extra component that must be reviewed: the configuration management system. Configuration management is the documentation and control of the features and functions of the product the project is creating. The configuration management system provides the documentation, labeling, and baseline of the project’s product. It provides three things:  Configuration identification applies to the components of the product the project is creating.  Configuration status accounting documents and tracks changes, both approved and proposed, to the product and when the changes are implemented.  Configuration verification and audit provides an assurance that the approved product configuration have been met and implemented as planned.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version