Wondershare EdrawMind
MindMap Gallery Chapter 12 Project Scope Management
- 107
- 1
- 1
Chapter 12 Project Scope Management
Project scope management includes the processes of ensuring that 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.
Edited at 2022-01-27 14:56:10
- Recommended to you
- Outline
Chapter 12 Project Scope Management
I. concept
1. definition
Ensure that the project does and only does all the work required to successfully complete the project's various processes.
Define and control what work should and should not be included in the project
2. content
planning scope management
The process of creating a scope management plan to document how project scope and product scope are defined, validated, and controlled
Gather requirements
The process of identifying, documenting, and managing the needs and wants of interested parties to achieve project objectives
Define scope
The process of developing detailed project and product descriptions
Create WBS
The process of breaking down project deliverables and project work into smaller, more manageable components
Confirm scope
The process of formal acceptance of completed project deliverables
Control range
Monitor project and product scope status and manage the process of scope baseline changes
3. scope
Product Range
The features and functions of a product, service or result
Project scope
Work that must be done to deliver a product, service, or result with specified features and functionality
Project scope sometimes also includes product scope
4. Development trends and emerging practices
Identify problems and identify business needs
Identify and recommend solvable solutions that meet these needs
Collect, document and manage stakeholder requirements to meet business and project objectives
Drive successful application of a program or project’s products, services, or results
5. Factors to consider when cutting
Knowledge and requirements management
Validation and control
development method
stability of demand
governance
II. planning scope management
1. concept
definition
The process of creating a scope management plan to document how project scope and product scope will be defined, validated, and controlled.
effect
Provide guidance and direction on how to manage scope throughout the project.
2. enter
Project Charter
Document 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 into project practices affects the way in which project and product scope are managed.
Project life cycle description
The project life cycle defines the series of stages that a project goes through from inception to completion
development method
Development methodology defines whether the project uses a waterfall, iterative, adaptive, agile, or hybrid development approach
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
3. Tools & Techniques
expert judgment
Similar projects in the past
Information on specific industries, disciplines and application areas
data analysis
Alternatives analysis
Evaluate various methods for gathering requirements, detailing project and product scope, creating products, validating scope, and controlling scope
Meeting
4. output
scope management plan
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
How to plan, track and report on various requirements activities
Configuration management activities
Requirements prioritization process
Metrics to measure and reasons for using them
A tracking structure that reflects which requirement attributes will be included in the tracking matrix
III. Gather requirements
1. concept
definition
The process of identifying, documenting, and managing the needs and wants of interested parties to achieve project objectives
effect
Establishes the basis for defining product scope and project scope and does it only once or only at predefined points in the project
2. enter
Project Charter
Document the project purpose, project overview, assumptions, constraints, and high-level requirements that the project is intended to achieve
project management plan
scope management plan
The scope management plan includes information on how to define and specify the project scope
demand management plan
A requirements management plan contains information on how to collect, analyze, and document project requirements
Stakeholder Engagement Plan
Understand stakeholder communication needs and participation levels from stakeholder engagement plans in order to assess and adapt to stakeholder participation in demand activities
project files
Hypothetical log
The Assumption Log identifies assumptions about the product, project, environment, stakeholders, and other factors that affect requirements
Lessons Learned Register
The Lessons Learned Register provides an effective requirements gathering technique, especially for projects using an iterative or adaptive product development approach.
Interested Party Register
The stakeholder register is used to understand which stakeholders can provide requirements information and record their needs and expectations for the project.
business documents
The business document that affects the requirements gathering process is the business case, which describes the necessary, expected, and optional standards that should be met to meet business needs.
protocol
The agreement will contain project and product requirements
business environment factors
group Culture
infrastructure
Personnel management system
market conditions
organizational process assets
policies and procedures
Historical information and lessons learned knowledge base containing information from past projects
3. Tools & Techniques
expert judgment
business analysis
Requirements acquisition
demand analysis
requirements document
Project requirements for similar previous projects
Illustration techniques
guide
conflict management
data collection
Brainstorming
Techniques for generating and gathering diverse ideas for project requirements and product requirements
Interview
Formal or informal methods of obtaining information through direct conversations with interested parties
focus group
Gather intended stakeholders and subject matter experts to understand their expectations and attitudes toward the product, service, or outcome in question
Questionnaire
Design a series of written questions to quickly gather information from a large audience
Benchmarking
Compare actual or planned products, processes, and practices with those of other comparable organizations to identify best practices, formulate suggestions for improvement, and provide a basis for performance appraisal. Can be internal or external.
data analysis
protocol
business plan
Business process or interface documentation
Business rules library
current process
market literature
Problem log
policies and procedures
regulatory documents
invitation to propose
Example
decision making
vote
unanimously agreed
everyone agrees on a course of action
Most agree
Decisions can be made after gaining the support of more than 50% of the people in the group
A relative majority agrees
Make a decision based on the opinions of a few people, and use it when there are more than two candidates
autocratic decision making
One person is responsible for making decisions for the entire group
Multi-criteria decision analysis
Use a decision matrix to evaluate and prioritize ideas using a systems analysis approach to establish criteria such as risk level, uncertainty, and value return
Data performance
Affinity diagram
Techniques used to group large numbers of ideas for further review and analysis
mind Mapping
Integrate the ideas obtained from brainstorming into a picture to reflect the commonalities and differences between the ideas and stimulate new ideas
Interpersonal and team skills
nominal group technique
Ask the group a question and problem
Moderator records everyone’s ideas on a flip chart
Brainstorm various ideas and guide all members to clarify and understand
Individuals vote privately to prioritize ideas
observe and talk
guide
Joint application design or development
Quality function deployment
user stories
System interaction diagram
prototype method
Prototype creation
user experience
Feedback collection
Prototype modification
4. output
requirements document
Business needs
Stakeholder needs
Solution requirements
Functional Requirements
non-functional requirements
Transition and readiness needs
Project requirements
quality requirements
Requirements Tracking Matrix
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
IV. Define scope
1. concept
definition
The process of developing detailed project and product descriptions
effect
Describe the boundaries and acceptance criteria for a product, service, or outcome
2. enter
Project Charter
Includes a high-level description of the project, product characteristics, and approval requirements
project management plan
Includes a scope management plan that documents how the project scope will be defined, validated, and controlled
project files
Hypothetical log
requirements document
risk register
business environment factors
group Culture
infrastructure
Personnel management system
market conditions
organizational process assets
Policies, procedures and templates for developing project scope statements
Project archives of past projects
Lessons learned from previous phases or projects
3. Tools & Techniques
expert judgment
data analysis
decision making
Interpersonal and team skills
product analysis
product breakdown
demand analysis
system analysis
Systems Engineering
Value Analysis
Value Engineering
4. output
project scope statement
Product range description
Deliverables
Acceptance Criteria
Project Exclusions
Project file updates
Hypothetical log
requirements document
Requirements Tracking Matrix
Interested Party Register
V. Create WBS
1. concept
definition
The process of breaking down project deliverables and project work into smaller, more manageable components
effect
Provide a structure for what is to be delivered, only once or at predefined points in the project
2. enter
project management plan
project files
project scope statement
requirements document
business environment factors
WBS standards for your industry
organizational process assets
Policies, procedures and templates for creating WBS in terms of
Project archives of past projects
Lessons learned from past projects
3. Tools & Techniques
expert judgment
break down
Identify and analyze deliverables and related work
Determine the structure and arrangement of the WBS
Decomposition layer by layer from top to bottom
Specify and assign identification codes to WBS components
Verify the appropriate level of decomposition of deliverables
4. output
Scope Baseline
project scope statement
WBS
work package
planning package
WBS Dictionary
Account code identifier
work description
Assumptions and constraints
responsible organization
progress milestones
Related progress activities
Required resources
Cost Estimate
Quality requirements
Acceptance Criteria
Technical references
Protocol information
Project file updates
Hypothetical log
requirements document
VI. Confirm scope
1. concept
definition
The process of formal acceptance of completed project deliverables
effect
Bring objectivity to the acceptance process and increase the likelihood of acceptance of the final product, service or result by validating each deliverable
2. 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
3. Tools & Techniques
examine
decision making
4. output
Deliverables for acceptance
job performance information
change request
Project file updates
Lessons Learned Register
requirements document
Requirements Tracking Matrix
VII. Control range
1. concept
definition
Monitor project and product scope status and manage the process of scope baseline changes
effect
Maintain the scope baseline throughout the project and as needed throughout the project
2. enter
project management plan
scope management plan
demand management plan
change management plan
configuration management plan
Scope Baseline
performance measurement standards
project files
Lessons Learned Register
requirements document
Requirements Tracking Matrix
job performance data
organizational process assets
3. Tools & Techniques
data analysis
Deviation analysis
trend analysis
4. output
job performance information
change request
Project Management Plan Update
scope management plan
Scope Baseline
progress baseline
cost basis
performance measurement benchmarks
Project file updates
Lessons Learned Register
requirements document
Requirements Tracking Matrix