Skip to content
PMPCAPM

Work Package

A work package is the lowest level of the work breakdown structure, representing a deliverable or project work component that can be estimated, scheduled, monitored, and controlled.

Share:

Explanation

Work packages sit at the bottom of the WBS hierarchy and represent the smallest units of deliverable-oriented work that the project team defines during scope planning. They are the point at which cost and duration can be reliably estimated, work can be assigned to a responsible individual or team, and performance can be tracked.

During the Define Activities process in Schedule Management, work packages are further decomposed into activities (the actual tasks to be performed). This distinction is important: the WBS ends at the work package level, and activities are defined in the schedule, not in the WBS.

Work packages are typically described in detail in the WBS dictionary with attributes such as a code of account identifier, a statement of work, responsible organization, schedule milestones, acceptance criteria, and cost estimates. The size of a work package follows the general guideline of the 8/80 rule, meaning it should require between 8 and 80 hours of effort, though this is a guideline rather than a strict rule.

Key Points

  • Lowest level of the WBS hierarchy
  • Can be reliably estimated, scheduled, and controlled
  • Further decomposed into activities during Define Activities
  • Follows the 8/80 guideline (8 to 80 hours of effort)

Exam Tip

Activities are NOT part of the WBS. The WBS stops at the work package level. Activities are created from work packages during the Define Activities process in Schedule Management.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Power/Influence Grid

The power/influence grid is a stakeholder classification model that groups stakeholders based on their level of authority (power) and their active involvement or ability to affect the project (influence).

Part of

Scope Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.