Project Management Chapter 5

Work Breakdown Structure (WBS)

A deliverable-oriented grouping of the work involved in a project that defines the total scope of the project

WBS Dictionary

A document that describes detailed information about each WBS item

Deliverable

A product produced as part of a project, such as hardware or software, planning documents, or meeting minutes

Requirements Traceability Matrix (RTM)

A table that lists requirements, various attributes of each requirement, and the status of the requirements to ensure that all requirements are addressed

Work Package

A task at the lowest level of the WBS

Mind-Mapping Approach

A technique that uses branches radiating out from a core idea to structure thoughts and ideas

Requirements

Conditions or capabilities that must be met by the project or present in the product, service, or result to satisfy an agreement of other formally imposed specification

Controlling Scope

Controlling changes to project scope throughout the life of the project

Collecting Requirements

Defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them

Requirement Development Categories

Elicitation, Analysis, Specification, and Validation

Validating Scope

Formalizing acceptance of the project deliverables

Benchmarking

Generating ideas by comparing specific project practices or product characteristics to those of other project or products inside or outside the performing organization, can also be used to collect requirements

Project Scope Management

Includes the processes involved in defining and controlling what is or is not included in a project

Goals of the scope are to

Influence the factors that cause scope changes, assure changes are processed according to procedures developed as part of integrated change control, and manage changes when they occur

Scope

Refers to all the work involved in creating the products of the project and the process used to create them

Analogy Approach

Review WBSs of similar projects and tailor your project

Project Scope Statement

Should Include at least one project 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. Should reference supporting documents, such as product specifications.

Top-Down Approach

Start with the largest items of the project and break them down

Bottom-Up Approach

Start with the specific tasks and roll them up

Variance

The Difference between planned and actual performance

A WBS is

a foundation document that provides the basis for planning and managing project schedules, costs, resources, and changes

Scope control involves

controlling changes to the project scope

Planning scope

determining how the project's scope and requirements will be managed

Requirements Management Plan

documents how project requirements will be analyzed, documented, and managed

Scope Management Plan Contents

how to prepare a detailed project scope statement, how to create a WBS, how to maintain and approve the WBS, how to obtain formal acceptance of the completed project deliverables, how to control requests for changes to the project scope

Scope Baseline

includes the approved project scope statement and its associated WBS and WBS dictionary

Scope Validation

involves formal acceptance of the completed project deliverables

Defining scope

reviewing the project charter, requirements documents, and organizational process assets to create a scope statement

Decomposition

subdividing project deliverables into smaller pieces

Creating a WBS

subdividing the major project deliverables into smaller, more manageable components

The scope management plan is a

subsidiary part of the project management plan

Project scope management includes

the processes involved in defining and controlling what is or is not included in a project

The project team uses expert judgement and meetings to develop two important outputs:

the scope managements plan and the requirements management plan