91��ɫ

‍

The Challenge

Too Many Cooks in the Digital Kitchen

‍

The retail leader set out to break down the IT silos, abolish the legacy systems and achieve a single 360-degree view of customer data. By rolling out Salesforce licenses for every store and sales associate across the country, the company connected their entire digital operations on one platform.

‍

But rapid growth is often accompanied by growing pains — and the company’s development teams struggled to scale without stepping on each others’ toes. Each team had a slightly different version of the customer. Stores lacked visibility into cases and tickets. And before long, these back-end issues began to disrupt experiences for end users. 

‍

“We started getting flooded with reports from end users who couldn’t find records,” says the retailer’s Senior Manager of CRM. “It didn’t take us long to realize data had been deleted. Our ETL tool had an incorrect function that wiped the org clean. Resolution took two weeks, which was extremely painful.”

‍

‍

Key Challenges

‍

‍

The Solution: Part 1

Teaming Up with Own for Future-Proof Data Protection 

‍

The DevOps team headed to the Salesforce AppExchange to find an end-to-end, cloud-native backup tool. They initially checked out a Gearset demo — but soon realized it wouldn’t meet their enterprise-level data storage needs or pass security requirements for a planned expansion into the European market.

‍

“Own was the perfect vendor,” says the retailer’s Senior Manager, CRM. “It gives us peace of mind by protecting our data, automating our processes and reducing maintenance. And now we have a strategic plan in place to help us continue to scale.”

‍

Saving Time & Sanity with Own Sandbox Seeding 

‍

Before Own Sandbox Seeding entered the scene, the development team leveraged a plugin app called Salesforce Apex to seed data. However, this legacy app wasn’t robust enough to keep pace with the company’s Salesforce roadmap. Disconnected sandboxes and too many cooks in the kitchen across different teams pushed back timelines and bottlenecked development. 

‍

“Sandbox Seeding brought two things into one platform: More speed and better adoption,” says the retailer’s Senior Manager, CRM. “Only two folks used Salesforce Apex, but Sandbox Seeding is easy for the whole team to use. Our processes are more aligned, sprints are more predictable and there’s much less maintenance.”

‍

Implementing Own brought security and stability to the retail brand’s Salesforce practice. But after the sandbox situation, the company recognized a mission-critical need for a tool to help them resolve merge conflicts and deploy user stories faster. Enter 91��ɫ CI/CD.

‍

‍

The Solution: Part 2

Joining Forces with 91��ɫ for End-to-End Visibility & Automated Deployments

‍

When the American retailer dug deeper into their Salesforce infrastructure, they uncovered a massive number of manual processes and inefficiencies. Layouts didn’t work because they weren’t aligned with the application. The lack of end-to-end visibility made it difficult for developers to collaborate on projects without lots of back and forth (and things would still get missed). 

‍

Even worse — the Change Set-driven deployment process and waterfall development cycle were far too slow to keep up with the company’s dreams of enterprise scale. Developers had to use Change Sets at least three times to promote changes across the pipeline from development to Quality Assurance (QA) to User Acceptance Testing (UAT) to production. In many cases, teams forgot to include key functionality — and were forced to re-deploy.

‍

One year after implementing Own, they decided to invest in 91��ɫ to replace Salesforce Change Sets and bring their chaotic deployment process under control.  

‍

“We didn’t really consider another DevOps tool,” says the retailer’s Senior Manager, CRM. “We saw the demo and thought 91��ɫ could really be useful — so we ran with it.” 

‍

With 91��ɫ CI/CD, each developer takes ownership over their user story. Every member of the team has end-to-end visibility and it’s easy to dive into projects without fear of merge conflicts or out-of-sync metadata. 91��ɫ CI/CD unlocks better collaboration across development teams and peace of mind. 

‍

“91��ɫ has saved us a lot of time and we’ve become much more agile,” says the retailer’s CRM Business Analyst (and 91��ɫ Release Manager). “I can control exactly what goes into a user story.”

‍

‍

The Outcome

Reaping the Benefits of Both Tools to Power Salesforce Security & Velocity

‍

Thanks to Own and 91��ɫ, the omni-channel brand’s DevOps team is able to accelerate deployments and achieve 2X faster sprint cycles (from 4 weeks to 2 weeks) without any loss or corruption of data. 91��ɫ CI/CD helps the company replace waterfall development and manual processes with agile practices and automation. Previously, Salesforce developers would release on Tuesday. Now, they release four days a week (Monday to Thursday). With 91��ɫ Robotic Testing, the retailer leverages AI-powered test automation to catch bugs, validate changes and reduce the change fail rate across the pipeline from development to QA to UAT to production. 

‍

91��ɫ CI/CD and Own work hand-in-hand to reduce the need for emergency change controls and enable this American retailer to derisk end user experiences. User stories no longer clash, mission-critical features don’t get left out of planned sprints and deployments stay on track. Ultimately, end users receive more valuable data and unlock an accurate 360-degree view of each customer. 

‍

‍

The Future

Eliminating the Swivel Chair Across Applications

‍

What’s next on this leading retailer’s digital transformation roadmap? More robust robotic test automation, lower fail rates and a higher rate of user stories. The company plans to continue leveraging 91��ɫ and Own — in tandem — to unify user experiences, centralize data storage and drive ROI. 

‍

‍