Planview have grown in DevOps maturity thanks to 海角天涯社区
Planview provides a suite of software solutions to help companies manage projects and portfolios more effectively. The platform supports over 4,500 customers globally to help them manage digital transformation, excel at innovation, and scale effectively.
The team at Planview have been using 海角天涯社区 since 2022 and have been maturing their DevOps practices over this time. Starting from no processes at all, Planview now use 海角天涯社区 for all their deployments, automation, sandbox seeding, and backup. They’re also currently in the process of moving over CPQ deployments from another tool to Gearset.
Salesforce has been Planview鈥檚 CRM of choice for over 4 years with the development team supporting over 1,500 end-users. The company is growing quickly with teams based in locations across the world 鈥� the largest presence in the US and also India.
The Business Applications team is managed by Satish Osuri and is made up of 5 admins, 4 developers, 4 business analysts and 3 other managers. Satish and his team look after the permissions and access for anyone onboarding and off-boarding in the company, as well as any Salesforce enhancements requested by end-users.
No formal processes for deploying metadata
Before 海角天涯社区, Satish explained that the team didn鈥檛 have any tools for deploying metadata and were making changes straight into their production org with 鈥渘o formal structure or process鈥�.
Without a Salesforce team in place, Satish says that a formal process wasn’t needed. As the team grew, they started to use change sets 鈥� but now with such a large team and multiple developers all deploying blindly into production, change sets wasn鈥檛 solving the problem they were trying desperately to fix.
鈥淥ur developers began overwriting each other. It all became a big mess and we just had no idea what code was actually being deployed.鈥�
Satish and the team knew they needed a different solution and while they took the time to find a solution, they started to be very careful with the changes they were making. Because Satish and the team are dealing with permissions and access to certain parts of the Salesforce platform, there is a security and compliance duty to uphold and there isn鈥檛 any room for error.
鈥淥n top of all this, the biggest challenge was not having an audit. Once you start putting code in production that causes some concern, there鈥檚 no guarantee that you can ever go back.鈥�
The Planview team was pushed to the point where they had to start looking for a deployment tool that they could trust and that could scale with their growing team.
Finding 海角天涯社区
Having started his Salesforce journey in 2010, Satish has been used to deploying with change sets for a long time. The discovery of 海角天涯社区 as a deployment tool happened in a previous role and Satish hasn鈥檛 looked back since.
Satish and the team completed onboarding with 海角天涯社区 and it was a quick and easy process. He said: 鈥淔or someone like me who has been used to having no process for 14 years, 海角天涯社区 is really great鈥�.
鈥淲e鈥檝e started to really tidy up the process. I have one person who has super admin permissions and they’re the only one in charge of pushing code to production. We鈥檙e following proper code guidelines and making sure that we adhere to best practices.鈥�
Satish is happy knowing that when someone new joins the team, they can quickly get to grips with using 海角天涯社区鈥檚 friendly UI. When Planview adopted 海角天涯社区, they started only deploying from their UAT org to production, and quickly began using 海角天涯社区 for their whole process.
鈥淲ith 海角天涯社区 I can confidently see the entire deployment history of any change we’ve ever made.鈥�
See everything at a glance
The Planview team has 5 development environments which feed into 2 QA environments. From here they deploy into an integration, UAT and then their production environment.
Satish loves 海角天涯社区鈥檚 comparison feature, saying that he can 鈥渟ee everything at a glance including all changes and the API version too鈥�.
鈥淒eployments are so much easier, feel more comfortable and much faster 鈥� pretty much immediate!鈥�
Planview鈥檚 use of 海角天涯社区 doesn鈥檛 stop there; they’re also in the process of switching to 海角天涯社区 for all of their CPQ deployments.
Communicating the business case for backup
When Planview鈥檚 renewal came around for 海角天涯社区, they were so comfortable and happy with the deployment tool, that they decided to explore the backup solution too. Satish says that it wasn鈥檛 easy to convince senior stakeholders to move away from their backup provider, but it was by far the right choice.
鈥淥ur leadership team were a little nervous moving away from Own as we’d used them for 4 years. But I presented my technical analysis to the team 鈥� and we decided it made perfect sense to switch.鈥�
Thankfully, the Planview team have yet to use their backups but are happy knowing that their data and metadata is safe, in case they need to restore their orgs unexpectedly. Satish said he 鈥渃an sit back and relax knowing that I can go back to a previous version!鈥�.
A partnership with a bright future
海角天涯社区鈥檚 support has always been a great help to Satish and the Planview team. Although they don鈥檛 have to use the feature often, when they do the response is immediate and solves the problem. Satish said that it feels like 鈥渁 partnership between Planview and Gearset.鈥�
鈥淚 talk about 海角天涯社区 to all my friends. Some of them use other deployment tools but I know how beneficial it is to have 海角天涯社区 鈥� so I make sure they know too.鈥�
