Project Scope Management 37

10. Rather than use a WBS, your team developed a bill of materials to define
the projects work components. A customer review of this document uncov-
ered that a scope change was needed, because a deliverable had not been
defined, and a change request was written subsequently. This is an example
of a change request that was the result of
a. An external event
b. An error or omission in defining the scope of the product
c. A value-adding change
d. An error or omission in defining the scope of the project

11. Collecting requirements is critical in project scope management as it

becomes the foundation for the projects
a. Scope management plan
b. WBS
c. Schedule
d. Scope change control system

12. The project scope statement addresses and documents all the following
items EXCEPT
a. Project exclusions
b. The relationship between the deliverables and the business need
c. Product scope description
d. Project management methodology (PMM)

13. The first step in collecting requirements on any project, large or small,
isto
a. Talk with the project stakeholders through interviews
b. Review the scope management plan
c. Conduct facilitated workshops with stakeholders
d. Prepare a requirements document template that you and your team can
use throughout the collect requirements process

14. You want to structure your project so that each project team member has a
discrete work package to perform. The work package is a
a. Deliverable at the lowest level of the WBS
b. Task with a unique identifier
c. Required level of reporting
d. Task that can be assigned to more than one organizational unit