The project scope management involves ensuring that the project does and only does all the work required to successfully complete the various processes of the project.
managing project scope is primarily about defining and controlling what work should be included in the project and what should not be included in the project.
The project scope management process includes:
- planning scope management — the process of creating a scope management plan to document how project scopes and product scopes are defined, validated, and controlled.
- gathering requirements — the process of identifying, documenting, and managing the needs and needs of interested parties to achieve project goals.
- define scope — the process of developing detailed descriptions of projects and products.
- Create a WBS—The process of breaking down project deliverables and project work into smaller, more manageable components.
- scope of validation — the process of formally accepting the completed project deliverables.
- scope of control — supervise the scope status of projects and products, and manage the process of changing the scope benchmark
the core concept of project scope management
product range: the characteristics and functionality of a product, service or outcome.
scope of the project: the work that must be done to deliver a product, service or outcome with the specified characteristics and functionality. the scope of the project sometimes also includes the product scope.
[1] Plan for scope management
planning scope management is the process of creating a scope management plan to document how project scopes and product scopes are defined, validated, and controlled. the main role of this process is to provide guidance and direction on how to manage the scope throughout the project. this process occurs only once or only at predefined points in the project.
1.1 scope management plan
a scope management plan is an integral part of a project or set management plan that describes how the project scope will be defined, developed, monitored, controlled, and validated. developing a scope management plan and refining the scope of a project begins with an analysis of the information in the project charter, approved subplans in the project management plan, historical information in the organization's process assets, and relevant business environment factors
the scope management plan specifies the management process that will be used for: 1. develop a project scope statement; 2. create a wbs based on a detailed project scope statement; 3. determine how to approve and maintain a scope benchmark; and 4. formally accept the completed project deliverables
1.2 project management plan
project management program components include (but are not limited to):
1. quality management plan: the way in which the organization's quality policies, methods and standards are implemented in a project affects the way the project and product scope are managed.
2. project life cycle description. the project lifecycle defines the series of phases that a project goes through from inception to completion.
3. development methods. the development methodology defines whether the project takes a waterfall, iterative, adaptive, agile, or hybrid approach to development.
1.3 requirements management plan
a requirements management plan is an integral part of a project management plan that describes how project and product requirements will be analyzed, documented, and managed.
The main elements of a requirements management plan include (but are not limited to):
1. how to plan, track and report on various demand activities;
2. configure management activities, such as how to initiate changes, how to analyze their impact, how to trace, track and report, and change approval authority;
3. requirements prioritization process;
4. measure the indicators and the reasons for using them;
5. reflect which requirements attributes will be included in the tracking structure of the tracking matrix
[2] Gather requirements
Gathering requirements is the process of identifying, documenting, and managing the needs and needs of interested parties to achieve goals. the main role of this process is to lay the foundation for defining the product scope and the scope of the project, and to do it only once or only at the predefined points of the project.
a requirements tracking matrix is a table that connects product requirements from their sources to deliverables that meet the requirements. using a requirements tracking matrix to link each requirement to a business goal or project goal can help ensure that each requirement has business value.
record the relevant properties of each requirement in the requirements tracking matrix, which help clarify the key information for each requirement. typical attributes recorded in the requirements tracking matrix include a unique identifier, a text description of the requirement, a reason for including the requirement, owner, source, priority, version, current status (such as in progress, canceled, deferred, newly added, approved, assigned, and completed), and status date.
[3] Define the scope
The scope of definition is the process of developing a detailed description of the project and product, the main role of which is to describe the boundaries and acceptance criteria of the product, service or outcome.
[4] Create a WBS
Creating a work breakdown structure (wbs) is the process of breaking down project deliverables and project work into smaller, more manageable components. the main role of this process is to provide an architecture for what is to be delivered, either once or only at predefined points in the project.
4.1 WBS
wbs is a hierarchical breakdown of the entire scope of work that a project team needs to implement to achieve the project goals and create the desired deliverables. wbs organizes and defines the overall scope of the project, which represents the work specified in the approved current project scope specification.
The components of the lowest level of wbs are called work packages, which include planned work. work packages categorize related activities in order to schedule work, estimate, monitor and control.
4.2 decomposition
decomposition is a technique that progressively divides the scope of a project and project deliverables into smaller, more manageable components; work packages are the lowest-level work of the wbs that estimates and manages their costs and duration. the degree of decomposition depends on the degree of control required to enable efficient management of the project; the level of detail of the work package varies depending on the size and complexity of the project. to break down the entire project work into work packages, the following activities are often required:
1. Identify and analyze deliverables and related work; 2. Determine the structure and orchestration method of WBS; 3. Refine the decomposition layer by layer from top to bottom; 4. Develop and assign identification codes for WBS components; 5. Verify that the degree of decomposition of deliverables is appropriate.
4.3 WBS DICTIONARY
The wbs dictionary is a file that details deliverables, activities, and progress information for each component in the wbs, and the wbs dictionary provides support for the wbs, where much of the information is created by other processes and then added to the dictionary at a later stage.
WBS dictionary content may include, but is not limited to, the following
job description; assumptions and constraints; responsible organization; milestones; related schedule activities; resources required; cost estimates; quality requirements; acceptance criteria; technical references; agreement information.
[5] Confirm the scope
validation scope is the process of formally accepting the completed project deliverables. the primary role of this process is to make the acceptance process objective and to increase the likelihood of acceptance of the final product, service or outcome by confirming each deliverable.
the verified deliverables output from the quality control process are reviewed by the customer or sponsor to confirm that these deliverables have been successfully completed and formally accepted. the validation and final acceptance of deliverables in this process needs to be based on outputs (e.g., requirements documents or scope benchmarks) obtained from the planning processes in the knowledge areas managed by the project scope, as well as work performance data obtained from the implementation processes in other knowledge areas.
[6] Control range
scope of control is the process of supervising the scope status of projects and products and managing changes to the scope baseline. the main role of this process is to maintain a scope baseline throughout the project and needs to be carried out throughout the project.
performance measurement benchmarks: when using earned value analysis, compare performance measurement benchmarks to actual results to determine whether changes are necessary and corrective actions or preventive actions are taken
deviation analysis: deviation analysis is used to compare a benchmark to actual results to determine whether deviations are within a critical value interval or whether corrective or preventive actions are necessary
Trend analysis: trend analysis is designed to review how a project's performance has changed over time to determine whether performance is improving or deteriorating
No comments:
Post a Comment