PM Chapter 5

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.

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.

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.

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.

FALSE The project's size, complexity, importance, and other factors affect how much effort is spent on collecting requirements.

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.

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.

FALSE As time progresses, the scope of a project should become more clear and specific.

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

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.

TRUE The project scope management plan, scope statement, requirements documentation, enterprise environmental factors, and organizational process assets are the primary inputs for creating a WBS.

FALSE The scope baseline includes the approved project scope statement and its associated WBS and WBS dictionary.

FALSE A project team often organizes the WBS around project products, project phases, or the project management process groups.

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.

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.

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.

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.

TRUE Many organizations provide guidelines and templates for developing WBSs, as well as examples of WBSs from past projects. Microsoft Project 2010 comes with several templates, and more are available on Microsoft's Web site and other sites.

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.

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.

: 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.

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.

C Thee term deliverable describes a product created as part of a project. Deliverables can be product related, such as a piece of hardware or software, or process-related, such as a planning document or meeting minutes.

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

A Collecting requirements involves defining and documenting the features and functions of the products for the project as well as the processes used for creating them. The project team creates requirements documentation and a requirements traceability matrix as outputs of the requirements collection process.

B Defining scope involves reviewing the scope management plan, 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.

D Validating scope involves formalizing acceptance of the project deliverables. Key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables during this process.

A Creating the WBS is a subprocess associated with the planning process of the project scope management.

B The requirements management plan documents how project requirements will be analyzed, documented, and managed.

B Benchmarking, or generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization, can be used to collect requirements.

A A requirements traceability matrix (RTM) is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed.

D After collecting requirements and defining scope, the next step in project scope management is to create a work breakdown structure. A work breakdown structure (WBS) is a deliverable oriented grouping of the work involved in a project that defines its total scope

C The main tool or technique involved in creating a WBS is decomposition—that is, subdividing project deliverables into smaller pieces.

D A work package is a task at the lowest level of the WBS.

B The scope statement should list and describe all of the deliverables required for the project. It is very important to ensure consistency between the project charter, scope statement, WBS, and Gantt chart to define the scope of the project accurately.

D A method for constructing a WBS is the analogy approach. In the analogy approach, you use a similar project's WBS as a starting point.

C To use the top-down approach, start with the largest items of the project and break them into subordinate items. This process involves refining the work into greater and greater levels of detail.

C To use the top-down approach, start with the largest items of the project and break them into subordinate items.The top-down approach is best suited to project managers who have vast technical insight and a big-picture perspective.

B 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.

ANS: D Mind mapping is a technique that 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, mind mapping allows people to write and even draw pictures of ideas in a nonlinear format.

B Some basic principles apply to creating any good WBS and its WBS dictionary. Firstly, a unit of work should appear at only one place in the WBS. The work content of a WBS item is the sum of the WBS items below it.

A Scope creep refers to the tendency for project scope to keep getting bigger and bigger.

A Scope validation involves formal acceptance of the completed project deliverables. This acceptance is often achieved by a customer inspection and then sign-off on key deliverables.

B Variance is the difference between planned and actual performance

A Prototyping involves developing a working replica of the system or some aspect of the system.

D Use case modeling is a process for identifying and modeling business events, who initiated them, and how the system should respond to them. It is an effective tool for understanding requirements of information systems.

B Joint Application Design (JAD) 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.

ANS: Project scope management

ANS: Scope

ANS: scope definition

ANS: WBS work breakdown structure work breakdown structure (WBS) WBS (work breakdown structure)

ANS: Requirements

ANS: requirements traceability matrix requirements traceability matrix (RTM) RTM

ANS: project scope statement

ANS: WBS work breakdown structure

ANS: decomposition

ANS: scope baseline

ANS: summary

ANS: task

ANS: lowest

ANS: guidelines

ANS: bottom-up

ANS: Mind mapping

ANS: WBS dictionary

ANS: Scope creep

ANS: inspection

ANS: Scope control

ANS: Variance

ANS: Prototyping

ANS: Use case modeling