Scope refers to all the work involved in creating the products of the project and the processes used to create them.
Deliverables are only product-related, such as a piece of hardware or software.
False;
can also be process-related
Project scope management includes the processes involved in defining and controlling what is or is not included in a project.
The scope management plan can be informal and broad or formal and detailed, based on the needs of the project.
The project’s size, complexity, importance, and other factors do not affect how much effort is spent on collecting requirements for scope planning.
Information from the project charter provides a basis for further defining the project scope.
Project scope statements must include the
project boundaries, constraints, and assumptions.
False;
not a must, just Helpful
The scope of a project is clear and specific from the start.
False;
it becomes more clear
and specific with time
Many information technology projects also require detailed functional and design specifications for developing software, which also should be referenced in the detailed scope statement.
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.
The project scope statement, stakeholder requirements documentation, and organizational process assets are the primary inputs for creating a WBS.
The scope baseline in a WBS consists of the requirements documentation and enterprise environmental factors.
False;
includes approved project scope
The WBS is organized solely around project phases
False;
around project products, project phases, or the project management process groups
A work package represents one component of the product that the project aims to deliver.
False;
a task at the lowest level of the WBS; represents the level of work that the project manager monitors and controls
A work package must always represent less than 80 hours of work.
False;
represent work completed in one month or more
The tasks in a WBS must be developed as a sequential list of steps.
False;
he tasks do not have to be developed as a sequential list of steps
The executing tasks of the WBS remain constant from project to project.
False;
vary the most from project to project
Many organizations provide different guidelines and templates for developing WBSs.
Mind mapping allows people to write and even draw pictures of ideas in a nonlinear format.
The format of the WBS dictionary is essentially the same for all projects.
False;
each WBS item, dictionary varies on project needs
A unit of work should appear at only one place in the WBS.
Scope creep if not managed well can lead to the failure of information technology projects.
The term ______ describes a product produced as part of a project.
the work involved in creating the products and the processes used to create them.
_____ involves defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them.
_____ 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.
_____ 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.
Creating the WBS is a subprocess associated with the _____ process in project scope management.
The ______ documents how project needs will be analyzed, documented, and managed.
requirements management plan
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(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
A(n) _____ is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project.
The main technique used in creating a WBS is _____, which involves subdividing project deliverables into smaller pieces.
A(n) ____ is a task at the lowest level of the WBS.
The _____ should list and describe all of the deliverables required for the project.
In the _____ approach for constructing a WBS, you use a similar project’s WBS as a starting point.
The _____ approach for constructing a WBS involves refining the work into greater and greater levels of detail.
The _____ approach for constructing a WBS starts with the largest items of the project and breaks them into subordinate items.
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.
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.
Which of the following is recommended for the creation of a good WBS?
A unit of work should appear at only one place in the WBS.
the tendency for project scope to keep getting bigger and bigger.
_____ involves formal acceptance of the completed project scope by the stakeholders.
_____ refers to the difference between planned and actual performance.
_____ refers to the process of developing a working replica of the system or some aspect of the system.
_____ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them.
_____ 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.
JAD(Joint Application Design)