Change Log Template - British Columbia



<Note: Replace (or delete) bracketed text with required information><This is an interim template that will be reviewed and revised as time and resources permit. In the meantime, it is available to use and change as desired.> DOCPROPERTY Project_name \* MERGEFORMAT [Project Name] DOCPROPERTY Name_of_org \* MERGEFORMAT [Name of Ministry]NRS Change Management PlanProject Manager: DOCPROPERTY Author \* MERGEFORMAT [Business Portfolio Manager]Creation Date:2013-05-07Last Updated:2013-06-04Document Number:6450-25/[Project Name]Version:0.0.1Purpose of DocumentThis document defines the procedures and processes for managing changes that arise during a project.Table of Contents TOC \o "1-2" \f \h \z \u Purpose PAGEREF _Toc358107418 \h 3Procedures PAGEREF _Toc358107419 \h 3Process PAGEREF _Toc358107420 \h 4Process Inputs: PAGEREF _Toc358107421 \h 4Process Outputs: PAGEREF _Toc358107422 \h 4Templates PAGEREF _Toc358107423 \h 4VERSION HISTORYVersionDateResponsibleNotes0.0.12013-06-04Ian BedfordInterim Change Management PlanPurpose496824014605This is not the same as the Critical Support Change Request form, log or process, used for maintenance and support of an existing application.00This is not the same as the Critical Support Change Request form, log or process, used for maintenance and support of an existing application.Project changes are needed when it is deemed necessary to change the scope, time, cost or content of one or more previously approved project deliverables. Most changes will affect the budget and/or schedule of the project. Project changes generally arise as a result of an issue or risk event (or an opportunity) or from business decisions made by the sponsoring organizationA Change Management (or Change control) Plan outlines the mechanism or process the Project Manager will use to:Initiate, record, assess and resolve project changesEnsure all requested changes are documented and not forgottenTrack a single change request to an application throughout the life of the project during the projectProvide a history of all the change requests created during the projectProvide an audit trail of events and resolutions, with a consistent look and feel, captured in case an audit of the system occurs after the project is completed4968240193040“If it is not documented, it does not exist. As long as information is retained in someone’s head, it is vulnerable to loss” – Louis Fried, 199200“If it is not documented, it does not exist. As long as information is retained in someone’s head, it is vulnerable to loss” – Louis Fried, 1992ProceduresA process for recording, reviewing and approving a change to a system’s specifications, including levels of authority, is established early in the project and followed throughout. All changes must go through the review and approval process before being included in the project plans.The standard NRS Change Request and NRS Change Log linked to in this plan would be created and filed in the project repository by Project Managers. An NRS Change Request will be used to initiate and document all changes. A separate change request form will be created for each individual change requested by an authorized team member or vendor (see list below). All change requests will reside in <insert location>.A change log will be created for the project to record the history of all change requests and will reside <insert location>. The change log will be maintained by the Project Manager <or insert role> and reviewed at project status meetings <or insert when and frequency>.The change management process should be clearly communicated to all members of the project team and stakeholders and if a change is requested it should be submitted on the change request form. As the change request follows the change request process and is reviewed, approved or denied, the status will be updated in the change log.Who can initiate a change request?The following members of the project team <Business, Vendor or the Project Manager> will initiate change requests. The Project Manager will prepare the change request form. <list of project team members that can initiate a change e.g. Business Lead, Vendor Team Lead>Every change request will have: an "Owner" (who's responsible for ensuring the change request is resolved in a timely manner)an "Approver" (Project Manager or Project Sponsor based on level of authority)Change requests beyond the approval level of the project manager will be evaluated and approved either by the Project Sponsor or by the Project Steering Committee.ProcessThe change management process records, reviews and tracks requested changes in light of the approved project scope, budget, schedule and impact along with potential changes to approved deliverables already produced by the project.Process Inputs: Issue(s) that require a project change in order to resolve, orAn identified problem, concern, opportunity or risk that could be resolved or mitigated by changing some aspect of the projectProcess Outputs:A documented change request, ultimately closed (either approved and built into the plans and system specifications, or denied) with the rational for the options and decision.An approval process, including levels of authority, established early in the project and followed throughout. All changes must go through the approval process before being included in the project plans.A change log that captures the history of a change request.Templates HYPERLINK "" Link to NRS Change Request HYPERLINK "" Link to NRS Change Log ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download