Chapter 4 1 The project objective must be clear, attainable, specific, and measurable

subject Type Homework Help
subject Pages 14
subject Words 6569
subject Authors Jack Gido, James P. Clements

Unlock document.

This document is partially blurred.
Unlock all pages and 1 million more documents.
Get Access
page-pf1
CHAPTER 4: DEFINING SCOPE, QUALITY, RESPONSIBILITY, AND
ACTIVITY SEQUENCE
1. The project objective must be clear, attainable, specific, and measurable.
a. True
b. False
2. There can be situations where the project objective needs to be modified as the project proceeds.
a. True
b. False
3. The project scope defines what needs to be done.
a. True
b. False
4. Contractor requirements define the functional or performance specifications for the project’s end product
and other project deliverables.
a. True
b. False
5. 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.
a. True
b. False
page-pf2
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
6. 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.
a. True
b. False
7. Having the contractor or project team review the statement of work with the sponsor or customer
provides an opportunity to make sure everything that the customer expects is included.
a. True
b. False
8. A detailed description of each deliverable will help to manage stakeholder expectations.
a. True
b. False
9. An understanding of project deliverables would also be a setback to developing a good working
relationship with the customer.
a. True
b. False
page-pf3
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
10. The inclusion of specifications or standards will help assure quality of the deliverable.
a. True
b. False
11. A clear description of the acceptance criteria with quantitative measures will help to avoid
understanding.
a. True
b. False
12. For some projects, the terms of payment may be tied to the customer’s acceptance of certain
deliverables.
a. True
b. False
13. Clear, ambiguous acceptance criteria for all deliverables are important because they are the basis for
verifying that the project scope has been completed in accordance with the customer’s requirements and
expectations.
a. True
b. False
page-pf4
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
14. A network diagram is a technique for organizing and subdividing all the project work and deliverables
into more manageable components.
a. True
b. False
15. The deliverables in the project scope document will be used as the basis for creating a more detailed
WBS in the next step of the planning process.
a. True
b. False
16. 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.
a. True
b. False
17. 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 multiyear project, or a project that has several phases.
a. True
b. False
page-pf5
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
18. The project scope document is valuable for establishing a common understanding among project
stakeholders regarding the scope of the project.
a. True
b. False
19. 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.
a. True
b. False
20. The agreed-upon project scope document establishes the baseline for any changes that may be made to
the scope during the performance of the project.
a. True
b. False
21. Planning for quality is a necessary, yet often forgotten or dismissed, function on a project.
a. True
b. False
page-pf6
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
22. 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.
a. True
b. False
23. The quality plan may also state that suppliers must provide documentation certifying that the materials
they supply meet certain required specifications.
a. True
b. False
24. The project quality plan should state which tools and techniques to use and when.
a. True
b. False
25. The customer may hire an independent third party or laboratory to be its representative or perform tests
when checking the quality of a project deliverables.
a. True
b. False
page-pf7
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
26. The customer may make unannounced visits to the contactor’s facility or work.
a. True
b. False
27. The customer may randomly select certain work elements to review in order to determine whether they
are being done in conformance with quality standards and requirements.
a. True
b. False
28. With the quality plan in place including procedures for the application of appropriate quality tools and
techniques, quality can then be monitored and controlled.
a. True
b. False
page-pf8
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
29. The key to quality control is to wait until all the work is completed before checking or inspecting for
quality.
a. True
b. False
30. 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.
a. True
b. False
31. The focus must be on relying on after-the-fact inspections or testing and then do the necessary work to
correct quality problems.
a. True
b. False
page-pf9
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
32. The work breakdown structure subdivides the project into smaller pieces called work items.
a. True
b. False
33. The work package includes all of the specific work activities that need to be performed to produce the
deliverable associated with that work package.
a. True
b. False
34. The network diagram can be created using a graphic chart format or as an indentured list.
a. True
b. False
35. All branches of the WBS have to be broken down to the same level.
a. True
b. False
36. For large or complex projects, it may be difficult for one individual to determine all the work elements to
include in the work breakdown structure.
a. True
b. False
page-pfa
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
37. The project manager should involve every project member in developing the WBS to have special
expertise, knowledge, or experience that will help develop a more comprehensive and complete WBS.
a. True
b. False
38. The WBS usually indicates the organization or individual assigned responsibility for performance and
completion of each work item.
a. True
b. False
39. The work breakdown structure is the same thing as the project organization chart or structure.
a. True
b. False
40. Different project teams might create somewhat different work breakdown structures for the same project.
a. True
b. False
41. A responsibility assignment matrix defines who will be pay for the work.
a. True
b. False
page-pfb
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
42. A responsibility assignment matrix is used to designate the individuals responsible for accomplishing the
work items in the work breakdown structure.
a. True
b. False
43. Multiple individuals should be designated the lead, or primary, responsibility for each work item.
a. True
b. False
44. 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.
a. True
b. False
45. Activities define more generally than work packages how the work will get done.
a. True
b. False
46. An activity, also referred to as a task, is a defined piece of work that consumes effort by people and not
necessarily time.
a. True
b. False
page-pfc
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
47. An activity does not necessarily require the expenditure of effort by people.
a. True
b. False
48. It is easier to define the specific activities for near-term work; but as more information is known or
becomes clear, the project team can progressively elaborate the specific activities.
a. True
b. False
49. A project scope statement defines the sequence of how the activities will get done.
a. True
b. False
50. Certain activities in a network diagram have to be done in serial sequence.
a. True
b. False
51. Some activities in a network diagram may be done concurrently.
a. True
b. False
52. Some projects have a set of activities that are repeated several times.
a. True
b. False
page-pfd
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
53. A tangible output or product or deliverable as a result of an activity should define the end of one activity
in a network diagram and the start of other activities in the network diagram.
a. True
b. False
54. The is the tangible end product that the project team or contractor must produce and deliver in order
for the sponsor or customer to achieve the expected benefits from implementing the project.
a. network diagram
b. project plan
c. objective
d. work breakdown structure
55. The project objective is usually defined in terms of the
a. all the constraints for the project.
b. end product or deliverable, schedule, and budget.
c. initiating, planning, executing, and controlling.
d. project scope.
page-pfe
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
56. The project objective must be clearly defined and agreed upon by the
a. sponsor or customer and the project team or contractor that will perform the project.
b. stakeholders for the project.
c. project team and subcontractors.
d. suppliers of materials to the project.
57. Expected benefits, which will result from implementation of the project and define success, establish
a. the reason the contractor proposes the solution.
b. how much money the customer is willing to pay.
c. how quickly the project must be completed.
d. why the project is being done.
58. 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.”
a. the same idea
b. different views
c. similar understanding
d. a clear thought
page-pff
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
59. The project scope is all the work that must be done to do all of the following except:
a. meet with every stakeholder.
b. produce all the project deliverables.
c. accomplish the project objective.
d. satisfy the sponsor or customer that all the work and deliverables meet the requirements or acceptance
criteria.
60. The project scope document is valuable for establishing
a. a request for proposal for the project.
b. a common understanding among project stakeholders regarding the scope of the project.
c. the contact between the contractor and the customer.
d. the risk management plan for the project.
page-pf10
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
61. The customer requirements section should also include or reference that must be used and met
regarding quality and performance of the project work and deliverables.
a. applicable technical specifications, standards, and codes
b. quantitative and qualitative levels
c. audits and surveys
d. published articles
62. It is important to document the detailed requirements in the in order to establish a clear
understanding with the sponsor or customer.
a. statement of work
b. project scope document
c. network diagram
d. work breakdown structure
page-pf11
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
63. The defines the major tasks or work elements that will need to be performed to accomplish the work
that needs to be done and produce all the project deliverables.
a. statement of work
b. project scope document
c. network diagram
d. work breakdown structure
64. The defines what the project team or contractor will do.
a. statement of work
b. project scope document
c. network diagram
d. work breakdown structure
65. If something is the statement of work, then it should be assumed that .
a. included, it will not change during the course of the project.
b. not included in, it will not be done or provided.
c. missing from, if the RFP stated the requirement is will be completed.
d. left out of, will be completed during the project.
page-pf12
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
66. 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.
a. statement of work
b. customer requirement
c. deliverables
d. acceptance criteria
67. are the products or outputs that the project team or contractor will produce and provide to the
customer during and at the completion of the performance of the project.
a. Contracts
b. Acceptance criteria
c. Deliverables
d. Responsibilities
page-pf13
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
68. 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.
a. repeated
b. expanded on in greater detail
c. stated at higher levels
d. listed in sequence with the responsible person or organization
69. A detailed description of each deliverable should be stated to provide a basis for agreement between the
project team or contractor and the customer of
a. exactly what will be provided.
b. general terms of the contract.
c. who is responsible.
d. technical requirements.
page-pf14
Chapter 4: Defining Scope, Quality, Responsibility, and Activity Sequence
70. Acceptance criteria for all project deliverables must be than what is stated in the project charter or
request for proposal.
a. repeated
b. described in greater detail
c. stated at higher levels
d. listed in sequence with the responsible person or organization
71. 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.
a. specifications, standards, and codes
b. quantitative and qualitative levels
c. audits and surveys
d. published articles

Trusted by Thousands of
Students

Here are what students say about us.

Copyright ©2022 All rights reserved. | CoursePaper is not sponsored or endorsed by any college or university.