1. Enterprise Applications Change Management Process Enhancement Presentation October 1 st 2009

2. Agenda Charge Current State Proposed Options Suggested Option GOAL: Balance control and customer responsiveness

3. Charge Add Senior Management Approval to Enterprise Applications Change Management Process Use an appropriate communication approach for change communications

4. Current State of Ent. Apps. Change Mgmt. Process Currently using a documented and continuously audited (14+ years) change process see: topic 250181952 – “The Management Information Systems (MIS) Department Configuration Management Process” in the MIS Tech Journal Process has been utilized for controlling changes to the Enterprise Applications when they were maintained by the BSS and FI sections. Change documentation accessible on Fermi Network (Web browser and Notes Client) Process has multiple control checkpoints

5. Current State of Ent. Apps. Change Mgmt. Process Meshes change management workflow (BSPTA application) and code control (Allfusion Harvest) Demonstrates segregation of duties Has recently been changed to add a Change Advisory Board Control to the release process Not used for some systems and services that Enterprise Applications depend on

6. BSPTA Application Tracks all aspects of a change Maintains comprehensive metadata (Dates, People, Request Info, Request change info, etc.) Provides Detailed lifecycle Management Has ability to record wide variety of data types. (Screen Shots, File Attachments, etc.)

7. BSPTA Details Change details with text, file attachment s, and other rich content Change Description Current Workflow Information https://bss-support.fnal.gov/project/bspta.nsf/tasklink/14055

8. BSPTA Workflow Steps From item 14051 Detailed Workflow Information People involved in the change

9. BSPTA Meta data Automatic generation of change log (in grey) User Comments (in black) Example of Screen Shots in Comments

10. Code Management uses Allfusion Harvest (Harvest) Code Management Steps Map to BSPTA Steps

11. Harvest Package Names Map to BSPTA Items

12. ECS Change Advisory Board Uses a documented process see http://bss- support.fnal.gov/Products/SNP_BOOK.nsf/wip/280811274?openDocument http://bss- support.fnal.gov/Products/SNP_BOOK.nsf/wip/280811274?openDocument Meets on a weekly basis Includes Development/PM/Service Owner stakeholders Provides a web accessible Fermi network available change log See https://bss-support.fnal.gov/project/bspta.nsf/tasklink/14055https://bss-support.fnal.gov/project/bspta.nsf/tasklink/14055

13. CAB Log –Prior Week’s Changes

14. CAB Log –Forward Looking Changes

15. Possible Options for Adding Senior Management Approval to Process A.Move Enterprise Applications Change process to Computing Division Change Process B.Add Lifecycle step to the BSPTA workflow process for Senior Management Approval C.Provide e-mail copy of ECS CAB log to Senior Management for them to approve and send back D.Member(s) of Senior Management and the Communication Group attends CAB meeting and approves with other stakeholders

16. Proposed Option Member(s) of Senior Management and the CD Communication Group attends CAB meeting and approves with other stakeholders – Reduces possibility of adding lag time to change implementation – Provides ability for senior management to get quick feedback on questions – Adds to the “legitimacy” of the process – Incorporates the Communication Group to improve the communications about system changes