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

The WBS is of deliverables or end items that will be achieved or produced by the project team or contractor during the project.

Many projects because of scope creep caused by additional work that was not documented or approved, or was not communicated and in turn caused errors or rework for other elements of the project.

Although major or key deliverables may be stated in the project charter or request for proposal, they need to be in the project scope document.

Certain activities in a network diagram have to be done in serial sequence.

An understanding of project deliverables would also be a setback to developing a good working relationship with the customer.

A shows their appropriate sequence and defines the dependent relationships indicating how the activities need to be performed to achieve the overall project work scope and produce the deliverables.

The all of the lowest-level work packages in the work breakdown structure constitutes completion of the project work scope.

A clear description of the acceptance criteria with quantitative measures will help to avoid understanding.

The project quality plan should state which tools and techniques to use and when.

The shows all the individuals associated with each work item in the work breakdown structure, as well as all the work items associated with each individual.

The defines what the project team or contractor will do.

The section of the project scope document is where the contractor or project team can state and clarify exactly what is included in the work scope and provide an opportunity to reconsider items that are not stated but that the customer may have forgotten to include in her requirements or RFP.

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

Each box for an activity in a network diagram is assigned

The WBS should be decomposed to a level that identifies individual work packages for

The states the specific deliverable that is expected to be completed from the work activities associated with each lowest level work package.

It is important to plan for in performing the project to assure that the work is done according to specifications and applicable standards and that deliverables meet acceptance criteria.

It is easier to define the details for , but as the project progresses or moves from phase to phase, the project team or contractor can progressively elaborate the details as more information is known or becomes clear.

Quality standards that will be used should also be stated and referenced in other appropriate project documents, such as technical specifications and acceptance criteria, and communicated to members of the project team

It might not be possible to define all of the requirements, work elements, and deliverables at a detailed level for a project with a long duration, such as a multi-year project, or a project that has several phases.