|
|
|
|
|
|
|
|
Size Does Matter
Having a task number list that is too big can be worse than a task number list that is too small.
You need enough task codes to control the project. If you have too many task codes, it becomes burdonsome to fill in timesheets, etc., and the task codes will eventually be ignored. If the costs are not captured in the correct task numbers, project controls is impossible.
More is not necessarily better, you need just enough task codes to control the project, and not too many that the cost control is ignored.
If the project team wants to go down to a lower level of detail with the task numbers, ask what purpose would it serve? And remember, the more detailed the task number list, the more difficult and time consuming (read expensive) it is going to be for everyone who uses it, the more errors there are going to be, and the closer you are going to get to the "give up" threshold and the project team just ignores it.
The KISS principle (Keep It Simple Stupid) definitely applies to constructing a task number (WBS) list for a project.
|
|
|
|
|
