PMBOK - Chapter 5

Question 0

How a WBS is structured?

Answer 0

Each descending level of the WBS represents an increasingly detailed definition of the project work. The WBS is finalized by assigning each work package to a control account and establishing a unique identifier for that work package from a code of accounts.

Question 1

What is a WBS?

Answer 1

Is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.

Question 2

What are the benefits of using a WBS?

Answer 2

• Helps prevent work from slipping through the cracks
• Provides the project team members with an understanding of where their fit into the overall project management plan and gives them an indication of the impact of their work on the project as a whole
• Facilitates the communication and cooperation between and among the project team and other stakeholders
• Helps prevent change
• Focuses then team’s experience on what needs to be done, resulting in higher quality and a project that is easier to manage
• Provides a basis for estimating staff, cost, and time
• Provides the proof of the need for staff, cost and time
• Gets team buy-in and build the team
• Helps people Get their minds around the project

Question 3

What do you do with a WBS once you have created it?

Answer 3

When completed, the WBS can be used any time the scope of the project need to be reevaluated. For example:

• Where there is a scope change to the project; The WBS along with the scope statement ca help to see is the new scope is within the planning scope of the project;
• As a part of integrated change control to evaluate any impacts of other changes on scope;
• As a way to control scope creep by reminding everyone what work is to be done;
• To help new team members see their roles.

Question 4

What are requirements?

Answer 4

Requirements include conditions or capabilities that are to be met by the project or present in the product, service, or result to satisfy an agreement or other formally imposed specification. Requirements include the quantified and documented needs and expectations of the sponsor, customer, and other stakeholders.