PMBOK 2012 version of project Scope management

First, the basic concept

1. What is Project scope management?

>> Project Scope Management: includes ensuring that the project is done and doing all the work to complete the project in order to successfully complete each process.

>> Project Scope Management role: define and control which work is included within the project and which work is not included within the project.

2. What does the scope contain?

>> product range: The features or functions required for a product, service, or outcome.

>> Project scope: Work to be done to deliver products, services or results with defined features and functions.

>> Note: The scope of the project also sometimes includes the product range. In general, there must be a product range, followed by the scope of the project.

3. What does the scope reference contain and what is the function?

>> consists of project scope specification, WBS (work breakdown structure) and WBS dictionary, which together form the project scope benchmark.

>> benchmarks are used as a basis for comparison in the validation scope, control range and other control processes.

>> the benchmark can only be changed by means of a formal change control program.

Ii. description of the process group

1. Planning Scope Management

>> definition: Create a scope management plan, a written description of how to define, confirm, and control the scope of each process.

>> role: Provides guidance and direction for how to manage scope throughout the project.

>> Input and output

Input tool output

Project Charter expert Judgment Scope Management plan

(the project Charter provides high-level product descriptions and product features, with product features derived from the project work instructions!) )

Project Management Plan meeting requirements management plan

Organizational Process Assets

Business environment factors

>> Key Notes

1. What content does the scope management plan contain?

The > Scope Management plan is the primary input for developing project management plans and scope management other processes. The scope management plan mainly includes:

How to make a detailed project scope statement

How to build a WBS based on a project scope statement

How to maintain and approve a WBS

How to formally accept completed project deliverables

How to deal with the change of the project scope statement

2. What does the requirements management plan contain?

> is part of a project management plan that describes how to analyze, document, and manage requirements. There is a great impact between phases and phases on how to manage requirements,

The relationship between phases and phases should therefore be documented in the requirements management plan.

How to plan, track, and report on various requirements activities

How to configure management activities

The process of prioritizing requirements

Reasons for the use of these indicators in product measurement indicators

To reflect which requirements attributes will be included in the demand tracking matrix

2. Collect demand

　　>> definition: The process of identifying, documenting, and managing stakeholder needs and needs in order to achieve project objectives.

>> role: Lay the groundwork for defining and managing the scope of the project, including the product range.

>> Input and output

Input tool output

Scope Management plan Interview requirements file

Demand management Plan focus group requirements Tracking matrix

Organizational process Asset-guided seminars

Stakeholder Management Plan Observation

Stakeholder Register Questionnaire Survey

Group Decision Technology

Group Innovation Technology

Prototype method

Benchmark comparison

File analysis

System interaction Diagram

>> Key Notes

　　　　1. Tool description

> interview: It can be one-to-many or a couple, usually used to collect confidential information

> Guided Workshops: Important techniques for defining cross-functional requirements and reconciling stakeholder differences. For example: JAD (Joint application design/development) and QFD (Quality function expansion)

The QFD workshop is often used to identify key features of new products .

> Group Decision Technology: Consensus (Delphi Technology), majority consent, relative majority consent, dictatorship

> Group Innovation Technology: Brainstorming, mind Mapping, affinity mapping, nominal group technology, multi-criteria decision analysis, etc.

> Survey: Suitable for the audience diversification, need to complete the survey quickly, the respondents geographically dispersed or carry out statistical analysis.

2. Definition of demand and importance of demand

> Requirements are the competencies or conditions that a project (product, service or outcome) must meet in accordance with a specific agreement or other mandatory specification.

Requirements are the basis of WBS, cost, schedule, and quality planning, and sometimes may be the basis for procurement work.

3. Requirement Documents

> Describes how a variety of single requirements will be met and the business requirements associated with the project. Only a clear, traceable, complete, coordinated, and mutually agreed-on requirement can be used as a benchmark.

> Content:

Business requirements, stakeholder needs, solution requirements, project requirements, transition requirements, and requirements-related constraints, assumptions, and dependencies.

3. Scope of definition

4. Create a WBS

5. Scope of Confirmation

6. Control Range

Iii. Summary of Project scope management

PMBOK 2012 version of project Scope management