Rework

Rework metrics measure the efficiency of your development and delivery processes, and can highlight bottlenecks and cost caused by inferior quality.

It’s not often that an SAP change makes its way from development to production at the first attempt. That may be understandable given the complexity of many systems and the high level of interdependency that may exist between different transports, but rework is a significant drain on resources.

Insight into levels of rework provides perhaps the clearest guide as to how you can optimise delivery of SAP change. Reducing rework means you can deliver faster, increase the volume of change that makes its way to production, and lower development and QA costs. You may even manage all three.

Rework is essentially a measure of the number of additional cycles it takes to deliver changes to completion. For example, a perfect change deployment would be done in one cycle. If a change failed testing twice before completion then that would add two rework cycles giving a total of three cycles to completion. In essence when a change has gone backwards and forwards in the change life cycle from development through to another system further in the path, it will evaluate the cycles and see how many times its gone through the delivery to deployment phase.

DevAnalytics provides 5 rework metrics:

• Cycles from DEV to QA – Average (Tasks) = The average number of cycles from Development to QA for tasks. A cycle represents the deployment of all the transports for a task into QA for testing. Each time there is a test failure another development cycle will be required to fix it. More than 1 cycle indicates a rework.
• Percentage of business tasks with reworks from DEV to QA = The percentage of tasks with more than 1 cycle from Development to QA indicating that there were reworks.
• Cycles from DEV to PROD – Average (Tasks) = The average number of cycles from Development to Production for tasks. A cycle represents the deployment of all the transports for a task into Production. Each time there is a Production failure another development cycle will be required to fix it. More than 1 cycle indicates a rework.
• Percentage of business tasks with reworks from DEV to PROD = The percentage of tasks with more than 1 cycle from Development to Production indicating that there were reworks.
• First pass percentage in QA (Tasks) = The percentage of tasks with only 1 cycle from Development to QA indicating that there no were reworks.