����ý

‍

The Challenge

‍

In 2018, Zen began using Sales Cloud to manage the company's sales pipelines and integrate with Pardot for marketing automation. Their Salesforce usage grew, but they didn’t have a software strategy or delivery plan.

‍

There were a few other problems as well. For example, they had a lot of solo admins, many of whom made changes directly into the production. They also ran testing within the production, which caused frequent problems. Zen made releases daily, but they were riddled with errors.

‍

They soon realized they needed a DevOps tool to manage everything.

‍

‍

Changing The Game With ����ý DevOps

‍

Other Zen teams were using Azure DevOps, but that didn't work for his team as they weren't able to push their change sets through. He knew the tool needed to work seamlessly with Vlocity, which Zen had implemented to simplify its lead nurturing.

‍

That’s when they discovered ����ý.

‍

Key Challenges

‍

‍

The Solution

‍

The transformation of Zen's delivery process began with getting a four-stage pipeline in place that allows the company to get every change into a single environment before it goes upstream. Now, Zen is moving toward a predictable weekly release cycle.

‍

����ý also provides a single place to document all the team's work. In the first four months with ����ý, Zen's development team has become much more efficient compared to working with change sets. They have full traceability and are able to roll back a release if needed.

‍

The Future

‍

����ý has enabled Zen to dramatically reduce their fail rate. Zen uses ����ý to build flows to convert cases into user stories.  ����ý also allows the Zen team to see all their DevOps work in one place and track who is responsible for specific tasks.

‍

As the development team explores more of ����ý's capabilities to achieve Continuous Integration/Continuous Delivery (CI/CD), they want to automate testing as well as the back-populating of environments after a new release.