hello welcome to this video about devops change velocity today I'll be covering the devops change velocity adoption Journey I'll be covering the path that customers typically take when adopting devops change velocity and the value that can be achieved at each maturity step the steps all cover are connecting with third party tools to import devops data attaching this data to change requests automatically creating change requests both with and without pausing your pipeline and automating change approval using policies let's jump in the first step in the adoption journey is to connect with your devops tools and start collecting data by connecting with the cicd tools that your teams are leveraging you get insight into the data they are producing this includes planning tools such as jira or service now SPM coding tools such as GitHub orchestration tools such as Jenkins quality scanning tools such as sonar Cube and tools that cover the full spectrum such as a Zer devops the devops change velocity application contains apis that make connecting with and importing data from these tools easy after importing all of your devops data from all of your different tools is normalized on a single data model within the service now platform additionally after connecting with tools data begins to flow into your insights dashboard which provides useful metrics such as door metrics flow metrics and operational metrics that give insight into how well the adoption of devops is going and what benefits you are getting from this adoption the second step is what we call change traceability now that you have data flowing into the dashboard you can connect this data to your change requests this gives Insight or visibility into the change itself such as Associated work items test results or software quality scans all of this information is typically manually added to the change descriptions but now we have this information directly on the change request and if we need additional information we can click into it to get additional details the key of this step is while you're collecting data and associating it to a change you're not altering your existing change process at all you're simply enhancing your change records with more data so with these first two steps we've added visibility into the data connected to your changes without any modification to your existing processes or a heavy lift on setting up these tools this alone is a huge value to your change teams now with step three we move Beyond visibility into autom this process we'll begin with automating the change registration process in this step our change requests are automatically created and the data on them automatically filled out in a consistent manner the key here is that while change requests are automatically created they do not stop the pipeline to wait for authorization of these changes that's why we refer to this step as change receipts we are not using it to enforce any approval policies or the automate authorization instead we're automatically creating change changes and adding receipts for each change so the change team or Auditors have a consistent view of information tied to each change request our next step is an interim step before moving on the full change automation now in step four instead of the change request being created and then returning immediately to the pipelines control to continue we will now hold this change until it reaches the implementation State our change request will remain in the authorized stage and our pipeline will not continue until the change has been manually approved once again we still haven't applied any policies but now after automatically creating a change the pipeline stops to wait for manual approval the final step in this process is to move the full change automation this is where we leverage the data not only for visibility and consistency but also for connecting the policies that have been defined within service now this allows for the authorization of the change to happen automatically policies are standard part of service now's change management application they take inputs such as code coverage test results or security scans to determine if a change should be automatically accepted rejected or flagged for manual review the level at which you automate is completely up to you and the policies that you've created within your organization this final step is where we found organizations have the most difficulty particularly when trying to scale creating change approval policies is technically not hard to do but to do so requires collaboration and often this collaboration is across different teams within your organization while this step is the largest lift it also often provides the largest benefit for many organizations that we've worked with full change automation has turned a process that typically takes days or even a week to complete to one that takes a few minutes to run through the process and now you've seen how companies like yours can get started with service now's devops change velocity while full change automation is the ultimate goal you can achieve value at each step in the maturity Journey to get started all you need to do is activate the devops change aost the application and start connecting your tools for additional support please check out the devops Community page where we have other helpful videos blogs and resources