The concept of the balanced score card (BSC) has been around for a long time now, and of course has perpetuated the now growing fields of performance management and analytics. But can that same concept be applied to more technical areas?
That's the question SAP's Veit Eska and Oliver Kapaun sought to answer regarding the new Custom Code Lifecycle Management (CCLM) in Solution Manager 7.1. Veit and Oliver introduced CCLM in a Solution Manager Expert article last year, noting that its functionality allows you to monitor custom developments in your system. Since custom developments are company assets -- and are ever growing -- it's important to try to monitor and analyze them.
In their latest article, they combine these two concepts by introducing readers to the custom code score card (CCSC):
The CCSC follows the CCLM vision and the data is derived from the reporting functionality of the CCLM application. All three levels of the pyramid presented in Figure 1 are taken into account. The following overview shows the necessary figures and a derived final score on the top level:
1. Life cycle management for best-run customization
- Score (calculated from second and third level)
2. Control and ownership level
- Custom code objects with or without a contract
- Custom code objects with or without an owner
3. Transparency and awareness
- Number of development classes
- Number of custom code objects
- Severity level (enhancements and modifications)
- Quality (high, medium, or low)
- Version inconsistencies
- Usage in productive systems
The overall final score is calculated at the top and based on the lower levels of two and three, which represent governance figures and the figures of control of custom developments.
For the full article, "Improve Custom Code Life Cycle Decision Making and Governance with the Custom Code Score Card," Solution Manager Expert subscribers can go
here. For more information about Solution Manager Expert, go here.