chapter-5 edited
1. 1. The term describes a product produced as part of a project.
c. deliverable
2. Scope refers to:
d. the work involved in creating the products and the processes used to create them.
3. involves defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them.
a. Collecting requirements
4. involves reviewing the project charter, requirements documents, and organizational process assets to create a scope statement, adding more information as requirements are developed and change requests are approved.
b. Defining scope
5. involves formalizing acceptance of the project deliverables and during this phase the key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables.
d. Validating scope
6. Creating the WBS is a subprocess associated with the process in project scope management.
a. planning
7. The documents how project needs will be analyzed, documented, and managed.
b. requirements management plan
8. Generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization is known as .
b. benchmarking
9. A(n) is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed.
a. requirements traceability matrix
10. A(n) is a deliverable -oriented grouping of the work involved in a project that defines the total scope of the project.
d. work breakdown structure
11. The main technique used in creating a WBS is , which involves subdividing project deliverables into smaller pieces.
c. decomposition
12. A(n) is a task at the lowest level of the WBS.
d. work package
13. The should list and describe all of the deliverables required for the project.
b. scope statement
14. In the approach for constructing a WBS, you use a similar project’s WBS as a starting point.
d. analogy
15. The approach for constructing a WBS involves refining the work into greater and greater levels of detail.
c. top-down
16. The approach for constructing a WBS starts with the largest items of the project and breaks them into subordinate items.
c. top-down
17. In the approach, team members first identify as many specific tasks related to the project as possible and then aggregate the specific tasks and organize them into summary activities, or higher levels in the WBS.
b. bottom -up
18. The technique for creating a WBS uses branches radiating from a core idea to structure thoughts and ideas instead of writing down tasks in a list or immediately trying to create a structure for tasks.
d. mind mapping
19. Which of the following is recommended for the creation of a good WBS?
b. A unit of work should appear at only one place in the WBS. assuming that the requirements are inflexible.
20. Scope creep refers to:
a. the tendency for project scope to keep getting bigger and bigger.
21. involves formal acceptance of the completed project scope by the stakeholders.
a. Scope validation
22. refers to the difference between planned and actual performance.
b. Variance
23. refers to the process of developing a working replica of the system or some aspect of the system.
a. Prototyping
24. is a process for identifying and modeling business events, who initiated them, and how the system should respond to them.
d. Use case modeling
25. uses highly organized and intensive workshops to bring together project stakeholders —the sponsor, users, business analysts, programmers, and so on—to jointly define and design information systems.
b. JAD