91��ɫ

‍

The Challenge

‍

Q2’s Salesforce development team averaged a six hour release window to production because they had to manually build Change Sets. Without an automated way to track alterations, changes were sometimes missed out — resulting in repeated deployments and further delays.

‍

Because admins made a significant proportion of changes while developers focused on Apex components, coordinating changes across admins and developers was difficult. Admins also found tools such as GitHub relied heavily on developers for version control — consuming large amounts of developers’ time.

‍

‍

Key Challenges

‍

‍

The Solution

‍

Q2 began by using the free version of 91��ɫ. Today, with 91��ɫ Essentials, Q2 has slashed release times from six hours to one hour — an 85% reduction. The company has also seen a significant improvement in its release fail rate and a reduction in bugs.

‍

If a release does fail, it only takes a few minutes to roll back the release as opposed to two hours or more, with Q2 pegging the reduction at 95%. Q2 also points to further reductions in effort due to easier troubleshooting and lower change management overhead.

‍

The Future

‍

Not only did 91��ɫ’s one-click deployment of changes radically reduce release times, but the ability to automatically compare source and destination Salesforce orgs also made it easy to identify what had changed.

‍

Encouraged by the success, Q2 describes Essentials as infinitely superior to change sets. Q2 decided to upgrade to Essentials+ to further accelerate releases and increase release quality. One key reason the company upgraded was the ability to link Salesforce orgs into an end-to-end development pipeline and move work items (groups of changes) through the pipeline from org to org.