MindMap Gallery 5. Project scope management
5. Project scope management, including 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.
Edited at 2023-05-26 00:08:24One Hundred Years of Solitude is the masterpiece of Gabriel Garcia Marquez. Reading this book begins with making sense of the characters' relationships, which are centered on the Buendía family and tells the story of the family's prosperity and decline, internal relationships and political struggles, self-mixing and rebirth over the course of a hundred years.
One Hundred Years of Solitude is the masterpiece of Gabriel Garcia Marquez. Reading this book begins with making sense of the characters' relationships, which are centered on the Buendía family and tells the story of the family's prosperity and decline, internal relationships and political struggles, self-mixing and rebirth over the course of a hundred years.
Project management is the process of applying specialized knowledge, skills, tools, and methods to project activities so that the project can achieve or exceed the set needs and expectations within the constraints of limited resources. This diagram provides a comprehensive overview of the 8 components of the project management process and can be used as a generic template for direct application.
One Hundred Years of Solitude is the masterpiece of Gabriel Garcia Marquez. Reading this book begins with making sense of the characters' relationships, which are centered on the Buendía family and tells the story of the family's prosperity and decline, internal relationships and political struggles, self-mixing and rebirth over the course of a hundred years.
One Hundred Years of Solitude is the masterpiece of Gabriel Garcia Marquez. Reading this book begins with making sense of the characters' relationships, which are centered on the Buendía family and tells the story of the family's prosperity and decline, internal relationships and political struggles, self-mixing and rebirth over the course of a hundred years.
Project management is the process of applying specialized knowledge, skills, tools, and methods to project activities so that the project can achieve or exceed the set needs and expectations within the constraints of limited resources. This diagram provides a comprehensive overview of the 8 components of the project management process and can be used as a generic template for direct application.
5. Project scope management
Preface Overview
definition
Including the various processes that ensure the project does, and only does, all the work required to successfully complete 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
include
Develop detailed scope statement
How to create a WBS from a detailed project scope statement
Maintain and approve WBS
How to formally confirm and accept the deliverables of a completed project
How to request changes to a detailed project scope statement
"scope" definition
Product scope (project requirement scope)
The features and functions of a product, service or result
Product scope completion should be measured against product requirements
Project scope
Work that must be done to deliver a product, service, or result with specified features and functionality
Completion of project scope should be measured against the project management plan (see 4.2.3.1)
Predictive vs Agile Scope
Scope Creep
Refers to the gradual expansion of the scope of uncontrolled projects
The result of scope creep is gold plating, which is extra work. Project Management Against Gold Plating
1. Planning scope management (Planning Process Group)
enter
Project Charter
project management plan
quality management plan
Project life cycle description
development method
business environment factors
organizational process assets
Tools & Techniques
expert judgment
data analysis
Alternatives analysis
Meeting
output
scope management plan
demand management plan
main effect
Create a scope management plan that describes in writing the process of how the project scope will be defined, validated, and controlled, providing guidance and direction on how the scope will be managed throughout the project
Data flow diagram
See P134
2. Collect requirements (Planning Process Group)
enter
Project Charter
project management plan
scope management plan
demand management plan
Stakeholder Engagement Plan
project files
Hypothetical log
Lessons Learned Register
risk register
business documents
business case
Benefit Management Plan
protocol
business environment factors
organizational process assets
Tools & Techniques
expert judgment
data collection
Brainstorming
Brainstorming is a technique used to generate and gather multiple ideas for project requirements and product requirements. (more creative)
Interview
focus group
Focus groups gather predetermined stakeholders and subject matter experts to understand their expectations and attitudes toward the product, service, or outcome in question. (The focus of the discussion, intense)
Questionnaire
Benchmarking
Benchmarking compares actual or planned products, processes, and practices with the practices of other comparable organizations in order to identify best practices, formulate suggestions for improvement, and provide a basis for performance appraisal.
data analysis
Text Analysis
decision making
vote
unanimously agreed
Most agree
Decisions can be made with the support of more than 50% of the group.
A relative majority agrees
Decisions are made based on the opinion of a relative majority of the group, even if majority support is not obtained.
Usually used when there are more than two candidates.
Multi-criteria decision analysis
autocratic decision making
Data performance
Affinity diagram
A technique used to group large numbers of ideas for further review and analysis. (After brainstorming)
mind Mapping
Interpersonal and team skills
nominal group technique
The nominal group technique is a technique used to facilitate brainstorming by ranking the most useful ideas by voting for further brainstorming or prioritization.
Observe and communicate
guide
situation
Joint Application Design or Development (JAD)
JAD conference is suitable for [software development industry]
Quality Function Deployment (QFD)
[Manufacturing industry] uses QFD as a guidance skill to help determine the key characteristics of new products.
user stories
Facilitation is used in conjunction with topical workshops to bring key stakeholders together to define product requirements. (reach a consensus goal)
System interaction diagram
A visual depiction of the product scope that shows business systems and how they interact with people and other systems
prototype method
The prototype method supports the concept of progressive detailing and requires an iterative process from model creation, user experience, feedback collection to prototype modification.
Storyboard
Storyboarding is a prototyping technique that illustrates a sequence or navigation path through a series of images or diagrams.
output
requirements document
Requirements Tracking Matrix RTM
definition
A requirements tracking matrix is a table that connects requirements to their sources so that requirements can be tracked throughout the project life cycle.
include
Business needs, opportunities, goals and objectives
Project Objectives
Project Scope and WBS Deliverables
product design
product development
Test strategies and test scenarios
High-level requirements to detailed requirements
Example
branch topic
main effect
Lay the foundation for defining and managing project scope, including product scope
Data flow diagram
See P139
3. Define scope (Planning Process Group)
enter
Project Charter
project management plan
scope management plan
project files
Hypothetical log
requirements document
risk register
business environment factors
organizational process assets
Tools & Techniques
expert judgment
data analysis
Alternatives analysis
decision making
Multi-criteria decision analysis
Interpersonal and team skills
guide
situation
Joint Application Design or Development (JAD)
Quality Function Deployment (QFD)
user stories
product analysis
definition
Product analysis can be used to define products and services and involves asking and answering questions about a product or service to describe the purpose, characteristics, and other aspects of the product to be delivered.
include
product breakdown
demand analysis
system analysis
Systems Engineering
Value Engineering
VE=F/C (F: function, C: cost. Both F and C can be changed to maximize VE)
Value Analysis
VA=F/C (F: function, C: cost. F cannot be changed, C is reduced, and pursuit of maximization is pursued)
output
project scope statement
include
Product range description
Deliverables
Acceptance Criteria
Project Exclusions
Project file updates
Hypothetical log
requirements document
Requirements Tracking Matrix
Interested Party Register
main effect
Lays the foundation for defining and managing project scope, including product scope. Describes the boundaries and acceptance criteria for products, services, or results.
Data flow diagram
See P151
Project charter vs project scope statement
See picture
4. Create WBS (Planning Process Group)
enter
project management plan
scope management plan
project files
project scope statement
requirements document
business environment factors
organizational process assets
Tools & Techniques
expert judgment
break down
definition
1. Decomposition is a technique that progressively divides the project scope and project deliverables into smaller, more manageable components; 2. A work package is the lowest level of work in the WBS for which cost and duration can be estimated and managed.
Decomposition steps
1. Identify and analyze deliverables and related work
2. Determine the structure and arrangement method of WBS;
3. Detailed and decomposed layer by layer from top to bottom;
4. Develop and assign identification codes to WBS components;
5. Verify whether the degree of decomposition of deliverables is appropriate.
Decomposition method
1. Use each stage of the project life cycle as the second level of decomposition, and put the products and project deliverables on the third level.
Example
2. Use main deliverables as the second level of decomposition
Example
output
Scope Baseline
project scope statement
WBS
work package
The lowest level of the WBS is the work package with a unique identification number.
These identification numbers provide a hierarchical structure for layer-by-layer aggregation of cost, schedule, and resource information to form account codes.
Each work package is part of a control account, which is a management control point. At this control point, scope, budget, and schedule are integrated and compared to earned value to measure performance.
A control account owns two or more work packages, but each work package is associated with only one control account
planning package
A control account can contain one or more planning packages, which are work breakdown structure components that are lower than the control account but higher than the work packages.
WBS Dictionary
A WBS dictionary is a document that details deliverables, activities, and progress information for each component in the WBS
Project file updates
Hypothetical log
requirements document
main effect
Is the process of breaking down project deliverables and project work into smaller, more manageable components. Provides a structure for what is to be delivered, which is done only once or only at predefined points in the project
Data flow diagram
See P156
5. Confirm scope (Monitoring Process Group)
enter
project management plan
scope management plan
demand management plan
Scope Baseline
project files
Lessons Learned Register
quality report
requirements document
Requirements Tracking Matrix
Verified deliverables
job performance data
Tools & Techniques
examine
decision making
vote
output
Deliverables for acceptance
job performance information
Requirements change
Project file updates
Lessons Learned Register
requirements document
Requirements Tracking Matrix
main effect
Is the process of confirming scope and formally accepting completed project deliverables. The main function of this process is to make the acceptance process objective; at the same time, by confirming each deliverable, it increases the possibility of acceptance of the final product, service or result.
Data flow diagram
See P164
Confirm scope VS control quality
Development order
Usually, quality control comes first and scope confirmation comes last; sometimes, they can also be carried out at the same time.
focus
Confirming scope is different from controlling quality. The former focuses on the [acceptability] of the deliverables, while the latter focuses on the [correctness] of the deliverables (meeting quality requirements).
interested parties
The "verification" in the quality control process, which is called Verify in English, is to verify the technical correctness of the deliverables. It is a job [within the project team].
The "confirmation" in the process of confirming the scope, known as Valídate in English, is to confirm the usefulness of the deliverables in achieving the project goals and whether they can pass acceptance. It is done by [the project team inviting the project sponsor and the customer].
6. Control scope (Monitoring Process Group)
enter
project management plan
scope management plan
demand management plan
change management plan
configuration management plan
Scope Baseline
performance measurement benchmarks
project files
Lessons Learned Register
requirements document
Requirements Tracking Matrix
job performance data
organizational process assets
Tools & Techniques
data analysis
Deviation analysis
Determine the extent and reasons why project scope performance deviates from the scope baseline
trend analysis
Predict future project scope performance.
output
job performance information
Requirements change
Project Management Plan Update
scope management plan
Scope Baseline
progress baseline
cost basis
Project file updates
Lessons Learned Register
requirements document
Requirements Tracking Matrix
main effect
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 scope baseline throughout the project and is required throughout the project.
Data flow diagram
See P168
Control quality VS control scope VS confirmation scope
branch topic
Compare several files
· Project charter. There is a preliminary product scope and a preliminary project scope.
· Requirements documents. Used as a basis for further clarifying product scope and project scope.
· Requirements tracking matrix. Used to track the achievement of project scope and product scope.
· Project scope statement. These include product scope and project scope, which are used to determine scope boundaries.
· Work breakdown structure. Used to identify all deliverables that must be completed.
· Work breakdown structure dictionary. Explain the elements in the WBS.
· Scope baseline. Approved product scope and project scope.
· Purchasing Statement of Work. The scope statement of the work to be outsourced is prepared by the buyer when preparing the procurement plan.
· Contract work breakdown structure. The WBS for outsourced work shall be prepared by the seller after signing the contract and submitted to the buyer for confirmation.
Compared
branch topic