Exam 4: Defining Scope, Quality, Responsibility and Activity Sequence

For some projects, the terms of payment may be tied to the customer's acceptance of certain deliverables.

The project scope is all the work that must be done to do all of the following except:

The focus must be on relying on after-the-fact inspections or testing and then do the necessary work to correct quality problems.

A comprehensive project scope document is the work breakdown structure.

The project scope document defines in terms of the statement of work and deliverables, and the WBS establishes the framework for to produce the project deliverables.

The project objective is usually defined in terms of

An activity does not necessarily require the expenditure of effort by people.

A project objective such as 'complete the project' is too ambiguous because the customer and the contractor may have of what is meant by 'complete'.

The project team or contractor must avoid , which is informally making changes to the project scope without appropriate approval.

The WBS establishes the framework for

All branches of the WBS have to be broken down to the same level.

The work packages are at a level can be assigned responsibility and accountability for achieving the work package.

The may include a high-level WBS in a graphic chart format or as an indentured list of the work elements and associated deliverables.

If the scope seems much less than originally anticipated by the customer, the customer and contractor would have to agree on increasing the budget, extending the schedule, reducing the scope, or some combination thereof.

Acceptance criteria for all project deliverables must be than what is stated in the project charter or request for proposal.

Having other project team members participate in developing the project scope statement and work breakdown structure increases the likelihood of building all the following except

A responsibility assignment matrix is used to designate the individuals responsible for achieving the work items in the work breakdown structure.

It is essential to wait until the end of the project to check if the sponsor/customer requirements and expectations have been met regarding the quality of the project deliverables.

For each deliverable, the quantitative measures or references to that will be used should be stated, as the criteria will be the basis for the customer agreeing that a deliverable is acceptable.

The project scope document is valuable for establishing