1. A change request is submitted to the IT department via a internal ticketing system.
2. The change request is reviewed by the IT manager.
3. The IT Manager approves, denies or suspends the request.
4. Once approved, the IT Manager assigns resources to the change request.
5. The IT Manager and the assigned resources assess the level of effort required to complete the change.
6. The IT Manager establishes a due date that is acceptable to the requestor of the change.
7. The assigned resources develop a design and implementation plan if needed.
8. The IT Manager reviews and approves the design and implementation plan.
9. The assigned resources execute the implementation plan and obtain additional input from the IT Manager and or requestor on an as needed basis. All change related communication is tracked via app.asana.com.
10. If the agreed upon due date cannot be met, the assigned resources, in conjunction with the requestor, request a change in scope or due date. A reason for the change is formally documented.
11. After the implantation plan has been executed, a series of test cases are implemented where necessary.
12. If necessary, the requestor will test the change and confirm that the change has been implemented to the desired specification.
13. After the change has been sufficiently tested, the change is scheduled for production release.
14. In concert with the requestor, an agreed upon deployment date is established.
15. The change is implemented on the agreed upon date and time after a system backup has been taken.
16. After the change has been implemented and confirmed by the requestor, the change request is closed out in the internal ticketing system.
17. During project closeout, the change request ticket is reassigned to the requestor for closure.
Note: All source code and test cases are stored in a source control system.