--- sourceDocument: Australia IT Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-service-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Service Management ft:clusterId : - itsm bundleId : - itsm workflow : - Technology --- # User journey # User journey for DevOps Change Velocity {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of User journey for DevOps Change Velocity The DevOps Change Velocity application enables ServiceNow customers to automate and accelerate change approvals through a phased implementation approach. This approach follows four progressive stages---crawl, walk, run, fly---that gradually increase automation and efficiency in change management tied to DevOps pipelines. Customers can start small and build toward fully automated change request creation and approvals integrated with their Continuous Integration (CI) and Continuous Deployment (CD) tools. Show full answer Show less ## Phased Implementation Approach * **Connect Tools and Applications:** Begin by integrating key DevOps tools with ServiceNow and selecting important objects to track. This phase requires no modifications to existing pipelines or development assets and is essential for bringing tool data into the ServiceNow AI Platform. It also involves creating DevOps Apps for onboarding teams. * **Change Traceability:** With tool integration established, relevant DevOps data such as stories, code commits, test results, and quality scans flow into ServiceNow. Users continue using existing change processes but benefit from automated population of key change request information, saving time and improving accuracy. * **Change Registration:** This phase automates creation of change requests directly from CI/CD pipelines, requiring pipeline adjustments. Automating this step reduces manual effort and human error by developers, streamlining the change registration process. * **Change Automation:** The final phase enables real-time data flow, automated change request creation, and automated approval or rejection decisions based on data-driven policies. Establishing policy guidelines here supports risk reduction and accelerates successful change rates. ## Key Outcomes By progressing through these phases, ServiceNow customers can: * Integrate DevOps tools seamlessly into change management without disrupting current workflows initially. * Enhance visibility and traceability of changes with automated data enrichment. * Reduce manual workload and errors by automating change request creation from pipelines. * Achieve fully automated, policy-driven change approvals to increase deployment velocity and reduce risk. * Utilize Insights dashboards throughout to monitor operational efficiency and growth in development processes. Review the adoption journey of the DevOps Change Velocity application to enable a phased (crawl, walk, run, fly) approach toward complete automation of change approvals. While automating change request creation from the Continuous Integration (CI) and Continuous Deployment (CD) pipelines and automatically approving them will be your end goals with DevOps Change Velocity, you can approach your implementation in this phased manner. Each phase here provides incremental value over the previous phase and enables you to get started with minimum changes to your existing processes: 1. Connect Tools and Applications: Get started by integrating your key DevOps tools and choosing the key objects from these tools to track. This can be done without needing to modify your pipelines or any of the development assets. And then create DevOps Apps for the teams that you want to onboard first. Completing this phase is necessary to bring data from your tools over to the ServiceNow AI Platform. For more information on integrating tools, see [Integrating DevOps Change Velocity with third party tools](https://www.servicenow.com/docs/pViQYW50q3XmI0CgMeO7rA "Integrate your orchestration, planning, coding, artifact, software quality, and security tools with DevOps Change Velocity for end to end change traceability and automation."). 2. Change traceability: After you have established integration with your key DevOps tools, relevant data from these tools will start coming into ServiceNow. Then you can continue to use your existing process to create changes but save time by having all relevant information added to the change request with just a few clicks. This information includes stories, code commits, test results, quality scans, and others. For more information on modeling a change request flow, see [Customizing DevOps flows](https://www.servicenow.com/docs/qL5ZkK2bE2766F_f0ltR7w "Customize or recreate the DevOps Change Request Manual Approval, DevOps Change Request Minimal Automation Approval, and DevOps Change Request Advanced Automation Approval flows based on your requirements using a flow or a script."). After these two phases are completed, you can progress toward the next two phases, which help you achieve automation of your change process, accelerate deployments, and increase velocity. You can start your implementation with these two phases as they don't need any changes to your existing processes or pipelines. 3. Change registration: This phase builds value further by automating the change request creation from the CI/CD pipelines. With this phase you'll need to modify the team's CI/CD pipeline to enable automatic creation of change requests. This automation saves the time of your developers as they don't have to manually fill the change requests, which reduces the risk of human error. For more information, see [Configuring DevOps change request details within the pipeline](https://www.servicenow.com/docs/JrPZPSHCjQRzCnCP7jFB5Q "Configure how the closure information, change state, and change request fields are updated from within a pipeline in the change step of the pipeline."). 4. Change automation: This is the final phase in value realization where data from the tools will come into ServiceNow in real-time, change requests will be automatically created and automatically approved or rejected based on data driven policies. This phase requires creating policy guidelines and enabling automated change approvals decisions based on input data to reduce risk and increase the rate of change success. For more information, see [Accelerating your DevOps change process](https://www.servicenow.com/docs/1IOGCXHTnX02RprvPaB2wg "Enable the change acceleration feature of DevOps Change Velocity for automatic change request creation in your pipeline, and use change approval flows and policies to automate approval under certain conditions."). {#user-journey-in-devops-change-velocity__ul_rbq_q44_pvb} All through these four phases, the Insights dashboards help you analyze operational and business reports and to determine the overall efficiency  and growth of your  development processes.