Re: cobol code assessment
- From: Louis Krupp <lkrupp@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 28 Jan 2006 22:44:37 -0700
HeyBub wrote: [snip]
Be sure to include the "skill inventory" of the staff. For example:
Average experience Senior programmers - 12. COBOL: 17.2 years Assembly: 3.3 years JAVA: 0.4 years RPG: 0.3 years FORTRAN: 0.1 years Other (all): 0.3 years
Junior programmers - 4. COBOL: 2.6 years Assembly: 0.2 years JAVA: 0.6 years
etc.
With a view toward emphasizing the human investment in the existing methodology.
Slightly OT, but is average experience necessarily a meaningful metric? Are ten people who can claim a year each of COBOL experience really equivalent to one person who can claim ten years, or two people who can claim five each? Is ten years' experience worth twice as much as five years, or is there a point of diminishing returns?
This question calls for some handwaving: I would sum a*log(b*e + 1) over the whole team, where 'e' is years of experience and 'a' and 'b' are constants of your choice, and use the result as a measure of available skill. 'a' and 'b' could be different for different skills; for years spent writing spaghetti COBOL with ALTER statements or FORTRAN with arithmetic IFs and Hollerith editing descriptors, 'b' could be very small or even zero while 'a' could be zero or even negative.
(That's what happens when I drink coffee.)
Louis .
- Follow-Ups:
- Re: cobol code assessment
- From: HeyBub
- Re: cobol code assessment
- From: Alistair
- Re: cobol code assessment
- From:
- Re: cobol code assessment
- References:
- cobol code assessment
- From: apple.time@xxxxxxxxx
- Re: cobol code assessment
- From: Alistair
- Re: cobol code assessment
- From: HeyBub
- cobol code assessment
- Prev by Date: Re: cobol code assessment
- Next by Date: Re: cobol code assessment
- Previous by thread: Re: cobol code assessment
- Next by thread: Re: cobol code assessment
- Index(es):
Relevant Pages
|