According to the PMBOKGuide, specifically within the Create WBS process, decomposition is the technique of subdividing project deliverables and project work into smaller, more manageable components called work packages. However, the guide warns against excessive decomposition.
* The Risk of Over-Decomposition: While breaking down work helps in estimation and control, doing so excessively (creating work packages that are too small) leads to several negative outcomes:
* Non-productive Management Effort: If the WBS is too granular, the overhead required to track, manage, and report on hundreds or thousands of tiny tasks outweighs the benefit of the control gained. The project manager spends more time on administrative updates than on leading the project.
* Inefficient Use of Resources: Resources may feel " micromanaged, " and the natural flow of work is interrupted by the need to constantly " start " and " stop " tiny administrative units of work.
* Decreased Utility: When work is broken down beyond a logical point, it becomes difficult to aggregate data meaningfully, leading to " noise " in project performance reports.
Analysis of Other Options:
* A and B. Insufficient project funding: Funding is generally determined by the scope and cost estimates, not by how finely the WBS is decomposed. While poor decomposition can lead to poor estimates, it is not a direct " identified risk " of the decomposition process itself.
* A and C. Disqualification of sellers: This is a procurement risk related to the Conduct Procurements process (e.g., a vendor failing to meet criteria), and is unrelated to how the internal project team breaks down their work structure.
* B. Ineffective use of resources: While similar to " inefficient, " the term " Non-productive management effort " is the specific terminology used in PMI standards to describe the administrative burden of an over-decomposed WBS.