Hi Group. WBS RP Draft.

here are some comments.

Presumably this document is meant to fit in a series of Breakdown Structure documents of which Organisation and Risk (OBS & RBS) have already been published. There are numerous other project breakdown structures within a project - contract, estimate, resource, cost, BoQ, scope, financial, requirements, documentation quality, - all of which provide a different view of the project. Each one is worthy of a separate RP. As the WBS is the overriding document it should be stand alone and reference in the text to just Contract BS seems out of place. 

I have found that coding WBS levels with leading 00's gives most software problems.

The key identifier and driver to the WBS should be that at some level (5) in its structure all the other project breakdown structures should be brought together and integrated into a series of documents - The WBS Dictionary. This section is seriously underplayed. If used correctly these documents, collectively, define all aspects of the project and are produced by the Project Control Team as and when required by the schedule and can be used as a measure of project progress. I attach a proforma (called a Internal Works Order) which I have used successfully on projects and is a great control document. Using this an instruction to the Work Package Manager from the Project Manager clearly lists all relevant information required to undertake a particular work scope element. If you cannot fill out an item in this document you have a problem BEFORE you start the work.