Change Management

The change management workflow adds speed and precision to developing, testing, and deploying application changes all while maintaining quality and system integrity. A project was created to speed the majority of the ancillary processes,
which are routine but time consuming, freeing personnel to concentrate on areas that required critical thinking and expertise.

The Development Team members (Devs) perform their code development and check in their code. The Devs then deploy a project that will build and deploy it on the Dev environment. Integration QA tests the changes in the Dev environment. If it passes their tests, Integration QA adds a Test Pass Note and Odyssey deploys a project to the User Acceptance Testing (UAT). UA tests the changes in the UAT environment. If it passes their tests, UAT deploys a project to begin the next phase. Because this is leaving UAT and proceeding to Production, the project requires one or more approvals, and Odyssey notifies the Approvers that UAT has requested deployment to Production. The Approvers then review the request and approve (or reject) the deployment. Once approved, the project deploys the code to production and to the
disaster recovery site.

Note that this flow encapsulates the best practices in a standard environment. The basic workflow can be modified asnew best practices are designed. The technologies can be swapped through changing the Task Agents.