Everything is different when it’s bigger, and DevOps is the same. But what does ‘bigger’ mean in the context of embracing DevOps in the Salesforce platform? Today, let’s consider what you will need to change, and how you will account for those changes as you manage your DevOps transformation?
For many organizations, ‘bigger’ simply means doing more things at once. Here are a few concepts we often challenge our customers to consider and plan for, when they look at their DevOps programs and the tooling that drives it.
Supporting Team Independence and Autonomy
We develop in teams, and DevOps thrives when your culture reinforces independence and autonomy for those teams. Your governance processes define company-wide guide rails, but how do you empower each team to set their own specific practices within those rules? And just as importantly, do your tools simplify or hinder the natural growth in the teams that are driving innovation in your company?
Your teams are always going to be morphing and adapting, with changing members, different vendors, shifting structures, and objective focus. The onboarding and offboarding experience that you provide for your team members will significantly affect the performance and reliability of the culture and skillsets you build.
Easing Parallel Workstreams
Can you walk and chew gum at the same time? Parallelism is one of the biggest pain-points at many enterprise-scale operations. It’s such a common pain that it’s often seen as an unattainable goal. But it’s not.
DevOps is fundamentally about the flow of change, so how does your program avoid turbulence when you have more than one stream of changes making their way through your system? There are several key factors at work here: governance, architecture, and tooling. The key is learning how to balance each of them to deliver more change, more quickly, at lower costs.
Reducing Maintenance Overhead for Multi-Production Environments
If you don’t already, you will end up with more than one production org. How unique are your orgs? More importantly, how unique are the codebases, release paths, rollback strategies, and monitoring processes for each of your orgs? Salesforce DX is continually providing an ever-expanding set of new options for how we manage our orgs; including scriptable configuration and new development models.
Your DevOps strategy needs to foundationally extend - not compete with or replicate - the innovation coming out from the Salesforce DX team. Each release includes new capabilities, and enhancements to existing ones, that you can leverage to further standardize the long-term management, maintenance, and monitoring of your orgs.
Planning for Splits, Mergers, and Acquisitions
Growth in an enterprise is not smooth and organic. You will face moments of major change including production org splits, mergers, and acquisitions. It’s very common for these changes to include additions or re-organizations in your team structure and the adoption or modification of core infrastructure like your DevOps stack. Is your program flexible enough to accommodate these changes?
There is aggressive and exciting innovation happening in and around DevOps. Does
your program prepare you to be nimble around your tooling?
These problems aren't trivial, and software alone is not the solution. DevOps success in enterprise is built from a comprehensive mix of governance, tooling, training, and partnerships. And I would be delighted to discuss this further if you’d like to get in touch.
Appirio DX closes the gaps to adopting and executing DevOps principles by building upon Salesforce DX. It is a set of licensable tools and professional services from Appirio, a Salesforce Global System Integrator with a history and experience of working at the enterprise scale. Our experience and intellectual property drives our software roadmap and is the basis for the ongoing training and standards that we define for our DevOps Architects and DevOps Engineers.
For more information, click here to fill out our contact form.
Next time, let’s look at how to approach tool selection in Enterprise.
About the AuthorFollow on Linkedin More Content by Roarke Lynch