Genesys Change Control – Improve your DevOps processes

We have all seen the painful cycle of the manually driven release process used in the customer experience industry. Changes get developed in a Dev environment and once stable are manually reproduced into a UAT environment for user testing. If all goes well, a change control process sees these changes documented and eventually the work is manually deployed into the Genesys production environment.

But, Are we engineers or data entry monkeys?

These sorts of processes are needed to ensure quality releases and prevent outages with the contact center platform. However, there is a trade off, engineering time vs down time. Generally, adding processes and quality checks is the answer when faced with risk but increasing these process usually slows everything down. Furthermore, these processes are all manual, which introduces more human error. This means the law of diminishing returns quickly kicks in.

How do you work around these manual processes? 

We like to promote processes that reduce risks while significantly speeding up your deployments. The key is in the ability to automatically move changes from one environment to another, removing human error and generating change control documentation along the way. Making a fast, high quality release with accurate documentation.

 Stop performing manual changes in production.

It is the greatest cause of outages and consumes a lot of engineering time. With the use of InProd, changes can be grouped into a ‘changeset’ and be treated as a reusable object. This allows promoting changes between environments and reuse of previous work. How many times has the same change been repeated within your environment. To learn more about simplified Genesys change control, get in touch with us today.