I have been reading this a few times and still can't quite visualize what it is. Can someone direct me to a sample of a WBS dictionary? Thanks. Saving Changes...
There are a variety of templates and samples online, but essentially the WBS dictionary is the narrative work statement and associated metadata.
It describes the details of the tasks to be performed, who is responsible for the work, duration, key dependencies, assumptions, and other descriptive data to fully define the tasks. To use an object oriented analogy, the WBS task level are the objects, and the WBS dictionary contains all the object attributes.
Personally I think it's an unfortunate title, since it doesn't define the WBS at all, but merely the task level.
...
1 reply by Lilian Seow
Jan 31, 2021 8:25 PM
Lilian Seow
...
Thank you Keith. I guess the "dictionary" sounds rather odd and unfamiliar.
WBS dictionary is a set of definition of each component of the work breakdown structure (WBS), it includes data as Component number code, required resources, scheduled start and end dates, duration, estimated cost, responsible, Quality Control protocol, Contract, and Technical Information.
It should be consulted before commencing any work component in order to understand adequately the things that should be done and ensure that the correct resources, proper standards, procedures, and quality control measures are being followed. Saving Changes...
Here's an example. I haven't checked it, but the page says it's from PMI's practice Standard for Work Breakdown Structures, which you can get for free (digital copy) if you're a PMI member.
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Lilian,
a WBS is often presented as a tree of boxes (WBS elements, e.g. work packages at the lowest level), that break down the work scope of the project. One main purpose is to show to stakeholders on one sheet how you structure the work.
In the process of breaking down the scope and further planning of the project, you will assign lots of attributes to each of the WBS boxes but it would be unfortunate to try to put all of them in the WBS. As you plan, there will be attributes for scheduling, cost estimation, risks, quality, deliverables, resources etc..
Here comes the WBS dictionary for help. In a simple form, it can be an excel sheet with columns representing the attributes and a row for each WBS box. As I said before, it is not filled once and forever, but is filled step by step and even updated when something changes (which is an example of progressive elaboration).
On mega-projects, a WBS dictionary might be a binder (or a library full of binders!) where each section is a distinct control account and each page is a separate work package.
The level of detail and the specific elements captured will vary depending on the context, industry and compliance requirements affecting the project.
On mega-projects, a WBS dictionary might be a binder (or a library full of binders!) where each section is a distinct control account and each page is a separate work package.
The level of detail and the specific elements captured will vary depending on the context, industry and compliance requirements affecting the project.
a WBS is often presented as a tree of boxes (WBS elements, e.g. work packages at the lowest level), that break down the work scope of the project. One main purpose is to show to stakeholders on one sheet how you structure the work.
In the process of breaking down the scope and further planning of the project, you will assign lots of attributes to each of the WBS boxes but it would be unfortunate to try to put all of them in the WBS. As you plan, there will be attributes for scheduling, cost estimation, risks, quality, deliverables, resources etc..
Here comes the WBS dictionary for help. In a simple form, it can be an excel sheet with columns representing the attributes and a row for each WBS box. As I said before, it is not filled once and forever, but is filled step by step and even updated when something changes (which is an example of progressive elaboration).
There are a variety of templates and samples online, but essentially the WBS dictionary is the narrative work statement and associated metadata.
It describes the details of the tasks to be performed, who is responsible for the work, duration, key dependencies, assumptions, and other descriptive data to fully define the tasks. To use an object oriented analogy, the WBS task level are the objects, and the WBS dictionary contains all the object attributes.
Personally I think it's an unfortunate title, since it doesn't define the WBS at all, but merely the task level.
Thank you Keith. I guess the "dictionary" sounds rather odd and unfamiliar. Saving Changes...
Community Champion
