laziness, impatience, and hubris | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Productivity should be measured in terms of deliverables. A deliverable is a black box that satisfies a set of requirements (either from a requirements document or the design document based on those requirements) and is completed to a certain degree of error-free-ness by a certain date. Either you produced or you didn't.
Now, a deliverable can be an entire application or a small function. It can satisfy 100 requirements or part of 1. It can be a customer deliverable or an internal deliverable. The reason I think in terms of deliverables is that LOC has nothing to do with the real world. For example, I write code differently depending on a huge number of factors:
However, if I can provide a deliverable in the time allotted that satisfies the requirements stated and is 99.999% error-free, I have succeeded. If I cannot, I have failed. Remember, you can't be 80% pregnant. Likewise, you can't be 80% productive. Either you produced or you didn't. ------ The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6 Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified. In reply to Re: Proving Productivity?
by dragonchild
|
|