Generic PPM Templates - DOC

							 NICS Centre of Expertise
for Programme and Project
       Management




 Generic PPM Templates




                      Request
                        for
                      Change
                      CoE/RFC/01
  Project Name

REQUEST FOR CHANGE


       V0.1
Document History

Document Owner            The owner of this document is:


Document Location         This document is only valid on the day it was
                          printed and the electronic version is located …

Document Status           The current status for this document is DRAFT

Revision History          Date of next revision:

    Version    Revision date        Previous         Summary of         Changes
    number                        revision date       changes           marked




Approvals                 This document requires approvals to be signed off
                          and filed in project files

       Name               Signature         Responsibility    Date of     Version
                                                               issue




Distribution              This document has been distributed as follows

                               Name          Responsibility   Date of      Version
                                                               issue
Purpose               The purpose of a Request for Change (RFC)
                      notification is to request a modification to a product
                      or an acceptance criterion as currently specified.
                      Requests for Change should be recorded on the
                      Issues Log. The content of the example below
                      broadly reflects the recommended PRINCE2
                      requirements but has authorisation details also
                      included


Derivation            A Request for Change can be submitted by
                      anyone connected with the project. An RFC can be
                      submitted as such or the Project Manager can
                      define a Project Issue as an RFC


1. Quality Criteria   When assessing ‘fitness for purpose’, the following
                      items should be considered:


                         The source should be clearly identified
                         The RFC should be logged as an Issue
                         The RFC should be fully and accurately
                          described
                         The benefits of making the change should be
                          clearly expressed and, where possible, in
                          measurable terms
2. Sample Request for Change

REQUEST FOR CHANGE (Authority)               Issue No:

Change Title:                                Class:      Status:

Raised By:                                   Date:

Change Description:




Reason for Change:




Impact of change:




Implementation
Priority Assessment:   Decision:



Date allocated:                    Date completed:




Authorised Signatory
Name:                  Role:



Signature:             Date: