<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Matt Dickens on Medium]]></title>
        <description><![CDATA[Stories by Matt Dickens on Medium]]></description>
        <link>https://medium.com/@gearset_matt?source=rss-911726b68092------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aipsYcerg3XB_UpY8svZrQ.jpeg</url>
            <title>Stories by Matt Dickens on Medium</title>
            <link>https://medium.com/@gearset_matt?source=rss-911726b68092------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:16:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gearset_matt/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Gearset’s Approach for Assessing DevOps Maturity]]></title>
            <link>https://medium.com/salesforce-architects/gearsets-approach-for-assessing-devops-maturity-a240a9e425e?source=rss-911726b68092------2</link>
            <guid isPermaLink="false">https://medium.com/p/a240a9e425e</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[salesforce-architect]]></category>
            <category><![CDATA[inside-salesforce]]></category>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[gearset]]></category>
            <dc:creator><![CDATA[Matt Dickens]]></dc:creator>
            <pubDate>Tue, 11 Jan 2022 17:58:37 GMT</pubDate>
            <atom:updated>2022-01-31T16:08:26.900Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fq3nLVS-LACspkTg8KmGAA.png" /></figure><p>From a Salesforce perspective, DevOps is ultimately about empowering teams of admins and developers to ensure that Salesforce delivers for their businesses. It’s a way of working — underpinned by tools and processes such as version control, CI/CD, and backups — that enables teams to release higher quality work to their end users faster and more reliably. The move to DevOps typically involves a cultural change. Teams work more iteratively, developing the agility to respond to users’ feedback. And they work more collaboratively, breaking down the silos that separate devs and admins.</p><p>Business today evolves at a rapid pace and organizations demand new features and functionalities to keep up with the needs of their customers. As a result, Salesforce teams have to scale their development and release management practices to keep up. Robust, automated DevOps practices can dramatically boost productivity and efficiency, enabling teams to release new work faster, more frequently, and more reliably. But knowing how to get started, or where to go next on your DevOps journey can be difficult.</p><p>This post explains why teams implement DevOps for Salesforce projects, outlines the first steps to get started, and describes Gearset’s <a href="https://gearset.com/assets/resources/how-mature-is-your-salesforce-devops.pdf">maturity matrix for Salesforce DevOps</a>, which can help architects assess how mature their company is on the DevOps spectrum in order to determine the right mix of tools and processes to fit their team.</p><h4>Gearset’s DevOps philosophy</h4><p>At Gearset, we understand that DevOps maturity is a spectrum, and teams begin from different starting points. We don’t think companies should spend six months implementing an entirely new process; DevOps is about incremental improvement, and we think it’s best to adopt DevOps itself incrementally. Gearset tools are designed to make DevOps adoption easy, by quickly solving the immediate challenges teams face, then helping them mature into an end-to-end, automated DevOps process.</p><h4>Why teams implement DevOps for Salesforce</h4><p>Salesforce is designed to make it easy for teams to add new capabilities and customizations directly to their orgs. For this reason, Salesforce teams have historically taken an in-org approach to development and releases on the platform. That is to say, teams add customizations directly to production orgs or develop new features in sandboxes and then deploy these features to production.</p><p>While this approach might be okay for small organizations with one or two developers who rarely make changes to their orgs, without a more robust set of DevOps processes, serious issues will start to arise quickly as business needs become more complex and development teams begin to grow. Without a good DevOps strategy, code changes can be overwritten, incomplete or untested features can find their way into production, and features that were previously working just fine can be inadvertently removed or replaced by earlier versions that are laden with defects. These issues can disrupt critical business processes and result in a loss of trust among business stakeholders. A robust set of DevOps policies and processes can dramatically reduce the risk of issues like these. And it’s never too early to start. Implementing a robust DevOps framework early, while development teams are still small, will help lay a strong foundation, which will improve scalability and reduce the need to retrofit practices with a much larger team that may not be as responsive to change.</p><h4>Assessing your DevOps maturity level</h4><p>The first step to progressing to a more mature level of Salesforce DevOps is to determine where your team’s current process is on the maturity spectrum.</p><p>At Gearset, the approach we typically take with customers starts with establishing a good understanding of each development team’s use cases, goals, and challenges. As we talk with teams, we gather additional details about their processes so we can advise them on the steps needed to improve their overall maturity. We open our discussions with questions like these:</p><ul><li>Can you describe your current DevOps strategy?</li><li>What DevOps processes do you already have in place?</li><li>Can you describe any relevant workflows (for example, Git branching strategies)?</li><li>Have you already adopted any tools to support your DevOps processes?</li><li>Do you have any specific performance targets (such as metrics for deployment times or release cadence)?</li><li>When was the last time a deployment went badly? Were you able to identify the root cause? If so, what was it?</li></ul><p>While we’re asking these questions, we also try to tease out the problems a team is facing by asking about the most significant bottlenecks, time sinks, and other pain points related to each item.</p><h4>DevOps maturity is a journey</h4><p>While the technical and <a href="https://gearset.com/blog/top-ten-business-benefits-of-salesforce-devops/">business benefits</a> of DevOps are clear, teams often find it difficult to decide where to start on their journey to a fully mature DevOps process. It’s best to take one step at a time. Partly this is to bring the team along with you. And partly it’s because DevOps tools and processes build on each other, so it’s useful to approach them in a sensible order. Here’s where a <a href="https://gearset.com/assets/resources/how-mature-is-your-salesforce-devops.pdf">maturity matrix</a> can help.</p><p>Every Salesforce team has its own way of working and will make different choices when integrating core elements of DevOps into an existing process. Some teams will embrace package-based application lifecycle management (ALM); others may not. Likewise, different Git branching strategies will work better for different teams. But successful teams all adopt core DevOps practices in a logical sequence. Using <a href="https://gearset.com/assets/resources/how-mature-is-your-salesforce-devops.pdf">Gearset’s maturity matrix</a>, architects can see what level of maturity their team is at and where they want to focus their efforts to mature further.</p><p>Any successful adoption of DevOps will need the whole team to be on board. Since DevOps empowers everyone and relies on a culture of close team collaboration, it also makes a lot of sense for teams to work through the maturity matrix together rather than having processes imposed from on high. Ultimately, this will help ensure the new practices stick and members of the team aren’t tempted to go back to an old, familiar way of working.</p><p>For additional information, check out the resources below:</p><ul><li><a href="https://gearset.com/assessment/">Gearset’s DevOps Assessment</a></li><li><a href="https://architect.salesforce.com/design/decision-guides/migrate-change">Migrating Changes</a></li><li><a href="https://architect.salesforce.com/deliver/#release-management">Release Management Resources</a></li><li><a href="https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models?trail_id=determine-which-application-lifecycle-management-model-is-right-for-you">Application Lifecycle and Development Models</a></li></ul><h4>About the Author</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*M3h1xpWzwUHjIHRi4lt3wg.png" /></figure><p><strong>Matt Dickens </strong>is<strong> </strong>Co-Founder and CPO at <a href="https://gearset.com/">Gearset</a>, the leading DevOps solution for Salesforce. Follow him on Twitter at <a href="https://twitter.com/DoubleDickens">@doubledickens</a> and follow Gearset at <a href="https://twitter.com/GearsetHQ">@gearsethq</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a240a9e425e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-architects/gearsets-approach-for-assessing-devops-maturity-a240a9e425e">Gearset’s Approach for Assessing DevOps Maturity</a> was originally published in <a href="https://medium.com/salesforce-architects">Salesforce Architects</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>