CH 5 Project Management
The term ______ describes a product produced as part of a project. a. variance b. scope c. deliverable d. work package
C
A(n) ____ is a task at the lowest level of the WBS. a. variance b. objective c. deliverable d. work package
D
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
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
T/F: A unit of work should appear at only one place in the WBS
true
T/F: Information from the project charter provides a basis for further defining the project scope
true
T/F: Many information technology projects also require detailed functional and design specifications for developing software, which also should be referenced in the detailed scope statement
true
T/F: Many organizations provide different guidelines and templates for developing WBSs
true
T/F: Mind mapping allows people to write and even draw pictures of ideas in a nonlinear format
true
T/F: Project scope management includes the processes involved in defining and controlling what is or is not included in a project
true
T/F: Scope creep if not managed well can lead to the failure of information technology projects
true
T/F: Scope refers to all the work involved in creating the products of the project and the processes used to create them
true
T/F: 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
true
T/F: The scope management plan can be informal and broad or formal and detailed, based on the needs of the project
true
T/F:The project scope statement, stakeholder requirements documentation, and organizational process assets are the primary inputs for creating a WBS
true
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
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
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
_____ 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
_____ involves formal acceptance of the completed project scope by the stakeholders. a. Scope validation b. Scope planning c. Scope control d. Scope baseline
A
_____ 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
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
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
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
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
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
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
_____ 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
_____ refers to the difference between planned and actual performance. a. Decomposition b. Variance c. Scope validation d. Scope creep
B
_____ 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
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
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
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 _____ 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
_____ 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
_____ 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
T/F: A work package represents one component of the product that the project aims to deliver
false
T/F: Deliverables are only product-related, such as a piece of hardware or software
false
T/F: Project scope statements must include the project boundaries, constraints, and assumptions
false
T/F: The WBS is organized solely around project phases
false
T/F: The executing tasks of the WBS remain constant from project to project
false
T/F: The format of the WBS dictionary is essentially the same for all projects
false
T/F: The project's size, complexity, importance, and other factors do not affect how much effort is spent on collecting requirements for scope planning
false
T/F: The scope baseline in a WBS consists of the requirements documentation and enterprise environmental factors
false
T/F: The scope of a project is clear and specific from the start
false
T/F: The tasks in a WBS must be developed as a sequential list of steps
false
T/F:A work package must always represent less than 80 hours of work
false