Change completeness – Updated Solution Documentation and Operation Handbook
% incidents with Priority 1/2 that are caused by missing or wrong solution documentation change or operations handbook (m)
Change completeness - test case adjustment with change request / implementation and transport/ E2E processes
% test cases reviewed or changes (after identification of affected ones) (m)
8
Standard Metrics for BC: Managed Integration Area
Mission
Challenge
New product incidents
Metric
# incidents with priority 1/2 after go-live of new products / technologies within first 3 months (m) Coverage of product trainings sessions for end users (m)
New product skills assessed Managed Integration
Mainstream new products / technologies
Ratio of incidents identified as training issues (m) Coverage of product trainings sessions for IT staff (m)
# critical business processes steps tested for performance regularly (m) # of MRP updates documented per annum (m) MRP update documented per SAP Release Strategy update (m)
11
Standard Metrics for POI: Development Management Area
Mission
Challenge
Metric % of incidents (prio 1/2 ) caused by custom developments (m)
Custom development stability
Upgrade change impact analysis
Custom code clearing
Development Management
Custom development standards
Custom development documentation
Custom development standards
Custom development documentation
Ratio of completed analysis projects in Upgrade Change Impact Analysis (m) Ratio of completed analysis projects in Custom Code Clearing (m) ratio of incidents caused by custom development (a) Level of clear development standards documented (m) # development projects without review of development standard compliance (m) % custom developments documented according to SAP Standard (Sol. Documentation for Custom Development) (m) % of custom code objects not compliant to documentation standard (m)
ICC
Reduce modification
% of custom code objects reviewed incl. documentation standard (m) % of reduction of unnecessary modifications (m)
Metric Ratio of profile changes for users in one year (m) Distance to implemented security note from released security note (m) # incidents caused by not implemented security notes (m) % security reviews vs new releases (m) # reviews of assigned roles vs. actual requirements (m) # infrastructure assessment per annum (m)
# alignment meetings (m)
Ratio of changes in standards/policies leading to IT reviews (m)
13
Standard Metrics for POI: Project Control Area
Mission
Challenge
Quality Gates Defined Managed quality gates Quality Gate Criteria Project Control
Metric
% projects with quality gates defined (m) % of quality gates passed by 1st attempt (m) # of criteria defined for each quality gate (m) # of quality gates passed by mgmt. decision (m) # incidents caused by ignored quality gates (m)
Integrated partners
Risk Management of Partners
Alignment meetings/ Participation in risk mitigation reviews
Established Project Methodology
Project Methodology aligned
% projects executed according to project methodology (m)
