The characteristics and functions of a certain product, service or achievement, and whether the product scope is completed are measured by the product requirements specification.

The scope statement defines the work and processes that must be completed to deliver products and services with specified features and functionality.

Whether the project scope is completed is measured by the project management plan, project scope statement, WBS and WBS dictionary. The project scope comes from a clear project goal or specific needs of the project investor or customer.

Project scope confirmation is the formal recognition of the project scope by project stakeholders and runs throughout the entire project life cycle.

Project scope is the only way to effectively manage demand changes. With a clear project scope, only the business processes within the scope can be analyzed to establish system functional requirements. When customer needs change, the scope can be effectively managed.

The project scope and functional requirements are not provided by the customer. The customer only knows what goals the requirements complete. The project team members obtain the functional requirements after understanding the customer analysis.

Refers to the process of defining and controlling what is and is not included in the project. This process is used to ensure that the project team and project stakeholders have a common understanding of the project products and the processes used to produce these products.

Obtain project requirements through demand development, determine the scope of the project on this basis, and conduct project scope management. Demand management manages the full life cycle of project requirements, including demand management definition, demand management process, formulating demand management plans, and managing demand. and implementation suggestions; for project requirements, they can be met step by step or in phases according to the urgency and importance of the requirements. Determining the requirements of each period will provide the basis for scope management of this period. Demand management handles changes in requirements, which will cause changes in the project scope.

Fundamental contents

5 processes

Describe how various single requirements will meet the business requirements related to the project. Only requirements that are clear, traceable, complete, coordinated with each other, and recognized by major stakeholders can be used as a baseline.

include

Describe how requirements are analyzed, documented, and managed throughout the project life cycle. Relationships between departments at each stage of the life cycle have a strong impact on how requirements are managed

include

Interviews, focus groups, guided workshops, group innovation techniques, group decision-making techniques, questionnaires, observations, prototyping

Delphi technique: A group of selected experts answer questionnaires and give feedback on the results of each round of requirements gathering. Expert responses can only be given to the moderator to maintain anonymity. Multiple controlled feedback, where experts are all equal, can avoid any individual having an undue exaggerated impact on the results.

Brainstorming: A technique used to generate and collect multiple ideas for project requirements and product requirements

Concept/mind mapping: Connect the ideas obtained from brainstorming with a simple diagram to reflect the commonalities and differences between these ideas, thereby guiding new ideas

Enterprise environmental factors, organizational process assets, project charter, preliminary project scope statement, project management plan

Expert judgment, work breakdown templates, change control forms, standards in organizational processes

scope management plan

Organizational process assets (templates), project charter, preliminary project scope statement, project scope management plan, approved change requests (occurs during the project execution phase)

Product analysis (an effective tool for projects with products as deliverables, including product decomposition, systems analysis, requirements analysis, systems engineering, value engineering analysis), alternative identification (techniques that propose different execution methods) , expert judgment method, project stakeholder analysis

Project Scope Detailed Description

change request

project management plan

After the project is decomposed, the relevant personnel can understand the project at a glance

Ensures the systematicness and integrity of the project structure (preventing work that should be done from being omitted and gilded)

Establish a complete project guarantee system

Clarify the working interface of all parties to facilitate the division and implementation of responsibilities

As a tool for schedule planning and control

Provide a basis for establishing project communication management

It is the basis and basis for the formulation of project plans and control measures.

hierarchical tree structure

tabular form

The hierarchical structure is a decomposition of the project work required to complete the project goals into small, manageable fragments, which organizes and defines all the work within the entire project scope. The lowest-level work package has clear and verifiable deliverables. , which cannot be divided logically, is the basis for schedule arrangement, cost estimation and monitoring. Each layer of WEB needs to be encoded.

Organizational process assets, project scope statement, project scope management plan, approved change requests (the WBS may need to be updated during the execution phase)

work breakdown structure template

break down

WBS coding design

Project scope statement (updated), work breakdown structure, WBS dictionary, scope baseline (the baseline is formed after the WBS is approved), project management plan, change request (change scope statement passes overall change control)

project scope statement

WBS Dictionary

project scope management plan

Deliverables

Check to achieve scope confirmation

Deliverables accepted

Change Request

Recommended corrective actions

Factors causing scope changes and requested changes are handled according to the overall project change control and managed when scope changes actually occur. Scope changes are modifications to the agreed upon WBS-defined project scope.

Reason for change

Focus

scope statement

Work breakdown structure, WBS dictionary, project scope management plan

performance report

Approved change request

job performance information

change control system

Deviation analysis

Replanning

configuration management system

Project scope statement, WBS and WBS dictionary, scope baseline, change request, approved corrective actions, organizational process assets, project management plan

Phased implementation - large projects have a wide scope, long cycle and complex business. The core business will be realized in the first phase and comprehensively promoted in the second phase.

Establish a project organizational structure including user managers, business managers, and key users - fully understand the scope of the project and avoid discrepancies

Adequate demand analysis and research--is the basis for determining the scope of the project and preparing a user demand specification

Develop a scope management plan - develop a scope statement to determine the project scope, deliverables at each stage, implementation methods to be used, and functional descriptions

Scope definition – using a top-down approach to divide WBS

Regular project meeting system-confirm project scope and results

Project weekly and monthly report system--analysis and summary of system progress

Project supervision system-supervision company participation