This document discusses the work breakdown structure (WBS) and its importance in project management. It defines the WBS and explains that it is used to break down project deliverables and work into smaller, more manageable components in a hierarchical structure. It emphasizes that the WBS is central to project planning, budgeting, scheduling, and monitoring progress. The WBS dictionary is also described as an auxiliary document that provides details for each WBS component, such as quality requirements, time estimates, and resources.
8. 1. Neglecting to create a WBS Dictionary
2. Expecting More than 100% from your WBS
3. Why bother with Formal Change Control?
4. Skipping the Buy-In Process
5. Too Many Tasks
4.2 Developing a usable WBS
10. • Activities share some common characteristics like :
– Has an expected duration.
– Consumes budget and/or human resources.
– Is named in verb-noun format. Example (Revising a user manual –
Digging footers).
• The 8/80 rule :
– The 8/80 rule refers to a guide line suggesting that activities should
require more than 8 and fewer than 80 hours of effort to complete.
4.3 Using the WBS to clarify product
constraints and activities