Develop a scope management plan that describes in writing how the project scope will be defined, validated, and controlled Procedure.

Project scope

Product Range

The process of identifying, documenting, and managing the needs and requirements of stakeholders to achieve project objectives

Business needs

Stakeholder needs

Solution requirements

Transition needs

Project requirements

quality requirements

Interview

focus group

guided seminar

Group innovation technology

group decision making techniques

Questionnaire

observe

prototype method

Benchmarking

System interaction diagram

File analysis

Business needs

Stakeholder needs

Solution requirements

Project requirements

Transition needs

Assumptions, dependencies, constraints

Includes all activities that maintain requirements consistency and accuracy during product development, including controlling requirements baselines, keeping project plans consistent with requirements, controlling version status of individual requirements and requirements documents, managing connections between requirements and contact chains, or Manage dependencies between individual requirements and other deliverables of the project, tracking the status of requirements in the baseline

demand baseline

Requirements acquisition

demand analysis

Requirements definition

Requirements verification

Defining scope is the process of formulating detailed descriptions of projects and products. Its main function is to clarify which of the collected requirements will be included in the project scope and which ones will be excluded from the project scope, thereby clarifying the boundaries of products, services or results.

expert judgment

product analysis

Alternative generation

guided seminar

Product range description

Acceptance Criteria

Deliverables

Project Exclusions

Constraints

Assumptions

effect

Break down project deliverables and project work into smaller, more manageable component process

Marks the formal completion of a deliverable or phase. Important checkpoints are milestones, important milestones are baselines

≥8 hours, ≤80 hours

A control account includes several work packages, but a work package only belongs to one control account

It refers to the WBS component under the control account where the work content is known but detailed progress activities are lacking.

Includes account code identification, work description, assumptions and constraints, responsible person or organizational unit, schedule milestones, related schedule activities, required resources, cost estimates, quality requirements, acceptance criteria, technical references, and agreement information

Identify and analyze deliverables and related work

Determine the structure and arrangement of the WBS

Decomposition layer by layer from top to bottom

Develop and assign identification codes to WBS components

Verify that the level of decomposition of deliverables is appropriate

WBS must be deliverable oriented

The WBS must fit within the scope of the project

The underlying layer of the WBS should support planning and control

There must be one person, and only one person, responsible for the elements in the WBS

WBS guidance. As a guideline rather than a principle, WBS should be controlled at 4 to 6 layers

The WBS should include project management work as well as subcontracted work.

The preparation of WBS requires the participation of all (main) project stakeholders and the participation of project team members.

WBS is not static

The process of formal acceptance of completed deliverables by project stakeholders

examine

group decision making techniques

Determine when scope validation is needed

Identify what inputs are needed for scoping validation

Determine the formally accepted criteria and elements for scoping

Determine the organizational steps for a scoping meeting

Organization scope confirmation meeting

Validation scope emphasizes the acceptance of deliverables; quality control emphasizes the correctness of deliverables;

Quality control is usually carried out before the scope is confirmed, or at the same time; the scope is usually confirmed at the end of the stage;

Quality control is an internal inspection; the scope is confirmed and the deliverables are accepted by the project stakeholders;

Scope confirmation emphasizes verification and acceptance of deliverables; closing emphasizes the process of ending the project or phase.

Confirmation scope emphasizes acceptance of deliverables; closing emphasizes acceptance of products

Influence the factors that lead to scope changes and try to make these factors develop in a favorable direction

Determine whether a scope change has occurred

Manage actual changes when scope changes occur, ensuring that all requested changes are processed in accordance with the project's overall change control process