Wondershare EdrawMind
MindMap Gallery Chapter 5 Project Scope Management Mind Map
- 18
Chapter 5 Project Scope Management Mind Map
This is a mind map about project scope management, which includes the management of project scope, which is the corresponding definition and control of what should and should not be included in the project.
Edited at 2021-06-12 16:05:15
- bacteria
This is a mind map about bacteria, and its main contents include: overview, morphology, types, structure, reproduction, distribution, application, and expansion. The summary is comprehensive and meticulous, suitable as review materials.
- Plant asexual reproduction
This is a mind map about plant asexual reproduction, and its main contents include: concept, spore reproduction, vegetative reproduction, tissue culture, and buds. The summary is comprehensive and meticulous, suitable as review materials.
- Reproductive development of animals
This is a mind map about the reproductive development of animals, and its main contents include: insects, frogs, birds, sexual reproduction, and asexual reproduction. The summary is comprehensive and meticulous, suitable as review materials.
Chapter 5 Project Scope Management Mind Map
- bacteria
This is a mind map about bacteria, and its main contents include: overview, morphology, types, structure, reproduction, distribution, application, and expansion. The summary is comprehensive and meticulous, suitable as review materials.
- Plant asexual reproduction
This is a mind map about plant asexual reproduction, and its main contents include: concept, spore reproduction, vegetative reproduction, tissue culture, and buds. The summary is comprehensive and meticulous, suitable as review materials.
- Reproductive development of animals
This is a mind map about the reproductive development of animals, and its main contents include: insects, frogs, birds, sexual reproduction, and asexual reproduction. The summary is comprehensive and meticulous, suitable as review materials.
- Recommended to you
- Outline
Chapter 5 Project Scope Management
Preface
Scope management goals
1. What to do
2. What to do only
Don’t do less, don’t do more. Anything more has a cost.
Scope management includes
Product Range
Project scope
scope management process
Make sure everyone involved agrees on what needs to be done
Differences in management of different life cycle scopes
Quality Function Deployment QFD
1. Planning scope management
enter
Project Charter
The project charter documents the project purpose, project overview, assumptions, constraints, and high-level requirements that the project is intended to achieve.
project management plan
quality management plan
The way in which the organization's quality policies, methods, and standards are implemented on projects affects the way in which project and product scope are managed
Project life cycle description
The project life cycle defines the series of stages a project goes through from inception to completion
development method
Waterfall
Iterative
adaptive
Agile
Hybrid
business environment factors
group Culture
infrastructure
Personnel management system
market conditions
organizational process assets
policies and procedures
Knowledge base of historical information and lessons learned
Tool technology
expert judgment
Consider the opinions of individuals or groups with relevant expertise or training on the following topics:
Similar projects in the past
Industry, discipline and application area specific information.
data analysis
Alternatives analysis
This technique is used to evaluate various methods of gathering requirements, detailing project and product scope, creating the product, validating scope, and controlling scope.
Meeting
output
scope management plan
Describe how project scope is defined, developed, monitored, controlled, and validated. It is necessary to provide for the management process of the following work
Develop project scope statement
Create a WBS based on the detailed project scope statement
Determine how to approve and maintain the scope baseline
Formal acceptance of completed project deliverables
demand management plan
Describe how to analyze, document, and manage project and product requirements. The main contents include but are not limited to
How to plan, track and report on various requirements activities
Configuration management activities, such as how to initiate changes, how to analyze their impact, how to trace, track and report, and change approval permissions;
Requirements prioritization process
Metrics to measure and reasons for using them
A trace structure that reflects which requirement attributes will be included in the trace matrix.
2. Collect requirements
About requirements
Tools and techniques for gathering requirements
expert judgment
data collection
Brainstorming
Interview
focus group
The meeting theme is clear
Questionnaire
large area wide area
Benchmarking
Compare with competitors and industry leaders
data analysis
decision making
The process of determining what needs should be met and what needs should require concessions from the customer
tool
vote
Odd number of voters
three ways
1. Unanimous agreement
2. Most agree 50%
3. Relatively majority agrees
dictatorship
Multi-criteria decision-making (MCDA)
data representation technology
Group ideas for further review and analysis
mind Mapping
Integrate the ideas obtained during brainstorming into a picture to reflect the commonalities and differences between the ideas and stimulate new ideas
Interpersonal and team skills
nominal group
1. Group members should stop breathing and think independently.
2. Each takes turns writing down alternatives and opinions.
3. Take turns to state your plans and opinions
4. Group members vote on all alternatives
5. The alternative with the most votes will be selected.
6. Of course, managers still have the right to veto this plan
Observation
guided seminar
Such as expert consultation
Cross-department and cross-professional discussion with moderator
Four ways of presenting requirements
user stories
Use fixed grammar to express customer needs into a unified format. To facilitate analysis by project members. Identify it.
As a WeChat user, I hope WeChat does not limit the number of friends so that I can only use one WeChat ID.
Storyboard
Use visual scripts to confirm requirements
System interaction diagram
By analyzing and deconstructing the working patterns and processes in reality, we finally generate a development requirement for our system.
Prototype
First make a sample to confirm the customer's needs.
Sample room
prototype
Sample app
output
requirements document
Describe how various single requirements will satisfy project-related business needs
After approval by major relevant parties, it can be used as a benchmark
Requirements Tracking Matrix
The biggest role: It can faithfully record the identification, recording, and changes related to requirements that have occurred in history, so that we can track and manage them.
3. Define scope
Summary
Since all the requirements identified during the requirements collection process may not be included in the project, the scope definition process requires selecting the final project requirements from the requirements document (the output of the requirements collection process), and then formulating information about the project and its products and services. or a detailed description of the results.
enter
Project Charter
project management plan
scope management plan
project files
Hypothetical log
requirements document
risk register
The risk register documents the risks that may affect the project scope and their response strategies, such as reducing and changing the project scope, to avoid or mitigate risks.
business environment factors
group Culture
infrastructure
Personnel management system
market conditions
organizational process assets
Policies, procedures, and templates for specifying project scope statements
Project archives of past projects
Lessons learned from previous phases or projects
Tools & Techniques
expert judgment
data analysis
Alternatives analysis
Assess various methods for achieving the needs and objectives stated in the project charter.
decision making
Multi-criteria decision analysis
A technique that uses a systems analysis approach with the help of a decision matrix, with the goal of establishing various criteria such as requirements, schedule, budget, and resources to refine the project and product scope.
Interpersonal and team skills
guide
Use facilitation skills in workshops and panels to coordinate key stakeholders with different expectations or different professional backgrounds to achieve cross-functional consensus on project deliverables and project and product boundaries.
product analysis
Transform high-level product or service descriptions into meaningful deliverables.
product breakdown
demand analysis
system analysis
Systems Engineering
Value Analysis
Value Engineering
output
project scope statement
Product range description
gradually refine, gradually detail
Deliverables
Description can be detailed or omitted
Acceptance Criteria
A series of conditions that must be met before a deliverable can be accepted
Project Exclusions
Identify what is excluded from the project. Helps manage stakeholder expectations and reduce scope creep
The relationship between project scope statement and project charter
It is a process of gradual elaboration. The charter is the outline and the scope statement is the details.
Senior management and needs
High-level description in WBS, rough requirements before segmentation
Project file updates
Hypothetical log
Update the hypothesis log as more assumptions or constraints are identified through this process
requirements document
Requirements documents can be updated by adding or modifying requirements
Requirements Tracking Matrix
Updated as requirements documents are updated
Interested Party Register
If new interested parties are gathered during this process, document them
4. Create WBS
enter
project management plan
The scope management plan defines how the WBS will be created based on the project scope statement
project files
project scope statement
requirements document
business environment factors
Industry WBS standards
organizational process assets
Policies, procedures and templates for creating WBS
Project archives of past projects
Lessons learned from past projects
Tools & Techniques
expert judgment
Use to solicit input from individuals or groups with knowledge or experience of similar projects
break down
Decomposition is a technique for progressively dividing the project scope and project deliverables into smaller, more manageable components.
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
Is the level of decomposition of appropriate deliverables appropriate?
output
Project Scope Baseline
project scope statement
Include a description of the project scope, key deliverables, assumptions, and constraints.
Work breakdown structure WBS
WBS components
Subproject
control account
Select the first-level work package as the account classification method
Generally corresponds to the team, one account per team
work package
Break it down to the point where you can easily know the time, resources, and cost required for this work. Such a unit is called a work package
The lowest level unit of wbs
The minimum project manager is responsible for the work package
planning package
Work packages that cannot be evaluated during decomposition are temporarily located in planning packages.
Activity
Work packages are subdivided into activities
Correspondence execution team
Task
Activities are divided into tasks
Corresponding to individuals
WBS is the most important work in project management and is the basis for other work
is the source of the benchmark
Directly determine the scope benchmark
Schedule and cost baselines are based on scope baselines.
is the basis of the plan
presentation of work
Basis for control
Team's Guide
WBS Dictionary
For each WBS component, a document detailing deliverable activities and progress information.
A work package corresponds to a table, and all tables together are called the WBS dictionary.
Project file updates
Hypothetical log
Update the hypothesis log as more assumptions or constraints are identified through this process
requirements document
Requirements documents can be updated to reflect changes proposed and approved during this process
5. Confirmation scope
Validating scope is the process of formal acceptance of completed project deliverables. The purpose of this process is to bring objectivity to the acceptance process and to increase the likelihood of acceptance of the final product, service or result by validating each deliverable. This process should occur periodically throughout the project as needed.
Pay attention to inspection before delivery
The work of confirming with customers should be proactive and do not accumulate. Timely confirmation in batches and installments.
Every time a part of the deliverable is completed, the customer will be confirmed in a timely manner at each stage.
enter
project management plan
scope management plan
Defines how to properly accept completed deliverables
demand management plan
The requirements management plan describes how project requirements will be identified
Scope Baseline
Compare the scope baseline with actual results to determine if changes and corrective actions are necessary.
project files
Lessons Learned Register
Lessons learned early in the project can be applied to later stages to improve the efficiency and effectiveness of acceptance of deliverables
quality report
Content may include an overview of all quality assurance matters managed by the team or required to be reported, suggestions for improvements, and situations discovered during quality control. Before accepting the product. All of these need to be viewed.
The output after the control quality process has been completed is a report
requirements document
Comparing requirements with actual results determines whether changes, corrective actions, or preventive actions are necessary.
Requirements Tracking Matrix
The requirements tracking matrix contains information related to the requirements, including how the requirements were confirmed
Verified deliverables
Verified deliverables are those that have been completed and checked as correct by the control quality process.
job performance data
Work performance data may include the degree to which requirements are met, the number of inconsistencies, the severity of inconsistencies, or the number of verifications performed during a time period.
Tools & Techniques
examine
Inspection refers to activities such as measurement, review and validation to determine whether work and deliverables meet requirements and product acceptance criteria. Inspections are sometimes also called reviews, product reviews, inspections, etc.
decision making
vote
output
Deliverables for acceptance
Deliverables that meet the acceptance criteria should be formally signed off by the client or sponsor. Formal documentation should be obtained from the client or sponsor demonstrating formal acceptance of the project deliverables by the relevant parties.
job performance information
Work performance data is used to derive work performance information, such as which deliverables have been accepted and which have failed and why. This information should be recorded and passed on to relevant parties.
change request
Deliverables that have been completed but have not passed formal acceptance and the reasons for failure should be recorded. Change requests and defect remediation may be required for these deliverables. Change requests should be reviewed and handled by implementing the overall change control process.
Project file updates
Lessons Learned Register
Update the Lessons Learned Register to document challenges encountered, how the challenge could have been avoided, and good deliverable acceptance methods.
requirements document
Document the actual acceptance structure and update the requirements document. Special attention needs to be paid to situations where the actual results are better than the original requirements, or where the original requirements have been abandoned.
Requirements Tracking Matrix
Update the requirements tracking matrix based on the acceptance results, including the acceptance methods used and the results of their use.
6. Control scope
Controlling scope is the process of monitoring the scope status of projects and products and managing changes to the scope baseline. The primary purpose of this process is to maintain the project scope throughout the project and is required throughout the project.
Controlling project scope ensures that all change requests, recommended corrective actions, or preventive actions are processed through the implementation of the overall change control process.
As changes occur, the scope of control process is also used to manage those changes.
The control scope process should be conducted in coordination with other control processes.
Uncontrolled expansion of product or project scope (without corresponding adjustments in time, cost, and resources) is called scope creep.
How to prevent scope creep
If possible, leave as many openings as possible to allow for the possibility of making changes.
Scope creep: refers to the scope being changed without going through the overall change control process, thus producing undesirable effects.
Range gold plating:
Be cautious and stable when plating gold
initiative
range crawl
Customers keep changing,
passive
None have gone through the scope change process.
how to avoid
The reason for gold plating
1. Please customers
2. Configuration obsessive-compulsive disorder
Ivory Chopsticks Comprehensive Certificate
3. Show off your talents
to avoid
The added functions must be absolutely stable, otherwise they will not be added.
range crawl
A disciplined change process is a firewall that protects the project manager and project team.
Change is inevitable, so some form of change control must be enforced on every project.
enter
project management plan
scope management plan
Documented how to control project and product scope
demand management plan
Documented how to manage project requirements
change management plan
Defined process for managing project changes
configuration management plan
Defines which configuration items are configuration items, which configuration items require formal change control, and the change control process for these configuration items.
Scope Baseline
Use the scope baseline to compare with actual results. To determine whether changes, corrective actions, or preventive actions are necessary.
performance measurement benchmarks
When using earned value analysis, performance measurement baselines are compared to actual results to determine whether changes, corrective actions, or preventive actions are necessary.
project documents
Lessons Learned Register
requirements document
Used to identify any deviations from the agreed project or product scope
Requirements Tracking Matrix
The requirements tracking matrix helps to explore the impact of any changes or any deviations from the scope baseline on the project objectives. It also provides the status of controlled requirements.
job performance data
May include the number of change requests received, the number of change requests accepted, and the number of deliverables verified, validated, and completed.
RAM Responsibility Assignment Matrix
There is only one person in charge