Summary
This procedure shall establish a change request process produced by the IT Application & Business Analyst division. The change request process provides formalized communication for proposing, documenting, and implementing changes within a system. It ensures that decisions do not compromise the IT systems or business operations.
Body
Purpose
This procedure shall establish a change request process produced by the IT Application & Business Analyst division. The change request process provides formalized communication for proposing, documenting, and implementing changes within a system. It ensures that decisions do not compromise the IT systems or business operations.
Scope
Change requests will be considered and circulated through the proper channels for collaboration and consideration.
- Change request: Receipt of an Application Change Request Form from a department.
- Formal assessment: Evaluation of the request to determine the impact of the change.
- Planning: Estimated hours to determine a Service Request or Project.
- Implementation: Design and configuration.
- Final assessment: User acceptance testing and approval
Responsibilities
- Department
- Documents change using the IT Change Request form.
- Meet with stakeholders for collaboration and consensus.
- Initiate a TDX Service Request by attaching the completed and signed change request form.
- Information Technology
- Approval of change (40+ hours will require a project in TDX).
- If the change request results in a TDX Project, PM will determine the grace period.
- No changes shall occur within the initial 90 days of a project implementation.
- Upon approval, IT works on updating the application with the changes identified in the change request.
- User Acceptance Testing.
- Implementation to PROD.
- Enforcement of guidelines.
Guidelines
Upon completion of a change request:
- Month 1 – 3: Users operate the application documenting issues.
- Month 4 – 5: The department identifies issues.
- Month 6+: Formal change request followed by IT review.