Work Breakdown Structure (WBS)

Correct Answer: Consolidate related work packages into higher-level elements

The best approach to simplify a WBS that has become too detailed is to consolidate related work packages into higher-level elements. This method helps in streamlining the WBS while maintaining its essential structure and purpose.

Consolidating related work packages allows for a more manageable overview of the project, reducing complexity without losing important information. It helps in better communication and understanding of the project scope among stakeholders.

The other options are not appropriate solutions:

Removing tasks that are not on the critical path is not advisable as it would eliminate important project components, potentially leading to scope creep and incomplete deliverables.

Assigning multiple team members to each task doesn't simplify the WBS structure itself and may lead to resource allocation issues and decreased efficiency.

Creating separate WBS structures for each project phase could lead to fragmentation and loss of overall project coherence, making it harder to manage the project as a whole.

By consolidating related work packages, project managers can maintain a comprehensive yet manageable WBS, ensuring effective project planning and control.

Correct Answer: To ensure all work necessary to complete the project is included

The primary purpose of the '100% rule' in developing a Work Breakdown Structure (WBS) is to ensure all work necessary to complete the project is included. This rule is fundamental in project management as it helps to:

1. Capture the entire project scope
2. Prevent scope creep
3. Ensure no work is overlooked or duplicated

The correct answer emphasizes this comprehensive inclusion of all project work.

The other options are incorrect because:

- Guaranteeing all work packages are broken down to the same level of detail is not the primary purpose of the 100% rule. While consistent detail is important, it's not the rule's main focus.

- Validating task assignment to team members is a separate process, typically done after the WBS is created. The 100% rule focuses on work definition, not resource allocation.

- Confirming stakeholder approval for each WBS element is a different process. While stakeholder input is valuable, the 100% rule is about work content, not approval processes.

The 100% rule ensures that the WBS represents the complete project scope, making it a crucial tool for effective project planning and management.

Correct Answer: You should use the Change Control Process.

The correct answer is that you should use the Change Control Process. In Project Management, especially in large projects, new requirements or changes after the project is underway cannot be added directly into the Work Breakdown Structure (WBS). That answer is incorrect. It's vital to go through a Change Control Process which analyses and estimates the impact of a change on the project's schedule, cost, resources and risk before making a final decision. It ensures the changes are documented and the necessary adjustments are made to maintain the overall integrity of the project. The answer suggesting to ignore the stakeholder's request is not ideal as stakeholders' feedback is crucial for the project's success. Ignoring their request could lead to dissatisfaction and project failure. Finally, the idea of creating an entirely new WBS for including the new feature in the middle of the project execution is impractical. It is not a feasible solution as it could lead to unnecessary rework, confusion among team members and a misalignment of original project objectives and deliverables.