Velocity

Velocity metrics identify how much new and updated functionality is being delivered into your SAP systems, by reviewing the number of transports and changes being deployed.

Velocity measures how much work has been done in a given time period. In the context of DevAnalytics, that means it’s a measure of the amount of change that is actually making it to QA and production – and hence to testers and end users – in the time period that you choose to monitor.

Velocity is a clear measure of how much work has actually been finished, regardless of how efficiently that work was carried out. It’s important during development planning as it provides a guide to the work that teams might realistically complete in each phase based on past performance.

Velocity is higher as the number of changes deployed increases and is lower when the deployment rate reduces.

DevAnalytics provides 12 velocity metrics:

• Deployments – Total (Transports) = The total number of transport deployments into each target system on any selected date
• Deployments – Success (Transports) = The total number of successful transport deployments into each target system on any selected date.
• Deployments – Error (Transports) = The total number of transport deployments in error into each target system on any selected date.
• Deployments – Percentage in error (Transports) = The percentage of transport deployments in error on any selected date.
• Deployments – Total tasks (Tasks) = The total number of task deployments into each target system on any selected date.
  A task is considered to be deployed if any of its component transports have been deployed. For example, If a task has transports that have been imported into 3 different target systems on a specific date this will count as 3 task deployments.
• Deployments – Success tasks (Tasks) = The total number of successful task deployments into each target system on any selected date.
• Deployments – Error (Tasks) = The total number of task deployments in error into each target system on any selected date.
• Deployments – Percentage in error (Tasks) = The percentage of task deployments in error on any selected date.
• Deployments – Emergency (Tasks) = The total number of emergency task deployments into each target system on any selected date. A task is considered to be an emergency if it’s priority is set to Emergency / Urgent.
• Deployments – Emergency percentage (Tasks) = The percentage of emergency task deployments on any selected date.
• Users involved in unreleased transports (Average) = The average number of users with transports that are unreleased on any selected date including sub-task users.
• Users releasing transports (Average) = The average number of users releasing transports on any selected date.