WBS breakdown
While working on a WBS, breaking down work into manageable parts is known as:
A. Decomposition
B. WBS dictionary
C. Work package
D. Scope management
Answer: A. Decomposition
Work packages are the lowest level of a WBS. The process of getting to that point is called decomposition.
Collect Requirements description
One way to describe the Collect Requirements Process is that it documents the stakeholders’ __________ to meet the __________.
A. Wants, target end date
B. Demands, needs
C. Expectations, quality standards
D. Needs, project objectives
Answer: D. Needs, project objectives
Collecting Requirements includes defining and documenting the needs of the stakeholders in order to reach the objectives of the project.
Verify Scope input
In order to execute the Verify Scope process, at a minimum, you must have:
A. Prototypes
B. Accepted deliverables
C. Project charter
D. Validated deliverables
Answer: D. Validated deliverables
Validated deliverables is a key input to the Verify Scope process. Without them, the process cannot occur. Other potential inputs to the process are project management plan, requirements documentation, and requirements traceability matrix.
Collect Requirements tools and techniques
Which tools and techniques are used during the Collect Requirements process?
A. Interviews and focus groups
B. Product analysis and inspection
C. WBS and WBS dictionary
D. Variance analysis and decomposition
Answer: A. Interviews and focus groups
The Collect Requirements process tools and techniques include interviews, focus groups, facilitated workshops, group creativity techniques, group decision making techniques, questionnaires and surveys, observations, and prototypes.
Accepted deliverables
Jim had his project’s key deliverable approved by his sponsor. Which process did he just complete?
A. Control Scope
B. Approve Scope
C. Verify Scope
D. Define Scope
Answer: C. Verify Scope
Accepted deliverables is the main output of the Verify Scope process.
Collect Requirements outputs
As a result of the Collect Requirements process, you could have:
A. Requirements documentation, project scope statement, WBS
B. Requirements documentation, requirements management plan
C. Project scope statement, requirements management plan
D. WBS, WBS dictionary
Answer: B. Requirements documentation, requirements management plan
The potential outputs of the Collect Requirements process are requirements documentation, requirements management plan, and requirements traceability matrix.
Scope verification deliverable
What is a key deliverable of the Verify Scope process?
A. Approved requirements
B. Customer acceptance
C. Product that passed quality tests
D. Completed WBS
Answer: B. Customer acceptance
The primary output of the Verify Scope process is an accepted deliverable. That means that the deliverable has met acceptance criteria and was formally signed off by the customer or sponsor.
Gantt chart weakness
You plan on using a project management information system (PMIS) to develop a Gantt chart. One drawback of using a Gantt chart is:
A. Finish dates for each project cannot be manually set
B. WBS outline cannot be represented
C. Relationships between tasks are not displayed
D. Only one resource can be assigned to a task
Answer: C. Relationships between tasks are not displayed
Although some PMIS tools do show relationships between tasks (e.g. Microsoft Project), traditionally, Gantt charts do not display them.
Scope management plan
The purpose of a scope management plan is:
A. Identify requirements on the project
B. Break down the work into manageable pieces
C. Monitor scope on the project
D. Describe how scope will be managed on the project
Answer: D. Describe how scope will be managed on the project
As with any management plan, the key is to describe how something will be managed. The key word being ‘how’. You do not actually do anything with the scope at this point; rather simply documenting the process of managing scope. The other choices on the list refer to other scope processes.
Work package size
Paula is creating a WBS for her project’s scope. However, she does not know the size of the work packages to break the work down to. As an experienced project manager, you tell her that one way to do it is to:
A. Ensure that no task is under 1 hour.
B. Drill down as far as she can.
C. Keep each work package between 8 and 80 hours.
D. Do what she feels is right.
Answer: C. Keep each work package between 8 and 80 hours.
As a general rule, work packages should be a manageable chunk. One method is to use the 8/80 rule. Usually, anything under a day of work can be managed by the resource and anything over two weeks should probably be broken down further.
0 Comments