Page 131 - Project+

If your organization typically undertakes projects that are similar in size,
scope, and complexity, consider using your existing WBS as a template for future
projects. It’s a great starting point for the new project and can help kick off the
brainstorming session with the project team.

A detailed WBS will not only prevent critical work from being overlooked, but it will
also help control change. If the project team has a clear picture of the project objectives
and the map to reach these objectives, they are less likely to go down a path unrelated
to the project scope. I don’t mean to imply that a WBS will prevent change; there are

almost always changes during the project life cycle. But a WBS will clarify that a
request is a change and not part of the original project scope. The WBS is also useful
when discussing staffing requirements or budgets.

The WBS is an excellent tool for communicating with customers and stakeholders.
People don’t always comprehend the magnitude of a project until they see the diagram
of the project deliverables and the subcomponents required to reach the objectives of

the project. Seeing the work of the project displayed on a WBS will help you convey to
the project team and the stakeholders the need for communicating at all levels of the
project, coordinating work efforts, and adhering to the project scope.

WBS Dictionary

There’s one more component of the WBS, called the WBS dictionary. This is where the
WBS levels and work component descriptions are documented. These are some of the

elements you should list in the WBS dictionary:

Code of accounts identifier

Description of the work of the component

Organization responsible for completing the component

Resources

Cost estimates

Criteria for acceptance

All the WBS components should be listed in the dictionary. This serves as a reference
for you and the team regarding the WBS and should be easily accessible to all project

team members.

Main Street Office Move

After the kickoff meeting, you’re ready to write the scope statement and the work

131