Change Management Discussion Presentation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2015 11:46 AM
Thank you for the great discussion this morning at the OK SNUG. Attached is the PowerPoint from our presentation.
I would love to continue the discussion we started, please use this forum to answer / ask questions about Change Management, here are a few starter questions from our presentation.
- What questions do you have about the Phillips 66 Change Process?
- Do you have a CAB, Emergency CAB? What kind of decision making authority do they have?
- What fields do you require in order to schedule a change? What fields do you lock down upon submission for approval?
- How do you calculate risk?
- What approvals do you require?
Thank you very much!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2015 07:06 AM
We have both CAB and eCAB. Our CAB meets weekly, and the eCAB is as needed for emergencies as they arise, or for an approval required prior to the next scheduled CAB. Typically the weekly CAB is 20 minutes or less. Our CAB is a combination of IT managers and IT Process Owners, sometimes a manager is the process owner, such as Incident or Problem.
Required fields, are similar to what Paige listed above. Category/CI/Impact/Risk/Short Desc/Schedule/Change, Backout, and Test Plans/ and approvals.
One of our desired enhancements is to refine our risk calculation to be more response to risk, impact, and urgency.
We require 2 approvals, first is the technical approval, and second is the change approval. The technical is responsible to make sure that the change is appropriate for the situation and that it is as it should be. Change approval makes sure that the process was documented.