The WBS and associated work descriptions should
be easy to understand
Do not arbitrarily subdivide work to the
lowest possible level, but the lowest level should
have about the same level of effort
(80-hour rule).
The WBS can act as a hierarchy of discrete,
measurable milestones so that everyone can tell when
a task should start and when
it should end.
Tasks should have clearly defined start and
end dates. You should be able to construct a schedule
or activity diagram
from the
tasks on the WBS.
Different projects have different WBS.
Although WBS templates are good, and no one wants
to reinvent the wheel, it
is very important for team building to involve
the planning team
in the creation and approval of the WBS.
