Originally Posted by jaurk
It's not useless for me, or the majority of the people who've responded it, here on the forums.
|
I see, I will try to explain this for those who aren't educated in software programming.
What you have here is the full project (let's call it X) needs to be done.
What is done here (on the wiki), is divide it into smaller parts like so:
Now, you only have
more unknown variables and more confusion!
What we do in software programming, is to introduce a
measurement tool. Many of you might think this would be hours, and you are correct that it is used sometimes. It could also be complexity points or even percentage points .
For this project, the optimal way to measure anything, would be in
complexity points, saying X/A is a 5 point assignment, but X/B is harder, so it's a 10 point assignment.
This helps in the sense that after X/A is completed, you know what to expect from X/B and the rest who are assigned points.
For those educated in Scrum, I'm of course referring to X/A,X/B, etc. as User Stories.
What this "status update" introduced was simply more unknown variables, nothing else. You shouldn't have to be educated to see that.
--------------------------------------------------
Simplified since people still aren't fully understanding
--------------------------------------------------
Example - Building a car:
Assignment A - Done!
Assignment B - Done!
Assignment C - 50% Done!
Assignment D - Not started.
Now the above looks like it's well over 50% done right? Like our car is almost finished!
Now let's say there were descriptions of the tasks:
Assignment A - Mount left wheel
Assignment B - Mount right wheel
Assignment C - Install Radio
Assignment D - Mount engine, carburator, and all other things.
Now it doesn't look 50% finished does it?
What would give a good image of progress is to use previously mentioned complexity points (or hours or percentage points), like so:
Assignment A - 3 points
Assignment B - 3 points
Assignment C - 1 point
Assignment D - 40 points