A hierarchical breakdown of a project into smaller tasks and activities is called what?

A hierarchical breakdown of a project into smaller tasks and activities is called what?

• A. Levels of Work Breakdown Structure
• B. Gantt Chart
• C. Network Diagram
• D. Work Breakdown Structure (WBS)

Answer: (D)

A hierarchical breakdown of a project into smaller tasks and activities is called a Work Breakdown Structure. The idea is to take the project deliverables and divide them into progressively smaller, more manageable components until each piece can be planned, assigned, and measured. The WBS is deliverable-oriented, not a timeline; it defines what must be done rather than when it happens. At the top is the project as a whole, and each descending level adds detail by breaking deliverables into sub-deliverables and finally into work packages—the smallest units that can be scheduled, resourced, and costed. The WBS often comes with a WBS dictionary that describes each work package, its owner, scope, and acceptance criteria. This structure helps clarify scope, prevent scope creep, and provide a solid foundation for estimating time and cost, assigning responsibilities, and anchoring the project schedule. It’s different from a Gantt chart, which shows timing and sequencing, and from a network diagram, which maps dependencies.

A hierarchical breakdown of a project into smaller tasks and activities is called a Work Breakdown Structure. The idea is to take the project deliverables and divide them into progressively smaller, more manageable components until each piece can be planned, assigned, and measured. The WBS is deliverable-oriented, not a timeline; it defines what must be done rather than when it happens. At the top is the project as a whole, and each descending level adds detail by breaking deliverables into sub-deliverables and finally into work packages—the smallest units that can be scheduled, resourced, and costed. The WBS often comes with a WBS dictionary that describes each work package, its owner, scope, and acceptance criteria. This structure helps clarify scope, prevent scope creep, and provide a solid foundation for estimating time and cost, assigning responsibilities, and anchoring the project schedule. It’s different from a Gantt chart, which shows timing and sequencing, and from a network diagram, which maps dependencies.