A Planning Package: WBS Component Between Control Account and Work Package

PMBOK v8 Definition

A planning package is a WBS component below the control account and above the work package with known work content but without detailed schedule activities. A control account may include one or more planning packages. Each work package is associated with a single control account, while a control account has two or more work packages.

Why It Matters for the Exam

The planning package concept appears frequently in PMI exam questions testing your understanding of the Work Breakdown Structure (WBS) hierarchy and scope decomposition. Questions typically ask you to identify where a planning package fits in the WBS structure, distinguish it from work packages, or recognize situations where planning packages are used for future work that cannot yet be fully decomposed.

Key Points to Remember (for the exam)

• Hierarchical Position: Planning package sits below control account and above work package in the WBS hierarchy
• Known Content: Has known work content but no detailed schedule activities
• Control Account Relationship: A control account may include one or more planning packages
• Work Package Distinction: Work packages are the lowest level of the WBS; planning packages are above work packages
• Decomposition Purpose: Used when work content is known but not yet detailed enough for schedule activities
• Scope Baseline Component: Planning packages are part of the scope baseline, which includes the project scope statement, WBS, and WBS dictionary
• Unique Identifier: Like work packages, planning packages have unique identifiers in the code of accounts

Typical PMI Exam Example

Your project has a control account for "Software Development." You know the team will build three modules, but you cannot yet define the detailed activities for Module 3. In the WBS, you place Module 3 as a planning package below the control account and above future work packages, with known work content but without detailed schedule activities.

PMI Exam Traps

• Trap: Confusing planning package with work package → Reality: Planning packages are above work packages in the hierarchy and lack detailed schedule activities; work packages are the lowest level with cost and duration estimates
• Trap: Thinking planning packages are optional or rarely used → Reality: Planning packages are legitimate WBS components used when work content is known but decomposition is not yet complete
• Trap: Believing planning packages have detailed schedule activities → Reality: The defining characteristic is that planning packages have known work content but WITHOUT detailed schedule activities
• Trap: Confusing control account with planning package → Reality: Control accounts are management control points where scope, budget, and schedule are integrated; planning packages are WBS components within control accounts

Important PMI Connections

Quick Review Questions

1. Where does a planning package sit in the WBS hierarchy relative to control accounts and work packages?

2. What is the key characteristic that distinguishes a planning package from a work package?

3. Can a control account contain multiple planning packages?

4. What information is known about a planning package, and what information is not yet defined?

5. In which project document would you find detailed information about a planning package's deliverables, costs, and resources?

PMBOK v8 Reference

Section 2.1.6 - Project Planning Artifacts (Scope Baseline components including WBS, work packages, and planning packages)