About 15 years ago, I spent a bunch of time looking at this problem. I also did a presentation at Common about it. At that time, no system of measurement produced better fidelity than lines of code (LOC). LOC is flawed because its scope is narrow and its definition contains serious flaws. In order to heal the definition problem, one must account for the effect of complexity on LOC. Richard Jackson Richard Jackson and Associates Ltd. IBM Business Partner mailto:firstname.lastname@example.org http://www.richardjacksonltd.com Telephone: 1 (303) 808-8058 -|-----Original Message----- -|From: email@example.com -|[mailto:firstname.lastname@example.org]On Behalf Of Gary R. Patterson -|Sent: Friday, November 10, 2000 2:36 AM -|To: MIDRANGE-L@midrange.com -|Subject: RE: programmer productivity. -| -| -|Lots of ways to measure programmer productivity. A few ideas: -| -|Developers: Lines of code vs. defects in produced code. -|Developers: Performance to project timelines vs. defects. -|Developers: Performance to task estimate vs. defects. Really needs -|standardized estimates. -|Maintenance programmers: Number of fixes (weighted for complexity) vs. -|defects in fixed code. -| -|Subjective measurements, too: Code review, standards compliance, peer and -|supervisor performance evaluation. -| -|Of course, you have to measure non-coding tasks, too. Some of the above -|metrics apply. -| -|1) Start tracking defects, and charge them to the responsible -|individual or -|team. (Have security walk you to the car for the first week or two.) -|2) Implement detailed time reporting. (Watch out for mail that ticks.) -|3) Implement code reviews (good idea anyway). Standard criteria, rotating -|responsibility. Check for standards compliance. (This way you -|can share a -|little of the heat with your senior staff.) -|4) Implement an estimating methodology. (Big fun. Nothing like a rousing -|afternoon of function-point counting.) -|5) Start tracking performance to estimate and performance to timeline. -|(Avoid food and beverages that are not prepared in your presence.) -| -|Enjoy. Might actually even improve productivity and quality, if you can -|manage it effectively. -| -|Gary R. Patterson -| -| -| -|-----Original Message----- -|From: email@example.com -|[mailto:firstname.lastname@example.org]On Behalf Of midrange -|Sent: Thursday, November 09, 2000 1:29 PM -|To: MIDRANGE-L@midrange.com -|Subject: Re: programmer productivity. -| -| -|I have been ask by accountants to provide them with a way to measure our -|programmers productivity. -| -| -|I know what I think is productive. fast accurate turnaround on projects. -| -|does anyone one else have any comments. -| -|thank you jeff grace -| -|+--- -|| This is the Midrange System Mailing List! -|| To submit a new message, send your mail to MIDRANGE-L@midrange.com. -|| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. -|| To unsubscribe from this list send email to -|MIDRANGE-L-UNSUB@midrange.com. -|| Questions should be directed to the list owner/operator: -|email@example.com -|+--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.