In addition to ensuring 100% of the project is contained in the WBS, it is just as important to exclude items that are not true work scope. A well constructed WBS should include exactly 100% of the project work scope—no more, no less. On my current project, a number of items were ultimately excluded because they more correctly belonged to other areas and teams within our institution.
Taking the time to define—and document—what is not included in your project then allows you to convey this to your stakeholders. This, in turn, means that they won’t be surprised at the end of the project when you deliver X and they were expecting Y. It also allows you to properly budget and schedule the work you and your team have to perform during the course of the project.
Did you find this post useful? Sign up here for our free email list to help ensure more like it are created. Thanks!
You can also email me directly at Mark@TheProjectManagementBlueprint.com