Introduction... 1 Management... 2 Activities... 3 Schedules... 5 Resources... 6

Transcription

1 Successful Projects don t Happen by Chance. Project XYZ Configuration and Change Control Plan Introduction... 1 Management... 2 Activities... 3 Schedules... 5 Resources... 6 Introduction This configuration and change control plan for project XYZ sets project-level policy that all changes to approved plan, scope, schedule, and cost baselines shall be documented, assessed, and approved or rejected by appropriate enterprise, organization, or project authority. Purpose. Successful projects require configuration and change control to ensure that the project delivers only what is asked for and mutually agreed upon. Scope. Configuration and change control apply to all project plans, scope, schedule, and cost baselines. Objectives. (1) Project work products and records are identified and controlled, (2) No change occurs except as a result of change control. Assumptions, Constraints, and Risks. Assumptions, constraints, and risks associated with this configuration and change control plan. References. This plan is consistent with PMBOK Guide, 5 th Edition, and the IEEE Standard for Software Configuration Management Plans (IEEE ). Glossary. No unique words or phrases are used in this plan. See ISO/IEC/IEEE 24765:2010 Systems and software engineering Vocabulary, Microsoft Corporation. Microsoft Manual of Style, 4th Edition. 2012, and the PMBOK Guide for definitions. Info@ProjectWeavers.com (855) PW-Sample Config and Change Control Plan ,. All Rights Reserved. Page 1 of 6

2 Project XYZ Organization. This configuration and change control plan is organized consistent with IEEE (above) and tailored for project XYZ. Each of the six sections begin with a brief summary of their purpose, scope, and objectives. Evolution. This document requires update whenever change occurs and should, at a minimum, be distributed for review and approval, monthly to secure formal approval of accumulated changes. Management Configuration and change control shall be coordinated by the change manager. Membership of assessment teams and change control boards is set by the following tables and as might be requested by the project sponsor and the project manager. Table 1. Configuration and Change Control Management Change Manager Project Manager Sponsor Primary Backup Table 2. Change control board by type and urgency Emergency Must Have Should Have Nice to Have Scope Schedule Cost Quality L M H L M H L M H L M H As required in Table 2, change control board membership shall consist of at least one of each of the following stakeholders: Table 3. Change control board membership by type and urgency Scope Schedule Membership PW-Sample Config and Change Control Plan Info@ProjectWeavers.com (855) Page 2 of ,. All Rights Reserved.

3 Successful Projects don t Happen by Chance.SM Cost Quality Table 4. Configuration and Change Control Board Membership by Area of Expertise Area of Expertise Primary Backup Activities Configuration and change control require two separate sets of activities: Configuration Control Controlled work products and records, including project deliverables, are identified in the source documents, contract (if exists), and charter. These are confirmed in the scope statement. The following activities address their identification and control: Configuration Identification. Each work product, record, and deliverable shall be uniquely identified and documented in a Configuration List. This section documents naming and versioning conventions and guidance, name, requirements to update, etc. Configuration Control. See Change Control, below. Configuration Status Accounting. This section sets plan for ongoing and periodic review of status of each work product, record, or deliverable. Info@ProjectWeavers.com (855) PW-Sample Config and Change Control Plan ,. All Rights Reserved. Page 3 of 6

4 Project XYZ Configuration Evaluation and Review. This section explains periodic audit to ensure integrity of the project work products, records, and deliverables as documented in the configuration list. Interface Control. If necessary, this section explains how are changes to the project s work products, records, and deliverables coordinated outside the project. Subcontractor/Vendor Control. If the project involves subcontractors or vendors, this section documents that relationship in terms of configuration and change control. Release management and Deliver. This section explains how work products, records, and deliverables shall be transferred to the sponsor. It should include the sequence of steps, approvals required, and timing anticipated. Change Control Process Change Control Change control involves eight basic processes: 1. Identify. A proposed or requested change is identified. 2. Document. A change request is created and submitted. 3. Validate. The change manager reviews the change request and either returns it for remediation or assigns it for assessment. 4. Assess. The change request is assessed for impact. 5. Schedule. Upon receiving impact assessment, the change manager shall assign the change request to the appropriate change control board. 6. Review. The chair of the change control board shall coordinate discussion and decision on the change request; reporting their action to the change manager. Identify Document Validate Assess Schedule Review Amend Contract Report PW-Sample Config and Change Control Plan Info@ProjectWeavers.com (855) Page 4 of ,. All Rights Reserved.

5 Successful Projects don t Happen by Chance.SM 7. Amend Contract or Agreement (if necessary). If the change involves contract terms, the change manager shall forward the approved change request to contract representatives for action. 8. Report. The change manager shall report approval or rejection of the change request. Schedules Configuration management and change control require two separate ongoing schedules: Configuration Management Once the configuration baseline is set, any changes shall be documented via version number when they occur. Periodic audits and review shall occur as follows: All work products and records should be checked in at the end of each work session. The change manager shall audit and review integrity of the configuration baseline, at a minimum, each week. The change manager shall be prepared to report status, if requested, each week. Change Control The schedule of change control activities depends on the urgency and impact of the change. As general guideline, which may be escalated by the sponsor or project manager: Emergency. Addressed immediately as quickly as required stakeholders can make themselves available. Must Have. Weekly, as coordinated by the change manager. Should Have. Weekly, as coordinated by the change manager. Nice to Have. At the next scheduled meeting relevant to the change request. Info@ProjectWeavers.com (855) PW-Sample Config and Change Control Plan ,. All Rights Reserved. Page 5 of 6

6 Project XYZ Resources Resources include lists identifying resources required for configuration and change control and outline or template of relevant work products and records. Identified Resources Stakeholders. Stakeholders as identified in Management, above, are documented in the project Stakeholder Register, which is found in the Project Management Plan or as may referenced there. Tool Baseline. Configuration and change control rely on the tool baseline set in the Project Management Plan, which, at a high level includes Microsoft Office 2010 suite of applications. No special tools are anticipated. Infrastructure. Configuration and change management shall rely upon the facilities and equipment available to the project team as noted in the Project Management Plan, see for example, the project communication plan. No special infrastructure requirements are anticipated. Work Products and Records Configuration List. The list shall include, at a minimum, any contract or standard identification of each work product, record, or deliverable, the name, format, location, status, requirement to update, and owner. Change Request Form. The written form shall include name of person originating request, date of request, title statement of the change, type of change (e.g., fix or enhancement), and detailed description or reference to where details are documented. As a change request is processed, each step will be documented, including, ultimately if the request is approved or rejected. Change Log. The log shall contain record of each change request and current status. The log shall contain, at a minimum, change request number, date submitted, title statement of the change, status, last and next action, and notes. Other. Agendas, minutes, peer review reports, status reports, etc., shall follow guidance set in the project management plan. PW-Sample Config and Change Control Plan Info@ProjectWeavers.com (855) Page 6 of ,. All Rights Reserved.