I would prefer to measure developers by inverting the cost of maintenance.

I don't want maintenance programmers to be productive, I want them to 
be whithout anything to do !  ;)

_____________________________________________________________
Thomas Berg   Specialist   IT Utveckling   Swedbank AB (Publ) 


> -----Ursprungligt meddelande-----
> Från: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] För Ted MacNEIL
> Skickat: den 21 december 2007 17:55
> Till: [email protected]
> Ämne: Re: Developer productivity
> 
> >If anyone has worked in a company that has
> successfully measured developer productivity I'd be 
> interested in how they did the measurement.
> 
> I don't know how successful it was, but years ago we used 
> function points.
> Rather than counting lines of code, we would count new 
> functionality (or modified function).
> 
> In OOP, I think it would be the equivalent of delivering a 
> new object and/or method.
> 
> But, how do you measure the productivity of maintenance programmers?
> 
> -
> Too busy driving to stop for gas!
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
> 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to