Request for Change Form

Document Sample
Request for Change Form Powered By Docstoc
					                                                                             Fordham Project Management Framework
                                                                                                 (FPMF)

                                            REQUEST FOR CHANGE FORM

                      Complete the Request For Change Form. Save & Email completed form to: SPO@fordham.edu

       EVENT NAME:                                   FUNCTIONAL DEPARTMENT:               APPLICATION NAME:



                                                                      DATE SUBMITTED:        START TIME:

       SYSTEM NAME:                     REQUESTING OFFICE/AREA:       PRODUCTION READY:      FAIL SAFE TIME:

                                                                      GO-LIVE DATE:          END TIME:


       REQUEST #:                       REQUESTOR:                                           DISTRIBUTION:




       TYPE OF CR:                            REGULAR                                     LITE

                                              ACCELERATED – PROVIDE REASON:




  DESCRIPTION OF REQUESTED CHANGE
       DESCRIPTION OF CHANGE / ISSUE: (Describe WHAT has been or will be done – in non-technical terms)




       REASON FOR CHANGE / NEED FOR RESOLUTION (Describe WHY the change is necessary; Include Benefits
       and what will happen if we don’t make the change)




       ALTERNATIVES




   IMPLEMENTATION OF REQUESTED CHANGE

       ACTION REQUIRED TO IMPLEMENT CHANGE:




Fordham IT / Strategic Program Office                             1                                            V 2.0 15-May-12
       PRODUCTS, PROJECTS, T ASKS, ETC., AFFECTED DURING IMPLEMENTATION – INCLUDE SYSTEM OR SERVICE
       OUTAGES


       Affected Systems:
       Affected Business Services:




       IMPACTED COMMUNITY MEMBERS (Who will be inconvenienced during the maintenance, and what will they
       Not be able to do? Students, Faculty, Staff, WAVES users, Blackberry users, etc.)




       COMMUNICATION/NOTIFICATION (Indicate whether communication should be sent to community members
       and which ones)


       YES          or NO          (check one)
       If yes, specify:



       EXPECTED COSTS AND TIMESCALE




       RESOURCES REQUIRED. DEPARTMENTS, VENDORS




       ADDITIONAL COMMENTS/BACKUP/TEST PLAN (include the test plan and/or Director level approval if no test
       plan is attached, when appropriate)

       CHECK BOX, IF APPLICABLE
          The work or the proposed back-out plan bypass or will bypass normal accounting and auditing
       procedures.

           MYFILES link to the work authorization form.

           MYFILES OR MS PROJECT SHAREPOINT link to the test plan/backout plan.



       STATUS UPDATE (brief update after work has been completed, cancelled etc.) OPTIONAL




Fordham IT / Strategic Program Office                     2                                     V 2.0 15-May-12
                                         CHANGE MANAGEMENT FORM FIELDS

 Field                                        Description

 Event Name                                   Short descriptive name of Event or Project Name [e.g., Mirapoint upgrade]

 Functional Department                        Functional Department overseeing the event [e.g., ETS/Comp Services]

 Application Name                             Name of the software impacted [e.g., Mirapoint, Lotus Domino, Lotus NAB,
                                              Banner Advancement, SIS, Blackboard, Xythos, Luminis, InCircle,
                                              PowerFaids, etc.]

 System Name                                  Name of the System impacted [e.g., Fire-Mail03, Fire-AMS02 LDAP, Fire-
                                              BES03, LARS, BESS, WEB-App03, etc.]

 Requesting Office/Area                       Office/Area of the requestor [e.g., Messaging Team, Internet Services,
                                              Enrollment, DAUR, etc.]

 Date Submitted, Production Ready, Go-        Date submitted to SPO, Production Ready Date, & Go Live Date
 Live date
 Start Time, Fail Safe Time, End Time         Requested time for work to start, roll back, and end


 Request Number                               Change Request Number [entered by Chg Mgmt Coordinator]

 Requestor                                    Your Name

 Distribution                                 CMB plus affected departments, etc.

 Description of Change/Issue                  Include descriptive words like upgrade, restart, fix, etc.

 Type of CR                                   Regular, Lite, Accelerated

 Reason for Change/Need for Resolution        Why is this change necessary? What is the consequence of not implementing
 (Include Benefits)                           the change?
 Alternatives                                 What other actions can resolve this issue?

 Action Required to Implement Change          What specific tasks will be done to accomplish the work?

 Affected Products, Projects, or Tasks        List services, applications, projects, etc., affected by the implementation of
                                              the proposed change        – Include System or Service outages
 Impacted Community Members                   List who will be inconvenienced during the maintenance, and what will they
                                              Not be able to do?

 Communication/Notification                   Indicate whether communication should be sent to community members and
                                              which ones

 Expected Costs and Timescale                 List the expected expenses and resources required to complete the
                                              implementation of the change [e.g., 1 week testing; 2 hours PM]

 Required Resources, Departments,             List necessary resources to implement the solution [e.g., DBA 3 hours]
 Vendors
 Additional Comments/Backup/Test Plan         Add any additional information, the backup/test plan, and/or Director level
                                              approval, when appropriate
 Status Update                                Add a brief update after work has been completed, cancelled etc. [This is
                                              optional]




Fordham IT / Strategic Program Office                       3                                                  V 2.0 15-May-12

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:9
posted:8/8/2012
language:
pages:3