PM Test Center

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.

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.

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.

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.

Which of the following statements about project scope and product scope is true?

A. Product scope ensures effective flow of a project while project scope is used to create a product.
B. Project scope and product scope can be used synonymously.
C. Product scope cannot be used to describe a project but project scope can be used to describe a product.
D. Project scope refers to work that needs to be accomplished to create a product; product scope refers to features that characterize a product.

Answer: D. Project scope refers to work that needs to be accomplished to create a product; product scope refers to features that characterize a product.
All other choices are false.

During the planning phase of your project, you are working closely with your team to put the finishing touches on the initial work breakdown structure (WBS). As your last step, you add a unique identifier to each work package so it can be used to monitor scope, time and cost later in the project. These unique identifiers are commonly known as:

A. Milestones
B. WBS dictionary
C. Outline system
D. Code of accounts

Answer: D. Code of accounts
The code of accounts is a set of unique identifiers for each work package. They label the hierarchy to the WBS (e.g. 1, 1.1, 1.1.2, 1.1.2.5) so that scope can easily be monitored and controlled, especially for performance reporting such earned value.

On a project to build a new corporate intranet, the project manager makes a request that you, her mentor, to help her collect requirements. She lays out a plan and asks you if you prefer to help her with interviewing stakeholders or creating prototypes. However, before deciding, you want to ensure that she is ready to start this step. Which of the following is the most appropriate?

A. Review the WBS to ensure that the tasks are necessary
B. Ask her if which task she needs more guidance with
C. Ensure that the schedule is realistic and can accommodate both tasks
D. Ask her if she has an approved project charter

Answer: D. Ask her if she has an approved project charter
The project charter, along with stakeholder register, is an input to the Collect Requirements process. Without the approved charter, the project does not exist and therefore, any requirements work would be premature. None of the other choices should even be considered unless the charter is signed, which gives the project the go-ahead.

While creating a WBS, Greg is working with his team to break down the work into manageable pieces. Once completed, Greg expects to determine costs and create a schedule using the lowest level WBS components, which are called:

A. WBS activities
B. Organizational process assets
C. Work packages
D. Decomposed tasks

Answer: C. Work packages
The lowest level WBS components are called work packages. These are used to plan, as well as monitor and control, time and costs. WBS activities and decomposed tasks are not generally recognized terms. Decomposition is a tool and technique used to break down work in a WBS but does not refer to a level of a WBS. Organizational process assets relates to things like policies and lessons learned documents and can serve as inputs to the Create WBS process.

An output of a scope process that links requirements to their origin is called:

A. WBS dictionary
B. Requirements traceability matrix
C. Scope baseline
D. Requirements documentation

Answer: B. Requirements traceability matrix
The requirements traceability matrix, an output of the Collect Requirements process, helps ensure that each requirement adds business value by linking it to the business and project objectives (PMBOK®).

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.