Question

Mariko has created a work breakdown structure diagram to show work broken down into manageable pieces. Which choice is not a reason for creating the WBS?

1) To define the scope of the project
2) To allocate resources and estimate costs
3) To identify dependencies and sequence of activities
4) To track project progress and monitor performance

Answer 1

While a Work Breakdown Structure (WBS) helps to define the scope, allocate resources, and identify dependencies within a project, it is not created to monitor project progress, which is tracked using other tools like Gantt charts.

Step-by-step explanation:

Mariko has created a Work Breakdown Structure (WBS) diagram which is essential in project management. The correct reasons for creating a WBS include:

1. To define the scope of the project, ensuring that all necessary work is included.
2. To allocate resources and estimate costs, which facilitates budget planning.
3. To identify dependencies and sequence of activities, which helps in scheduling and planning project tasks.

However, the choice that is not a reason for creating a WBS is to track project progress and monitor performance. This is typically done using tools like Gantt charts or project dashboards that track and display progress against the project plan established by the WBS.