PM Chapter 5

63. Some organizations prescribe the form and content for WBSs for particular projects. These are known as _____.

guidelines

68. The main tool for performing scope validation is _____ and group decision making techniques.

inspection

62. A work package is a task at the _____ level of the WBS.

lowest

65. _____ is a technique that uses branches radiating out from a core idea to structure thoughts and ideas when creating a WBS.

mind mapping

60. Tasks in a WBS that are decomposed into smaller tasks are called _____ tasks.

summary

1. Scope refers to all the work involved in creating the products of the project and the processes used to create them.

t

72. _____ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them.

use case modeling

34. The main technique used in creating a WBS is _____, which involves subdividing project deliverables into smaller pieces. a. conglomeration b. accumulation c. decomposition d. catalyzation

c. decomposition

24. The term ______ describes a product produced as part of a project. a. variance b. scope c. deliverable d. work package

c. deliverable

42. Mind mapping can be used for developing WBSs using a. the analogy approach only b. the bottom-up or analogy approach c. the top-down or bottom-up approach d. any approach

c. the top-down or bottom-up approach

38. The _____ approach for constructing a WBS involves refining the work into greater and greater levels of detail. a. analogy b. bottom-up c. top-down d. mind mapping

c. top-down

39. The _____ approach for constructing a WBS starts with the largest items of the project and breaks them into subordinate items. a. analogy b. bottom-up c. top-down d. mind mapping

c. top-down

48. _____ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them. a. Prototyping b. JAD c. RAD d. Use case modeling

d. Use case modeling

28. _____ 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. a. Creating scope b. Defining scope c. Controlling scope d. Validating scope

d. Validating scope

37. In the _____approach for constructing a WBS, you use a similar project's WBS as a starting point. a. top-down b. bottom-up c. mind-mapping d. analogy

d. analogy

40. 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. a. analogy b. bottom-up c. top-down d. mind mapping

