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

In many cases, the customer states high-level requirements in the project charter or RFP, but the project team or the contractor may need to collect more information from the customer or end users to further refine the requirements.

The customer may make unannounced visits to the contactor's facility or work.

The work packages are at a level at which the wants to monitor and control the budget, and can collect data on actual costs and the value of the work completed during the performance of the project.

Having a written quality plan at the outset of a project is extremely beneficial because it guarantees against incurring additional costs and schedule extensions due to rework caused by work and deliverables that fail to meet quality requirements and customer expectations.

The at a level of a high degree of confidence that all the activities that need to be performed to produce the deliverable can be defined, the types and quantities of resources can be determined, and the associated activity durations and costs can be reasonably estimated.

The WBS usually indicates the organization or individual assigned responsibility for performance and completion of each work item.

If something is the statement of work, then it should be assumed that .

The responsibility assignment matrix may use a P to designate responsibility and an S to indicate responsibility for a specific work item.

The project objective is usually defined in terms of the

Some projects have a set of activities that are repeated several times.

At the beginning of the project it might not be possible to define all of the requirements, work elements, and deliverables at a detailed level.

Expected benefits, which will result from implementation of the project and define success, establish

The project scope document is valuable for establishing

The is a communication tool for the project team because it shows who is responsible for each activity and how each person's work fits into the overall project.

Standard subnetworks should be developed for those portions of projects for which

An activity, also referred to as a task, is a defined piece of work that consumes effort by people and not necessarily time.

Using the work breakdown structure, the individual or team responsible for each work package must next define all the specific activities that need to be performed to produce the end item or deliverable for the work package.

Multiple individuals should be designated the lead, or primary, responsibility for each work item.

The work breakdown structure can include specifications regarding size, color, weight, or performance parameters, such as speed, uptime, throughput, processing time, or operating temperature range, that the project result must satisfy.

The project objective must be clearly defined and agreed upon by the