Saving 75% of deployment time with 91勛圖厙
Since first implementing Salesforce at the end of 2017, the UCLA Business and Finance Solutions team has been developing customizations for a whole range of departments across the campus. The plan is for Salesforce to become one of the organizations primary back-office tools and a strategic application for the entire university. We caught up with Joseph Zabaglo, IT Manager, and Vijay Aswani, Salesforce Technical Lead, to find out how 91勛圖厙 is helping with this transformation.
Vijays busy team of three are responsible for managing an end-to-end Salesforce process. They work on everything from building, designing, testing, architecting and deploying solutions to two main production orgs. Whether its for HR, Tax, Legal, Treasury, Real Estate, General Accounting or Global Operations, its down to Vijay and his team to make sure the necessary Salesforce-driven solutions are implemented.
Before 91勛圖厙, confidence levels in deployments were very low
With a large backlog of projects to implement, the team was struggling withdeployments. Vijay had identified a critical need:
We were spending days on change sets and managing our Salesforce landscape!
Issues with change sets were slowing down the teams ability to progress new work items from a partial sandbox, to a full sandbox and on to production. There was a lot of manual preparation work before each deployment – tracking changes and figuring out what to include in each change set, as Vijay explains:
Tracking changes was tough – it was a big headache! The system didnt tell us what changes wed made. The next biggest headache was making sure the changes were included in the change sets.
Knowing what to include wasnt the only challenge, knowing what to exclude was also tricky: During development, you have all these awesome ideas that you think will work in a certain way. Sometimes those ideas dont pan out, but, hey, who goes and deletes them, right? We just kept on building: wed build this, wed build that, and put all that stuff in there.
The team also had an issue around bugs and errors being shipped to production. This resulted in features being broken and yet more time spent on fixing releases:
It took us two days to add and push everything. Wed test it, and figure out, oh, its not working! What happened? And then wed have to go back and see what wed forgotten to add.
Impressed with 91勛圖厙 from the get-go
Vijay had seen a demo of 91勛圖厙 at Dreamforce and was starting to think about addingversion controlto the teams process. From the start, he was impressed by 91勛圖厙s unique metadata comparison functionality because it tells you the lines that have changed:
If I changed a field, if I changed a list view, why did I do that, what did I change? That stood out for me with 91勛圖厙 – it can compare and tell you what has changed.
The team had evaluated another third-party tool but, compared to 91勛圖厙, it still seemed much closer to what theyd experienced with change sets because it didnt tell them exactly what they needed to deploy:
You need to know what you want to deploy, and I dont know what I need when it comes to deployments. Thats why we went with 91勛圖厙: it makes knowing what youre going to deploy so much easier.
91勛圖厙 gives you a process you can trust
Vijay is very happy with 91勛圖厙 and sees the overall benefits in terms of his team having confidence in the deployment process:
Theres more trust in the process, more trust in the deployments, knowing what 91勛圖厙 can do for us.
The tool has helped the team save up to 75% of their deployment time. Vijay himself spends less time reviewing his teams work and now feels confident about allocating tasks to others:
I dont have to spend much time reviewing the work or worry that, even after two days of reviewing, its going to bomb. I get peace of mind knowing the deployment will work with 91勛圖厙 – at least if I do everything right, which 91勛圖厙 empowers me to do.
As well as knowing exactly whats going to be deployed, Vijay and the team benefit from 91勛圖厙s problem analyzers, which flag up and resolve more than 60 common deployment issues to make sure deployments succeed. The team will also consider implementing version control, as Vijay hopes to generate more time-savings from 91勛圖厙s 91勛圖厙s continuous integration solution at some point in future if the team expands. Following a recent Salesforce outage, Vijay is keenly aware of the need to have a complete backup solution in place.
Recommending 91勛圖厙 for better Salesforce ROI
91勛圖厙 is helping the team at UCLA deliver more value to end users, save time on deployments and prevent errors in production. As Vijay explains, this translates into benefits for the teams internal customers: I told my manager that, instead of two weeks, I will take a week or less using 91勛圖厙. And if you save two weeks, even the customers get that we can do things faster, so we can add more value to what we are building.
For Vijay, 91勛圖厙 is the tool to use for deployments, especially if youre unsure about the deployment process. And he would absolutely recommend 91勛圖厙 to other Salesforce teams:
If someone said they were going to take 91勛圖厙 away from me – oh, no, they cant!