Learn how ServiceNow® DevOps Change Velocity helps your Development and Change Management teams accelerate change and connect their DevOps tool chain with ServiceNow so that the DevOps tool data can be used to automate change processes.

DevOps Change Velocity overview

DevOps Change Velocity collects data from your DevOps planning, coding, testing, and orchestration tool chain to provide visibility across the entire software delivery life cycle. This enables a single view for both the Development team and the Operations team across the end-to-end activities (plan, develop, build, test, deploy, and operate).

The DevOps Change Velocity application provides the following major benefits:
Change automation
Automate the change workflow and approval decisions to increase change velocity while ensuring governance and control. Create and complete DevOps change requests automatically and automate approval decisions based on input data (auto-approve, auto-reject or manually approve).
Change traceability
Track the progress of your work items, commits, artifacts, builds, and releases using the change requests to lend additional transparency and provide a single source of truth to all the personas involved.
DevOps Insights
View flow metrics, change acceleration metrics and other KPIs across the end-to-end software delivery value chain and connected tools.

To learn about the tools that the DevOps Change Velocity application supports, see DevOps Change Velocity integrations.

To understand how you can incrementally progress to get value faster using DevOps Change Velocity, see User journey for DevOps Change Velocity.

With DevOps Change Velocity, get visibility of DevOps changes from across the toolchain, automate change process, and measure performance.

Benefits of DevOps Change Velocity according to persona

PersonaChallengesDevOps Change Velocity benefits
Developer
  • Long feedback loop for change approval
  • Manual collection of data
  • Swivel chair (entering data in multiple interfaces) from changes to work items
  • Lack of end-to-end visibility of the entire DevOps life-cycle
  • Significant time spent on admin tasks
  • Automated data collection process through integrations
  • No time lost in manually creating a change request or providing evidence manually
  • More time for actual development work
  • Developers can keep working in their own tools
Change manager
  • Difficulty in handling an increasing number of changes
  • Not able to focus on only the changes that truly need human intervention
  • Manual work to respond to audit request
  • Significant time spent on gathering data
  • Accelerate change process with automated flows
  • Visibility over pipeline, tests, and change in a single tool
  • Automated documentation of change content and controls
  • Automate appropriate change governance driven by data
  • One-click audit response
Release manager
  • Lack of correlation between changes and release to measure progress
  • Unable to eliminate manual tasks from delivery processes
  • Enhanced visibility into the release plan and progress
  • Automation of more tasks with integrations
  • Improved release reliability
Application development leadership
  • Lack of visibility across teams and value streams
  • Lack of team performance comparison data
  • Inability to identify and resolve performance bottlenecks
  • Visibility into the entire value stream
  • Normalized views of team performance
  • Identify bottlenecks and take appropriate action
Operations and Support teams
  • Limited forecast and speed of remediation
  • Lack of visibility over change content and impact
  • Too many tools to correlate change, release, and incidents
  • Single tool to manage changes and incidents
  • Easier correlation between change and incident
  • Reduced Mean Time to Resolution (MTTR) from improved visibility
IT compliance officer
  • Limited visibility to ensure compliance
  • Lack of transparency of data and process to measure risks
  • Ensure compliance with automated change policy
  • Improved control and visibility with automated gathering of data

Explore more details such as the user adoption journey, supported integrations, and Insights in the following sections.