d. mind mapping`

25. Scope refers to: a. each level of work that is outlined in a work breakdown structure. b. the end product created as part of a project that is delivered to the client. c. tasks that are decomposed into smaller tasks in a work breakdown structure. d. the work involved in creating the products and the processes used to create them.

d. the work involved in creating the products and the processes used to create them.

33. A(n) _____ is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project. a. project charter b. business case c. project scope statement d. work breakdown structure

d. work breakdown structure

35. A(n) ____ is a task at the lowest level of the WBS. a. variance b. objective c. deliverable d. work package

d. work package

12. The scope baseline in a WBS consists of the requirements documentation and enterprise environmental factors.

f

13. The WBS is organized solely around project phases.

f

14. A work package represents one component of the product that the project aims to deliver.

f

15. A work package must always represent less than 80 hours of work.

f

16. Given the project management software that is available, it is relatively easy to create a good WBS.

f

17. The tasks in a WBS must be developed as a sequential list of steps.

f

18. The executing tasks of the WBS remain constant from project to project.

f

21. The format of the WBS dictionary is essentially the same for all projects.

f

5. The project's size, complexity, importance, and other factors do not affect how much effort is spent on collecting requirements for scope planning.

f

7. Project scope statements must include the project boundaries, constraints, and assumptions.

f

8. The scope of a project is clear and specific from the start.

f

59. The _____ includes the approved project scope statement and its associated WBS and WBS dictionary.

scope baselina

69. _____ involves controlling changes to the project scope while keeping project goals and business strategy in mind.

scope control

67. _____ is the tendency for project scope to keep getting bigger and bigger.

scope creep

52. The main outputs of _____are the project scope statement and updates to project documents.

scope definition

2. Deliverables are only product-related, such as a piece of hardware or software.

F

58. Subdividing the project deliverables into smaller pieces is known as _____.

decomposition

56. The main outputs of scope definition are the _____ and project document updates.

moderate

50. _____ includes the processes involved in defining and controlling what work is or is not included in a project.

project scope mgmt

71. _____ involves developing a working replica of the system or some aspect of the system.

prototyping

54. _____ refer to "conditions or capabilities that must be met by the project or present in the product, service, or result to satisfy an agreement or other formally imposed specification."

requirements

55. A(n) _____ is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed.

requirements traceability matrix

51. _____ refers to all the work involved in creating the products of the project and the processes used to create them.

scope

26. _____ 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 b. Defining scope c. Controlling scope d. Validating scope

a. Collecting requirements

47. _____ refers to the process of developing a working replica of the system or some aspect of the system. a. Prototyping b. Variance c. Decomposition d. Use case modeling

a. Prototyping

45. _____ involves formal acceptance of the completed project scope by the stakeholders. a. Scope validation b. Scope planning c. Scope control d. Scope baseline

a. Scope validation

29. Creating the WBS is a subprocess associated with the _____ process in project scope management. a. planning b. monitoring and controlling c. closing d. executing

a. planning

32. 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 b. Gantt chart c. state transition table d. entity-attribute-value model

a. requirements traceability matrix

44. Scope creep refers to: a. the tendency for project scope to keep getting bigger and bigger. b. subdividing project deliverables into smaller pieces. c. the approved project scope statement and its associated WBS. d. a task at the lowest level of the WBS.

a. the tendency for project scope to keep getting bigger and bigger.

43. Which of the following is recommended for the creation of a good WBS? a. Any WBS item should be the responsibility of all the people working on it. b. A unit of work should appear at only one place in the WBS. c. Each WBS item should be created assuming that the requirements are inflexible. d. The work content of a WBS item is independent of the WBS items below it.

b. A unit of work should appear at only one place in the WBS.

27. _____ 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. a. Creating scope b. Defining scope c. Controlling scope d. Validating scope

b. Defining scope

49. _____ 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. a. Prototyping b. JAD c. RAD d. Use case modeling

b. JAD

46. _____ refers to the difference between planned and actual performance. a. Decomposition b. Variance c. Scope validation d. Scope creep

b. Variance

31. 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 _____. a. variance b. benchmarking c. prototyping d. decomposition

b. benchmarking

41. 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. a. analogy b. bottom-up c. top-down d. mind mapping

b. bottom-up

30. The ______ documents how project needs will be analyzed, documented, and managed. a. requirements traceability matrix b. requirements management plan c. WBS d. project scope statement

b. requirements management plan

36. The _____ should list and describe all of the deliverables required for the project. a. project charter b. scope statement c. WBS d. Gantt chart

b. scope statement

64. In the _____ approach to creating a WBS, team members first identify as many specific tasks related to the project as possible.

bottom-up

10. The project scope statement should reference supporting documents, such as product specifications that will affect what products are produced or purchased, or corporate policies, which might affect how products or services are produced.

t

11. The project scope statement, stakeholder requirements documentation, and organizational process assets are the primary inputs for creating a WBS.

t

19. Many organizations provide different guidelines and templates for developing WBSs.

t

20. Mind mapping allows people to write and even draw pictures of ideas in a nonlinear format.

t

22. A unit of work should appear at only one place in the WBS.

t

23. Scope creep if not managed well can lead to the failure of information technology projects.

t

3. Project scope management includes the processes involved in defining and controlling what is or is not included in a project.

t

4. The scope management plan can be informal and broad or formal and detailed, based on the needs of the project.

t

6. Information from the project charter provides a basis for further defining the project scope.

t

9. Many information technology projects also require detailed functional and design specifications for developing software, which also should be referenced in the detailed scope statement.

t

61. PMI uses the term "_____" to describe each level of work in the WBS.

task

70. _____ is the difference between planned and actual performance.

variance

53. Creating the _____ involves subdividing the major project deliverables into smaller, more manageable components.

wbs

57. A(n) _____ is a deliverable-oriented grouping of the work involved in a project that defines its total scope.

wbs

66. A(n) _____ is a document that describes detailed information about each WBS item.

wbs dictionary