Question

During these project objectives, you will work with project scope and handling changes to prevent catastrophic failure to the project. The project scope is usually defines as the use-case documentation is created and approved. The project manager should finally get signatures from the other managers when everyone agrees on the final draft of the project. The final draft is the scope and it will typically not change unless there is a change request. At the bottom of the project use-case documentation, add a signature page for all required manager signatures. Make sure the signature page looks and feels professional which should include the date of when a manager signed the use-case documentation for approval. You have more objectives in the course to build and integrate into your documentation but this should always be the last page of the document. Next document a typical scenario that might actually be a good reason to change the scope of a project. For instance, the documentation might not include form validation controls. As the users are testing, the validation is always necessary to keep the data clean in the database. Create your own scenario that could change the scope of the project and would cause the managers to agree and accept the change request. Document the change request procedure. This professional procedure would be used in a business when a tester found an issue that requires a project change and the requestor would need to follow through each step before the change would even be considered. Document the procedure in a chronological order as if each step was a checklist.

Answer 1

Change Management Process for External Facia Change for Front Loading Washing Machine

1) Purpose:

The purpose of this document is to provide the project manager, sponsors and all other stakeholders with a standard process for managing changes on "Facia Change for Front Loading Washing Machine". This is also to manage change requests so that approved changes will be controlled, ensuring the project remains on schedule, within budget and provides the agreed deliverables.

2) Objectives:

The primary objectives of change management are to:

• manage each change request from initiation through to closure;
• process change requests based upon direction from the appropriate authority;
• communicate the impact of changes to appropriate personnel; and
• allow small changes to be managed with a minimum of overhead.

In this case the design change of the facia to uplift the looks of the washineg machine.

3) Scope:

The scope is to have the face change of the Front Loading Washing Machine without changing the basic platform.

4) Change Management Documents:

4.1 Change Request Form

The ‘Change Request Form’ is used to identify and describe a proposed change to the project.

Change of the Facia for the following models (vix. WM1....WN10) with part nos. (X1,.... Xn)

4.2 CID (Change Issue, Decision) Log

This is used for tracking no. of version changes of the facia or any other parts for the washing machine model or variants.

5) Change Management Roles:

5.1 Project Manager/Lead

A team member initially recognizes a need for change to the project and formally communicates this requirement to the Project Manager and/or Lead. The Project Manager and/or Lead are then responsible for:

• Identifying the requirement to make a change to the project- e.g. BOM change, System change, Stock back flashing, etc.
• Documenting the requirement by completing a Change request form (CRF)
• Submitting the CRF to "Facia change for Front Loading Washing Machine" Leadership for review.

5.2 Project Managers

The Project Manager receives, logs, monitors and controls the progress of all changes within the project. The Project Managers are responsible for:

• Documenting and or receiving all CRFs and logging them in the CID Log
• Reviewing all CRFs to determine whether additional information is required
• Forwarding the CRF to "Project Name" Leadership for approval
• Escalating all CRF issues and risks to "Project Name" Leadership
• Reporting and communicating all decisions made by "Project Name" Leadership
• Close the Change Request and update the CID Log when completed

5.3 "Project Name" Leadership (CIO, Program Manager, Business Sponsor)

"Project Name" Leadership is the Steering Committee or other authorized body who is the principal authority for all CRFs forwarded by the Project Manager. "Project Name" Leadership is responsible for:

• Reviewing all CRFs forwarded by the Project Manager
• Categorizing and prioritizing all CRFs
• Considering all supporting documentation
• Approving / rejecting each CRF based on its relevant merits and when necessary escalating to the executive steering committee.
• Resolving change conflict (where 2 or more changes overlap)

6) Procedure:

The use of the formal change management procedure will be required when any changes are discovered or requested which impact previously reviewed, approved and published project deliverables.

The documentation and tracking of all change requests will be managed using the defined procedure and facilitated by the use of the CID log.

6.1 Identify and Submit a Change Request

This process provides the ability to submit a request for a change to the project. The Change Requester:

• Identifies a requirement for change to any aspect of the project (e.g. scope, deliverables, timescales and organization)
• Completes a Change Request Form (CRF) and distributes the form to the Project Manager. The CRF summarizes the change:
• -Description- Facia Change for VIBS WM1... WM10 with the part no. x1... xn.
• -Reasons- Reduction in cost and better look
• -Benefits- User friendly and trendy
• -Costs- Cheaper
• -Any supporting documentation- relavent drawings and part list.
• -Approvals

6.2 Review the Change Request

The Project Manager and Lead reviews the CRF and determines whether or not additional information is required for "Project Name" Leadership to assess the full impact of the change to the project time, scope and cost. The decision will be based on factors, such as:

• Number of change options presented
• Feasibility and benefits of the change
• Complexity and/or difficulty of the change options requested
• Scale of the change solutions proposed.

The Project Manager will record the CRF details in the CID Log to track the status of the change request.

6.3 Approval of the Change Request

• Impact on the project in implementing the change (time, resources, finance, quality).

After a formal review, "Project Name" Leadership may:

reject or accept or request for modification.

6.4 Closing the Change Request

If the change is approved, the following will occur:

• The change will be communicated to the team
• Project deliverables will be updated to reflect the change
• The change request will be closed on the CID Log
• All approved change requests will be communicated in the "Project Name" status report