Documents around employing changes to be safe and cost effective.
Request Forms
A form is sent detailing a problem. Should include:
- State of problem
- What needs to be fixed
- Desired outcome May be implemented as a Ticketing System
Purpose of Change
A reason for the change to occur must be given like:
- Improving users performance
Scope of Change
Who and what this change will affect. Document:
- Inventory of systems involved
- How long change will take
- Estimated cost of change
- How the change will take place
Document Date & Time of Change
- When change will occur
Determine Impact
Determining which systems and departments will be impacted as a result of this change.
Analyze Risk Levels
Conduct a risk analysis by asking questions like:
- What if update fails?
- Has it been tested before?
- Do current devices have adequate security to handle this?
Change Board Approvals
The request form is send and the board will review the document and give approval or a rejection.
End User Acceptance
- Conduct a census to see if this change is wanted
- Educate the end users of this new change and