MindMap Gallery Chapter 5 Project Scope Management
Chapter 5 summarizes the key knowledge of project scope management, including planning scope management, defining scope, creating WBS, confirming scope, controlling scope, etc.
Edited at 2022-05-30 20:42:50One 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.
project scope management
0. Concept
Project scope management includes the process of doing and only doing all the work required to successfully complete the project.
scope
Product Range
The features and functions of a product, service or result
Project scope
The work that must be done to deliver a product, service, or result with specified features and functionality. Project scope sometimes also includes product scope.
product demand
Refers to the conditions or capabilities that products, services or results must have according to specific agreements or other mandatory specifications.
1. Planning scope management
definition
It is the process of creating a scope management plan in order to record how to define, confirm and control the project scope and product scope.
enter
Project Charter
project management plan
business environment factors
organizational process assets
Tools & Techniques
expert judgment
data analysis
Meeting
output
scope management plan
Is the component of the project management plan that describes how to define, develop, monitor, control and confirm the project scope.
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
The requirements management plan is a component of the project management plan that describes how project and product requirements will be analyzed, documented, and managed.
2. Collect requirements
definition
Is the process of identifying, documenting, and managing the needs and wants of interested parties to achieve goals
enter
Project Charter
project management plan
project files
business documents
protocol
business environment factors
organizational process assets
Tools and Plans
expert judgment
Consider the opinions of individuals or groups with relevant expertise or training
data collection
Brainstorming
It is a technique used to generate and collect a variety of ideas for project requirements and product requirements.
Interview
It is a formal or informal method of obtaining information through direct conversations with relevant parties.
Can also be used to obtain confidential information
focus group
Convene scheduled stakeholders and subject matter experts
A trained moderator leads the interactive discussion
Questionnaire
The audience is diverse, the survey needs to be completed quickly, the respondents are geographically dispersed, and it is suitable for statistical analysis
Benchmarking
data analysis
decision making
vote
unanimously agreed
Most agree
A relative majority agrees
autocratic decision making
Multi-criteria decision sharing
Data performance
Affinity diagram
mind Mapping
Interpersonal relations and team skills
nominal group technique
Rank the most useful ideas by voting
observe and talk
Refers to direct observation of how individuals perform work or tasks and implement processes in their respective environments. When product users are difficult or unwilling to articulate their needs
guide
Quickly define cross-functional requirements
Joint application design or development
Quality function development
user stories
System interaction diagram
prototype method
Build a prototype of the intended product and solicit early feedback on requirements before actually manufacturing the product.
output
requirements document
A requirements document describes how various single requirements will satisfy the business needs associated with the project
Business needs
Stakeholder needs
Solution requirements
Requirements Tracking Matrix
A form that connects product requirements from their source to the deliverables that satisfy the requirements
3. Define the scope
definition
Defining scope is the process of developing a detailed description of the project and product
enter
scope management plan
project files
requirements document
Hypothetical log
risk register
business environment factors
organizational process assets
Tools & Techniques
expert judgment
data analysis
decision making
Human-computer relations and team skills
product analysis
output
Project scope statement
Is a description of the project scope, key deliverables, assumptions, and constraints
Product range description
Deliverables
Acceptance Criteria
Project Exclusions
There is some degree of overlap in the content of the project charter and the project scope statement, but their level of detail is completely different
Project file updates
Hypothetical log
requirements document
Requirements Tracking Matrix
Interested Party Register
4. Create WBS
definition
Creating a work breakdown structure is the process of breaking down project deliverables and project work into smaller, more manageable components.
enter
project management plan
project files
project scope statement
requirements document
business environment factors
organizational process assets
Tools & Techniques
expert judgment
break down
It is the lowest level of work in the WBS, and its cost and duration can be estimated and managed
Taking each stage of the project life cycle as the second level of decomposition
Second level of decomposition with main deliverables
Deliverables or components that are to be completed far into the future may not be decomposable today. The project management team therefore often needs to wait for agreement on the deliverable or component before the corresponding details in the WBS can be worked out. This technique is sometimes called rolling planning
output
Scope Baseline
project scope statement
WBS
work package
planning package
WBS Dictionary
Project file updates
Hypothetical log
requirements document
5. Determine the scope
definition
Validating scope is the process of formal acceptance of completed project deliverables
Verified deliverables output from the control quality process are reviewed by the customer or sponsor to confirm that these deliverables have been satisfactorily completed and formally accepted.
enter
project management plan
project files
Verify deliverables
job performance data
Tools & Techniques
examine
Inspection refers to carrying out activities such as measurement, review and validation to determine whether work and deliverables meet requirements and product acceptance standards
decision making
output
Deliverables for acceptance
Deliverables that meet the acceptance criteria should be formally signed off by the client or sponsor
change request
Deliverables that are completed but have not passed formal acceptance and the reasons for acceptance should be documented. Change requests and defect remediation may be required for these deliverables.
job performance information
Project file updates
6. Control scope
definition
It is the process of monitoring the scope status of projects and products and managing changes to the scope baseline.
Uncontrolled expansion of product or project scope (without corresponding adjustments in time, cost, and resources) is called scope creep. Change is inevitable, so on every project, some form of change must be enforced.
enter
project management plan
project files
job performance data
organizational process assets
Tools & Techniques
data analysis
Deviation analysis
trend analysis
output
job performance information
change request
Project Management Plan Update
Project document risks