Which of the following serves as a guiding principle for a program manager when preparing a program work breakdown structure?

The primary guiding principle for creating a Program Work Breakdown Structure (PWBS) is to decompose the work to a level that is sufficient for the program manager to effectively plan, execute, monitor, and control the program. The PWBS organizes and defines the total scope of the program, breaking it down into manageable components such as subprograms, projects, and other program-level work. The appropriate level of detail ensures that the program manager can maintain oversight, manage dependencies, and track progress against strategic objectives without getting into the granular detail managed at the component (project) level.

A. Decomposing the program work based upon available resources is incorrect because the PWBS is scope-driven, defining what work needs to be done, not who will do it. Resource allocation is a subsequent planning activity.
B. Decomposing the program to the work package level is incorrect. This level of detail is appropriate for a project WBS. A program WBS is a higher-level structure, typically decomposed only to the component level (e.g., projects).
C. Decomposing the program to the architecture baseline level is incorrect. The architecture baseline is a key input for defining scope, but the PWBS represents the decomposition of all program work, not just the technical architecture.

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 5.3.2.2, Program Work Breakdown Structure (WBS) and WBS Dictionary, p. 89. The standard states, "The program WBS is decomposed to a level of detail appropriate for the program manager to plan, execute, and control the program." This directly supports the principle of decomposing to a level sufficient for control.

2. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 5.3.2.2, p. 89. The text clarifies that, "The program WBS is typically not decomposed to the same level of detail as the WBSs for the projects within the program," which refutes the idea of decomposing to the work package level (Option B).

3. Thiry, M. (2015). A Framework for Value Management Practice. In Program Management: A Life Cycle Approach (Chapter 5). John Wiley & Sons. This academic text reinforces that program-level structures like the PWBS are focused on benefits and control at a strategic level, distinct from the deliverable-focused detail of a project WBS. The level of decomposition is dictated by the need for program-level governance and control.