     |
|
|
|
|
|
|
Sneak preview:
If you don't measure and
control maintenance effort, it will grow more than necessary. One great
risk is that work not allocated during more strictly controlled new development
projects will be hidden in maintenance endeavors. This is why one of the
biggest commercial banks in Finland began to collect development and maintenance
effort data as early as 1985. Every employee, including managers and secretaries,
reported time spent on all types of projects into an effort accounting
system every week.
...In order to improve the
annual budgeting of maintenance effort, both for the in-house maintenance
suppliers and the owners of the applications, Pekka Forselius and his team
collected a large amount of data including actual effort, size, age, defects,
classification variables and risk factors to help them to better understand
the qualitative differences among applications. This data was simply used
to help organize maintenance and manage risks, it was not statistically
analyzed at the time.
What could the bank have learned through the statistical analysis of this rich data set?
Also of interest:
Benchmark
your Software Development Productivity Online
Read
my Software Development Productivity Benchmarking Papers
Software
Metrics Research
 |
Applied Statistics
for Software Managers is the first complete guide to using statistical
techniques to solve specific software development and maintenance problems.
You don't need a mathematical background: Katrina Maxwell
presents an easy-to-follow methodology and detailed case studies that show
you exactly how to assess productivity, time to market, development effort
and maintenance cost drivers.
Book includes real software development and maintenance data from one bank. |