Productivity & controlling IT-costs
Measure & increase productivity
Quantitative Verfahren sind für jeden erfolgreichen IT-Prozess unverzichtbare Voraussetzung. Wie es die Industrie seit Jahrzehnten erfolgreich vorlebt, muss sich auch die Informatik bemühen,
Quantitative methods are an indispensable prerequisite for any successful IT process. As industry has successfully exemplified for decades, IT must also make an effort, to
- find key metrics for productivity & quality,
- systematically plan & control objective targets and
- systematically implement improvements based on the results.
We will support you during the introduction of a metrics system in your company. Functional metrics are recommended in the software industry. We are staffed with specialists in this area, who also have the necessary certification.
Ongoing assessment of the current situation – long-term success
Only the ongoing assessment of the current situation, especially with regard to the essential corporate goals of quality & productivity, ensures the long-term existence of a company. The crucial question is whether IT is still able to control the ever-increasing complexity in the economy.
Benchmarking has emerged as an indispensable tool in this context:
- we assist you in comparing your company with other successful companies; the goal is to determine where you stand & to come up with a list of improvement measures.
- we provide you with support in finding reference data, performing the analysis and developing & implementing the improvement measures.
- we offer comprehensive expertise in the selection & interpretation of benchmarking data & guide you to optimizations with an orderly process at appropriate time intervals.
Rules of thumb for quality & productivity in IT
The following rules of thumb & guidance values are derived from a condensation of all our previous studies. They should therefore not be used for active decisions in individual cases, but they are suitable for passive plausibility checks of statements:
- average productivity in the branch of IT: 15 FP/PM
- number of employees required (headcount) during the development project: number of FP divided by 150-200
- number of employees for maintenance: number of FP divided by 500
- scope creep & change request: number of FP increases by approx. 2% per calendar month of project runtime
- one test level detects only 30% of the bugs, 70% are carried forward
- effort for test
- writing a test case: 30 min
- executing a test case: 20 min
- writing a test case: 30 min
- every time 10 errors have to be corrected, 1 new error is induced (“bad fix”)
- defect costs: The effort required to correct errors increases exponentially. The sooner a defect is found, the better it is. Inspection (1 h correction effort per defect found), unit test (2.5 h), acceptance test (10 h), production (> 50 h).
