TheRemover
Newbie
- Nov 30, 2017
- 52
- 108
- 159
I applaud your effort, but at the same time I can't feel too hopeful many people will actually understand, or want to understand in the first place. The issues are blindingly obvious to anyone with development experience, and completely incomprehensible and irrelevant to anyone without. People have been saying for months minimum that the tasks are not created equal and yet this simple bit of information eludes a lot of the people in this thread. Sometimes people just want to complain and you're not going to convince them their complaints aren't the most factually correct thing since Galileo uttered his famous quote.That's exactly what I meant when I said that splitting the remaining tasks was a BAD idea (unless also the same was done also for completed tasks - obvioulsy a waste of time).
I try to develop the example that another user posted above.
The same amount of work remaining, but the percentage drops.
- Let's say we have 100 tasks. 84 are completed, so the progress is 84%
- 16 task are remaining, not homogeneous in terms of effort.
- 8 out of 16 tasks are huge, and have to be split each one in 4 subtasks -> 32 tasks resulting, representing the same work to be done
- 5 out of 16 tasks are big but not huge, and are split in 2 subtasks -> 10 more tasks resulting, representing the same work to be done
- 3 out of 16 are small tasks and don't need to be split
- Totally we have 32 + 10 + 3 = 45 tasks to be done
- Previously we had 84/100 done -> 84%. Now we have 84/(84+45) -> 84/129 -> 65.11%
As for the actual splitting, honestly, good decision made way too late. Big tasks complicate development and make it appear more sluggish than it is. But we'll have another influx of tasks (and resulting percentage decrease) anyway when the new version is "complete", testing starts, and the bug tickets come flooding in. I foresee a similar rash of complaints and crying from people who, again, have never developed anything in an organized fashion in their lives.