Alan GosiengfiaoSenior Managing Consultant| IBMTaguig City, Philippines
When moving from scope to schedule, we typically link activities to work packages. I follow that as a rule but never quite understood why we are NOT allowed to assign the integration activities to a higher node in the hierarchy (eg. a control account). So I limit myself to a work package or create a totally different branch for integration activities.
Can someone please explain with a good example? Saving Changes...
I've never strived to have my WBS charts be perfectly balanced so I have had cases where integration type activities hung directly off a main component control account which also had a few branches representing the decomposition of the sub-components of the control account.
This approach also facilitates mapping the WBS into a scheduling tool.
If I understood your question, you asking to link the activities (lowest node) to the third node of control account (without passing to the second node working package).
Because the work package (the lowest level of WBS) which obtained at create WBS (5.4 process) is further decomposed by defining activities at process (6.2 process- node 1)
then node1 (link to node 2 = work package ) then (node 2 link to node 3= control account)
Please do not forget the statement which saying " work package may be associated with ONLY one (single) control account" rather than associated with activities.
BR,
Mansour Saving Changes...
