It can look like repetitive, but I come again with the same question from here about WBS and planning deliverables.
I was "advised" in a meeting recently to include a planning deliverable leg. And a WBS deliverable at n-level if I want to measure time, cost, tasks and resources later.
As far as I know, WBS is equals to Scope of the project. Schedule are the activities to produce a deliverable, thus there is a strong relation between both. A block of activities that are not related to a deliverable it may be wrong and should be included in or update the WBS.
As far as we are in the planning phase of the project, there is no problem to update the WBS. In the contrary, if WBS got approved, the only way to update it is through a formal change process.
Should I include a WBS deliverable at n-level within my Planning leg of my global WBS in the early stages of the project? (Let's say when the project team is building it with post-it notes).
I know that it is an error to include SO MUCH DETAILS in the WBS or activities as long as we can measure progress and fulfill with the objective of the deliverable and get the success of the project.
I am curious about what would be your suggestions to include the WBS deliverable within the WBS "graphically". How do you deal with this. Any examples? Or your deliverable would be scope statement directly?
EDIT: Scope baseline = Scope statement + WBS + WBS dictionnary.