Reliable Releases: Building a Scalable Salesforce DevOps Process

Executive Summary 

A fast-growing commercial services organization had expanded its Salesforce environment faster than the development practices supporting it. Developers worked from a single shared code branch; releases followed no set schedule, and changes could reach production without consistent review, testing, or business approval. MRE Consulting helped the organization establish a repeatable process for planning, building, testing, approving, and releasing Salesforce changes using Azure DevOps and Salesforce DX. This process introduced separate development branches, required code reviews, clear testing and approval steps, and a regular sprint schedule. MRE also trained the client’s team to manage the process independently. The new approach resulted in releases with zero rollbacks, reduced defects through stronger user acceptance testing, and delivered the work on time and on budget. 

Technologies Implemented: ​​Salesforce DX,  Azure DevOps 

Challenge

As the organization’s use of Salesforce grew, the development team faced a growing user base with more complex requests and greater pressure to deliver. The practices for how they managed development did not support the new complexity, with developers working against a single shared code branch with no formal release cadence, no consistent code review process, and no shared definition of when a change could move into production

This created several business and delivery risks:

• Deployments could have conflicting code changes: Multiple developers making changes on the same branch could have changes that conflicted with each other, creating risk that one change could overwrite or interrupt the other.
• Production Deployments had unnecessary Risk: Changes could be deployed without regression testing, and there was no reliable way to trace a production issue back to the work item that introduced it.
• Deployments were difficult to predict: Without a regular release schedule, business leaders had limited visibility when new capabilities would be available. The perception was that the development team was slow in delivering new functionality.
• No Product Roadmap: The lack of a Roadmap made it difficult to forecast delivery dates or hold teams accountable to how new functionality would be available to support organization’s goals.

MRE realized that for the organization to accelerate its development with concurrent project workstreams, they needed a standardized, repeatable software delivery process that could scale with the organization, without slowing the business down.

Solution

MRE defined and implemented a DevOps operating model for Salesforce development, from source control strategy through to production release, built on Azure DevOps and Salesforce DX. Together, these tools and practices gave the team a consistent way to plan work, make changes, review code, complete testing, and release updates. MRE first established the governance and workflow the tools would enforce, then trained the team to run the processes and systems independently:

• Release-branch strategy: A single production-ready master branch, with a dedicated release branch established at the start of every sprint and feature branches for all developer work, eliminating direct commits to production code and allowing the team to combine and test planned changes before release.
• Governed Pull Request workflow: Every change moves from feature branch to release branch through a reviewed Pull Request linked to its Azure DevOps work item, with package.xml enforced in every branch so deployment resources are always source-controlled and traceable.
• Established Scrum delivery cadence: Sprint Planning, Daily Standups, Sprint Reviews, and Retrospectives to provide the team a predictable rhythm for development and releases. Business and technology teams gained a clear view of progress, checkpoints, and expectations, and a forum for continuous improvement.
• Visibility from Request to Release: Each work item moves through defined stages of Analysis, Development, QA, and UAT to Complete, each with a named owner and defined exit criteria, so nothing reaches production without being reviewed, tested, and formally accepted.
• Stage gate definitions: Formal criteria at every stage gate including requirements sign-off, testing, peer review, and user acceptance testing approval, so that quality is enforced by process.
• Roadmap: Regular processes for discovery and planning which look ahead to future business needs and how technology will be able to support it. This helped set expectations with business teams and business leadership, development teams and IT leadership.

Results

By establishing a consistent process and way of working from request to production deployment, MRE helped the organization move from risky deployments to controlled and a repeatable release process. The client can now deliver Salesforce changes with greater confidence and speed while coordinating business expectations to support a growing business.

• Delivered on-time and on-budget
• Zero production rollbacks: The organization has completed 20+ release cycles using the new process without requiring a rollback.
  Fewer production defects due to structured user acceptance testing process and stage gate.
• Improved traceability with code changes and pull requests linked to Azure DevOps work items.
• Stronger business engagement throughout software development lifecycle from request, user acceptance testing, release and adoption. More insight and looking ahead with roadmap development, providing alignment with business vision.