Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!mips!apple!netcomsv!jls
From: jls@netcom.COM (Jim Showalter)
Newsgroups: comp.software-eng
Subject: Re: use of metrics
Message-ID: <1991Jun7.074226.12105@netcom.COM>
Date: 7 Jun 91 07:42:26 GMT
Article-I.D.: netcom.1991Jun7.074226.12105
References: <795@tivoli.UUCP> <35121@mimsy.umd.edu> <4794.284cfad3@iccgcc.decnet.ab.com> <35346@mimsy.umd.edu>
Organization: Netcom - Online Communication Services  UNIX System {408 241-9760 guest}
Lines: 25

>Surely the manager knows from previous experience who
>meets deadlines, meets expectations, produces work that doesn't need to be
>redone, etc.

These are all metrics! Every single one of these could be measured,
calibrated, quantified, etc. I think people do this sort of metric
compilation constantly--it's just when someone talksabout making
the process explicit that people claim it can't be done.

>Lines of code for productivity?  Hey, blank lines!
>Effort to effect repair of a bug?  Hey, low-ball it!  Time spent on the 
>computer?  Uh, two or three runs, a few seconds, yeah!  Effort charged to
>the project?  What, you mean all those night hours I put in fixing my 
>screwups?  forget it!

The above assumes that metrics can only be gathered by asking people
to compile them for you. This is, I think, the WORST way to acquire
metrics data, since it puts humans--with all their bias, subjectivity,
and defensiveness--into the loop. Every item listed above could be
acquired automaically with relatively simple tools.
-- 
**************** JIM SHOWALTER, jls@netcom.com, (408) 243-0630 ****************
*Proven solutions to software problems. Consulting and training on all aspects*
*of software development. Management/process/methodology. Architecture/design/*
*reuse. Quality/productivity. Risk reduction. EFFECTIVE OO usage. Ada/C++.    *