A unit of work should appear at only one place in the WBS.
True (A basic principle of creating a good WBS and its WBS dictionary is that a unit of work should appear at only one place in the WBS.)
A work package must always represent less than 80 hours of work.
False (A work package represents the level of work that the project manager monitors and controls. If a project has a relatively short time frame and requires weekly progress reports, a work package might represent work completed in one week or less. If a project has a very long time frame and requires quarterly progress reports, a work package might represent work completed in one month or more.)
A work package represents one component of the product that the project aims to deliver.
False (A work package is a task at the lowest level of the WBS. It represents the level of work that the project manager monitors and controls.)
Creating the WBS is a subprocess associated with which process in project scope management?
planning (Creating the WBS is a subprocess associated with the planning process of the project scope management.)
Deliverables are only product-related, such as a piece of hardware or software.
False (Deliverables can be product-related, such as a piece of hardware or software, or process-related, such as a planning document or meeting minutes.)
During which approach do 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?
bottom-up (In the bottom-up approach, team members first identify as many specific tasks related to the project as possible. They then aggregate the specific tasks and organize them into summary activities, or higher levels in the WBS. Project managers often use the bottom-up approach for projects that represent entirely new systems or approaches to doing a job, or to help create buy-in and synergy with a project team.)
Given the project management software that is available, it is relatively easy to create a good WBS.
False (It is very difficult to create a good WBS. In order to do so, you must understand the project and its scope and incorporate the needs and knowledge of the stakeholders.)
Information from the project charter provides a basis for further defining the project scope.
True (The charter describes the high-level scope, time, and cost goals for the project objectives and success criteria, a general approach to accomplishing the project’s goals, and the main roles and responsibilities of important project stakeholders.)
Many organizations provide different guidelines and templates for developing WBSs.
True (Many organizations provide guidelines and templates for developing WBSs, as well as examples of WBSs from past projects. Microsoft Project 2016 comes with several templates, and more are available on Microsoft’s Web site and other sites.)
Mind mapping allows people to write and even draw pictures of ideas in a nonlinear format.
True (Instead of writing down tasks in a list or immediately trying to create a structure for tasks, mind mapping allows people to write and even draw pictures of ideas in a nonlinear format. This more visual, less structured approach to defining and then grouping tasks can unlock creativity among individuals and increase participation and morale among teams.)
Mind mapping can be used for developing WBSs using which approach?
top-down or bottom-up approach (You could conduct mind mapping for an entire project by listing the project in the center of a diagram and adding branches or develop a mind-mapping diagram for each deliverable and merge them to create one large diagram for the entire project.)
Project scope management includes the processes involved in defining and controlling what is or is not included in a project.
True (Project scope management includes the processes involved in defining and controlling what work is or is not included in a project. It ensures that the project team and stakeholders have the same understanding of what products the project will produce and what processes the project team will use to produce them.)
Project scope statements must include the project boundaries, constraints, and assumptions.
False (Project scope statements should include at least a product scope description, product user acceptance criteria, and detailed information on all project deliverables. It is also helpful to document other scope-related information, such as the project boundaries, constraints, and assumptions.)
Scope creep if not managed well can lead to the failure of information technology projects.
True (Even when the project scope is fairly well defined, many IT projects suffer from scope creep—the tendency for project scope to keep getting bigger and bigger. Many IT projects fail due to scope creep.)
Scope refers to all the work involved in creating the products of the project and the processes used to create them.
True (One of the most important and most difficult aspects of project management is defining the scope of a project. Scope refers to all the work involved in creating the products of the project and the processes used to create them.)
The executing tasks of the WBS remain constant from project to project.
False (The executing tasks vary the most from project to project, but many of the tasks under the other project management process groups would be similar for all projects.)
The format of the WBS dictionary is essentially the same for all projects.
False (WBS dictionary is a document that provides detailed information about each WBS item. The format of the WBS dictionary can vary based on project needs.)
The main purpose of the WBS is to define all of the work required to complete a project.
True (The main purpose of the WBS is to define all of the work required to complete a project.)
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 (The project scope statement should reference supporting documents, such as product specifications that will affect what products are created or purchased, or corporate policies, which might affect how products or services are produced.)
The project’s size, complexity, importance, and other factors do not affect how much effort is spent on collecting requirements for scope planning.
False (The project’s size, complexity, importance, and other factors affect how much effort is spent on collecting requirements.)
The scope baseline in a WBS consists of the requirements documentation and enterprise environmental factors.
False (The scope baseline includes the approved project scope statement and its associated WBS and WBS dictionary.)
The scope management plan can be informal and broad or formal and detailed, based on the needs of the project.
True (The scope management plan is a subsidiary part of the project management plan. It can be informal and broad or formal and detailed, based on the needs of the project.)
The scope of a project is clear and specific from the start.
False (As time progresses, the scope of a project should become more clear and specific.)
The tasks in a WBS must be developed as a sequential list of steps.
False (A concern when creating a WBS is how to organize it to provide the basis for the project schedule. You should focus on what work needs to be done and how it will be done, not when it will be done. In other words, the tasks do not have to be developed as a sequential list of steps.)