CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach

The WBS decomposes the total project scope into hierarchical work packages — the smallest units of work that can be planned, estimated, and assigned. It defines WHAT will be done (scope), not when or how. The WBS is the foundation for schedule, cost, and resource planning in a predictive approach.

**Why not B:** Defining the sequence of activities and their dependencies is the purpose of the Sequence Activities process, not the WBS. The WBS decomposes scope into work packages; the activity sequencing process then determines the logical order in which those activities must be performed.

**Why not C:** Estimating the probability and impact of project risks is part of the risk management processes (Perform Qualitative and Quantitative Risk Analysis). The WBS is a scope decomposition tool that has no direct role in risk assessment.

**Why not D:** Assigning team members to specific tasks is done through the responsibility assignment matrix (RAM/RACI) and resource management processes. The WBS defines what work exists but does not specify who will perform it.