According to the PMBOK Guide, the technique described is a core component of both Create WBS and Estimate Activity Durations. The process of breaking down a project deliverable or a high-level project component into smaller, more manageable parts is formally known as Decomposition.
* How it Works: The team starts with the final deliverables (as defined in the Scope Statement) and divides them into smaller components until the work is defined at the " work package " level.
* Estimation Link: Once the work is decomposed into these smaller, specific tasks, it becomes significantly easier and more accurate for the team to provide a " bottom-up " estimate of the effort, time, and resources required for each piece.
* Team Involvement: As seen in the scenario, involving the team in decomposition ensures that those who will perform the work are the ones analyzing it, leading to higher buy-in and accuracy.
Analysis of other options:
* A. Rolling wave planning: This is an iterative planning technique where work to be accomplished in the near term is planned in detail, while work further in the future is planned at a higher level. While it involves decomposition, it is a strategy for when to plan, not the specific act of breaking down work to estimate effort.
* B. Expert Judgement: This involves using individuals or groups with specialized knowledge. While the team members are " experts, " the method they are using to analyze the deliverables is decomposition.
* D. Data analysis: This is a broad category of techniques (like Alternative Analysis or Reserve Analysis). While the team is " analyzing " work, the specific systematic breakdown of deliverables described is the definition of decomposition.
Per PMI standards, Decomposition is the essential tool used to transform high-level scope into a detailed list of activities that can be measured, scheduled, and estimated.