Xref: utzoo comp.software-eng:2451 comp.misc:7423 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!samsung!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!jato!mars!baalke From: baalke@mars.jpl.nasa.gov (Ron Baalke) Newsgroups: comp.software-eng,comp.misc Subject: Re: Programmer productivity Message-ID: <2226@jato.Jpl.Nasa.Gov> Date: 20 Nov 89 20:22:15 GMT References: <34796@regenmeister.uucp> Sender: news@jato.Jpl.Nasa.Gov Reply-To: baalke@mars.UUCP (Ron Baalke) Distribution: na Organization: Jet Propulsion Laboratory, Pasadena, CA. Lines: 18 >From article , by emuleomo@paul.rutgers.edu (Emuleomo): >> I heard that the average programmer produces 3-4 lines of *finished* >> code a day! >> This sounds ridiculously low. Does anybody out there know what the real >> figure is? Or is it misleading to try and gauge productivity this way? >> If it is, what are the recommended ways to measure programmer productivity >> using some sort of metrics! Well, it is low if you count only the coding phase of the software development. The coding phase takes up only 10% of the entire software cycle. If you include to time to write the requirements, design, code, parameter & assembly test, integration and final testing, then the lines/day that a programmer produces is not low. Ron Baalke | baalke@mars.jpl.nasa.gov Jet Propulsion Lab M/S 301-355 | baalke@jems.jpl.nasa.gov 4800 Oak Grove Dr. | Pasadena, CA 91109 |