in reply to (OT) Proving Productivity?
I have no actual experience in this matter so take what I say with a grain of salt. Anyways, it seems in this case the only metric should be 'time to completion', as in, "With this feature set and this language etc etc, it will take me 6 months to complete it". But I have to admit I have no real idea on how to translate that in to a day by day metric. Perhaps saying "I have 50% of the code implemented 3 months in" or something might help, but that sounds.. tricky. Of course this sort of ties in with the .. fluid .. requirement list as you can just say "adding this feature will take an additional two months" or something and keep a running total.
|