Implementing Salesforce or already using Salesforce? Do you have a well-defined development & release management process to ensure that you are doing it the right way, using all the proper tools & technologies, automating processes where it can and should be automated?
Do you have a proper process to ensure that you are building an optimal solution on Salesforce, leveraging on the platform’s features and capabilities, not incurring technical debt and not cutting corners on best practices?
Have you laid down the design/technical standards and best practices and made it mandatory for all admins, consultants, developers to read and follow it? Have you baked in a formal process to review the solution design before and after the build?
If not, the following quote from Steve Jobs may force you to pause and think if you are doing things the right way.
We had a fundamental belief that doing it right the first time was going to be easier than having to go back and fix it. And I cannot say strongly enough that the repercussions of that attitude are staggering. I’ve seen them again and again throughout my business life.Steve Jobs
But it may still not be too late. Why not take a look at the following development & release management process for Salesforce and see this something that you would like to use. You can start with this as a base and then modify/fine-tune it as per your requirement. This will also help you come up with a formal and documented process.
But I don’t claim to be an expert in Development & Release Management. The process that I have defined here is based on my experience & observations.
If you have any recommendations on how the whole process can be made even better or if I have missed out anything, please do let me know in the comments below and I will reach out to you for further collaboration.
Blog Change Log:
- 10-Jun-2021 – Added Scratch Org and line for smoke testing in Production
- 23-Mar-2021 – 1st Published