Everyone complains about how many non-value add activites are in their Software Development Method - but how do you actually measure it? It's a truism that you can't manage what you can't measure so surely you really ahve to measure this.
Here's my proposal.
How much documentation would be required to deliver
"Hello World"?
Are we talking a few pages, a stack a few centimetres tall, inches, feet, kilos? Remember this is everything it takes to get it from a twinkle in a stakeholders eye to supported in production. Business cases, support plans, test reports, meeting minutes. Everything - and no "small project" exemption because they're often more trouble than they're worth.
We could even classify methods by their order of Magnitude.
Scrum and XP are probably around a centimetre of docs. User stories and Index cards are pretty thick after all.
The IEEE standards are definetly into the inches
My own company is probably a little over an inch - but we're quite disciplined about trimming it down to match for the situation
RUP is definetly a few inches
I assume military projects would be into the kilos
Posts
No comments:
Post a Comment