This is the text based version of Change Request Process Flow.
Standard Change
| Stage | Change Task | Change Approval | Performed by |
|---|---|---|---|
| 1 | Request for Change Logged | Any OCIO Team Member | |
| 2 | Review RFC Task | Change Coordinator | |
| 3 | Authorized to Build, Test and Release | Change Coordinator | |
| 4 | Build, Test and Release RFC Task | Any OCIO Team Member | |
| 5 | Post Implementation Review | Change Coordinator |
RISK Level: Minimum
General Definition:
- Low risk and no impact planned during the change period
- Process is repeatable (process must be successfully repeatable)
- All changes previously considered to be routine
- Approved to this status in advance by CAB
Minimum lead time of the Request to Authorize for Release:
One business day unless otherwise define for each Standard Change upon initial approval.
Minor Change
| Stage | Change Task | Change Approval | Performed by |
|---|---|---|---|
| 1 | Request for Change Logged | Any OCIO Team Member | |
| 2 | Review RFC Task | Change Coordinator | |
| 3 | Authorized to Build? | Change Coordinator | |
| 4 | Build RFC Task | Any OCIO Team Member | |
| 5 | Authorized to Test? | Change Coordinator | |
| 6 | Test RFC Task | Any OCIO Team Member | |
| 7 | Authorized to Release? | Change Manager | |
| 8 | Release RFC Task | Any OCIOTeam Member | |
| 9 | Post Implementation Review | Change Coordinator |
RISK Level: Low
General Definition:
Combined Risk & Impact Ranking <8
Risk Factors
- Experience baseline moderate
- Not Complex
- No Planned Service Outage
or
Any Planned Service Outage must be contained within the Maintenance Window and have very little risk of additional user impact during or after the change.
Impact
- More than 1 user affected
Minimum lead time of the Request to Authorize for Release:
3 business days before the target implementation date
Major Change
| Stage | Change Task | Change Approval | Performed by |
|---|---|---|---|
| 1 | Request for Change Logged | Any OCIO Team Member | |
| 2 | Review RFC Task | Change Coordinator | |
| 3 | Authorized to Build? | Change Coordinator | |
| 4 | CAB Review | Change Advisory Board | |
| 5 | Build RFC Task | Any OCIO Team Member | |
| 6 | Authorized to Test? | Change Coordinator | |
| 7 | Test RFC Task | Any OCIO Team Member | |
| 8 | Authorized to Release? | Change Manager | |
| 9 | Release RFC Task | Any OCIO Team Member | |
| 10 | Post Implementation Review | Change Coordinator |
RISK Level: High
General Definition:
Combined Risk & Impact Ranking ≥8
Risk Factors
- Experience baseline low or failed in past
- Very Complex
- Planned Service Outage or the risk of user impact during the change (i.e. high risk during or after the change)
- Difficult to fully test
- Difficulty to back out
Impact
- Extensive/Widespread cessation of core service to the business
- 2 Significant/Large multiple users affected
Minimum lead time of the Request to Authorize for Release:
As soon as Change is known and/or has received management support decision (Between Initiation and Planning phases of project) must include 2 CAB meetings prior to release.
Urgent/Emergency Change
| Stage | Change Task | Change Approval | Performed by |
|---|---|---|---|
| 1 | Request for Change Logged | Any OCIO Team Member | |
| 2 | Review RFC Task | Change Coordinator | |
| 3 | Service Owner Authorization? | Service Owner | |
| 4 | SLT Authorization | SLT Member | |
| 5 | Authorized to Release? | Change Manager | |
| 6 | Build RFC Task | Any OCIO Team Member | |
| 7 | Test RFC Task | Any OCIO Team Member | |
| 8 | Release RFC Task | Any OCIOTeam Member | |
| 9 | Post Implementation Review | Change Coordinator |
RISK Level: Highest
Emergency Change resolves a Priority 1 Incident (may be completed in retrospect), or a Priority 2 Incident.
Urgent Change is any change where business need does not allow for it to be scheduled as a Normal Change.
Minimum lead time of the Request to Authorize for Release:
As Soon as Possible