Ahmed KararProject Engineer| Ministry of Water Resources, Irrigation and Electricity Khatoum, Khatoum/ Jabl Awlia, Sudan
Information in the WBS dictionary may include but is not limited to:
Code of account identifier,
Description of work,
Assumptions and constraints,
Responsible organization,
Schedule milestones,
Associated schedule activities,
Resources required,
Cost estimates,
Quality requirements,
Acceptance criteria,
Technical references, and
Agreement information.
_____________________
I quoted the above list from PMBOK6, how I find the Associated schedule activities,
and other information before their process started note that WBS dictionary is part of scope baseline which should be change only as per formal change request. and how it comes to have incomplete baseline at first place Saving Changes...
Remember that processes are iterative and you will progressively elaborate many of the artifacts or documents over the life of the project.
So while the first creation of the WBS and WBS Dictionary might lack some details, as you proceed through schedule, cost, quality, HR and other processes, you will add those details to the WBS Dictionary.
A WBS Dictionary is merely a supporting document, which provides the definitions for each component contained in the WBS. Due to ever-changing circumstances, the Work Breakdown Structure Dictionary is under constant revision. Addition of details in WBS dictionary should not require to go through the formal change control process until and unless you are changing a WBS element entirely.
...
1 reply by Ahmed Karar
Jan 07, 2018 2:36 AM
Ahmed Karar
...
Nice comment Mr.Najam, generally I do agree with you that at first place we would not be able to have all information, activities, costs, resources...etc; we need to complete the WBS dictionary and I do agree that in the future when we insert those information it could be consider as revision or update rather than a change. that revision/update in the PMBOK is always mentioned as project management plan update but in the inputs of define activities the suggested update is to schedule and cost baseline so why they didn't put the scope baseline to give a chance to update the WBS dictionary.
Saving Changes...
Mehran BagherianControl and Instrumentation Engineer| RV AndersonNorth York, Canada
Ahmed,
Essentially WBS dictionary is going to provide detailed deliverable, activity, and scheduling information about each component in the WBS, and normally assigned to each work package which includes activities; i.e. the tasks which make a work package to be done.
Therefore, in spite of the fact that planning will be iterative, the "Associated schedule activities" are known since the beginning.
For instance; in a construction project, making a foundation (work package) needs the bar bending, forming, concrete pouring, etc. (Associated schedule activities) be performed.
Mehran Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
If you ask me for one deliverable I always create in a project is the WBS Dictionary no matter I have created a WBS or not. We create it with this objective: each person that has been assigned to an activity when she/he has to start working all the information she/he needs is inside the WBS Dictionary. So, you listed something valid but is a basement for us because we have modified it to achieve our objective. Saving Changes...
I completely agree with Kiron at one point: processes are iterative, and you can hardly have all the information that the WBS dictionary can contain, but you will get it through the project as the related processes start running and producing their output, some of which will provide valuable information to add to your WBS Dictionary. Saving Changes...
WBS dictionary is key to any important project. It may need interaction to be fully complete. The basis should be there from the start.It is a great way to find if anything is left behind. Saving Changes...
The various WBS dictionary components will change constantly, so it isn't feasible to get change request for each one, unless as Najam pointed out one of the deliverables or sub-deliverables are changed, Saving Changes...
Anish AbrahamPrivacy Program Manager| University of WashingtonAuburn, Wa, United States
My understanding is that WBS dictionary is an important tool for planning, because it's the repository the information needed to estimate project cost, calculate project resources, build an estimated schedule and define the project scope. Saving Changes...
Ahmed KararProject Engineer| Ministry of Water Resources, Irrigation and Electricity Khatoum, Khatoum/ Jabl Awlia, Sudan
Jan 04, 2018 8:47 AM
Replying to Najam Mumtaz
...
A WBS Dictionary is merely a supporting document, which provides the definitions for each component contained in the WBS. Due to ever-changing circumstances, the Work Breakdown Structure Dictionary is under constant revision. Addition of details in WBS dictionary should not require to go through the formal change control process until and unless you are changing a WBS element entirely.
Nice comment Mr.Najam, generally I do agree with you that at first place we would not be able to have all information, activities, costs, resources...etc; we need to complete the WBS dictionary and I do agree that in the future when we insert those information it could be consider as revision or update rather than a change. that revision/update in the PMBOK is always mentioned as project management plan update but in the inputs of define activities the suggested update is to schedule and cost baseline so why they didn't put the scope baseline to give a chance to update the WBS dictionary. Saving Changes...
