MindMap Gallery Advanced Project Chapter 5 - Project Scope Management Mind Map
This is a mind map about Chapter 5 of High Project - Project Scope Management. It is sorted out from aspects such as control scope and confirmation scope. The content is detailed, the structure is clear, and the logic is strict. It is worth learning.
Edited at 2021-06-21 13:11:15One 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.
Chapter 5 - Project Scope Management
5.1 Planning scope management
definition
Develop a scope management plan that describes in writing how the project scope will be defined, validated, and controlled Procedure.
Two ranges
Project scope
Work
Clarify project boundaries
Monitor project execution
Prevent project scope creep
definition
What the project must do in order to deliver the product
The basis for generating a project management plan
The scope baseline is the approved project scope statement, WBS, WBS dictionary
Product Range
What the product or service should include
It is a description of product requirements and is the basis of the project scope.
Determine whether the product scope is complete based on whether it meets the product description
5.2 Collect requirements
definition
The process of identifying, documenting, and managing the needs and requirements of stakeholders to achieve project objectives
Classification
Business needs
Stakeholder needs
Solution requirements
Functional Requirements
non-functional requirements
Transition needs
Project requirements
quality requirements
Tools & Techniques
Interview
focus group
Bring together pre-selected stakeholders and subject matter experts to understand their expectations and attitudes toward the proposed product, service, or outcome. A trained moderator leads the interactive discussion. Focus groups tend to be more engaging than one-on-one interviews. A focus group is a group interview rather than a one-on-one interview
guided seminar
By inviting key cross-functional stakeholders to join the meeting. Guided workshops focus on product requirements Theory and definition. Workshops are an important technique for quickly defining cross-functional requirements and reconciling differences among stakeholders
Group innovation technology
Brainstorming
nominal group
Poll to rank the most useful ideas for further brainstorming or prioritization
Delphi technique
Anonymous or back-to-back methods, several rounds of feedback during the prediction process, so that the opinions of experts gradually converge
Concept/Mind Map
Affinity diagram
It is to fully collect various experiences, knowledge, ideas, opinions and other language and words on a certain issue. Data are summarized through diagrams and summarized and organized according to their mutual affinities to make the problem clear.
Multi-criteria decision analysis
group decision making techniques
unanimously agreed
most
subtopic
Questionnaire
observe
prototype method
Benchmarking
System interaction diagram
File analysis
requirements document
Business needs
Stakeholder needs
Solution requirements
Project requirements
Transition needs
Assumptions, dependencies, constraints
Requirements tracking
Demand management
Includes all activities that maintain requirements consistency and accuracy during product development, including controlling requirements baselines, keeping project plans consistent with requirements, controlling version status of individual requirements and requirements documents, managing connections between requirements and contact chains, or Manage dependencies between individual requirements and other deliverables of the project, tracking the status of requirements in the baseline
demand baseline
The results of software project requirements development should include project view and scope documents, use case documents, software requirements specifications and related analysis models. After review and approval, these documents define the requirements baseline of the development work. This baseline establishes an agreement between the customer and the developer to plan the functional and non-functional requirements of the product.
Requirements acquisition
Actively communicate with users, obtain user needs, analyze and correct them, and finally form a user interface that is suitable for solving problems. User needs and generate "User Needs Specification"
demand analysis
Analyze and abstractly describe various requirements to establish a conceptual model that can guide the system
Requirements definition
Based on the results of demand acquisition and demand analysis, define accurate product requirements and generate "Requirements Specification" Book"
Requirements verification
5.3 Define scope
definition
Defining scope is the process of formulating detailed descriptions of projects and products. Its main function is to clarify which of the collected requirements will be included in the project scope and which ones will be excluded from the project scope, thereby clarifying the boundaries of products, services or results.
Tools & Techniques
expert judgment
product analysis
Alternative generation
guided seminar
project scope statement
Product range description
Acceptance Criteria
Cost, schedule, quality measurement indicators
Deliverables
Project Exclusions
Constraints
Assumptions
effect
Scope
communication basics
planning and control basis
Change basis
planning basics
5.4 Create WBS
definition
Break down project deliverables and project work into smaller, more manageable component process
milestone
Marks the formal completion of a deliverable or phase. Important checkpoints are milestones, important milestones are baselines
work package
≥8 hours, ≤80 hours
control account
A control account includes several work packages, but a work package only belongs to one control account
planning package
It refers to the WBS component under the control account where the work content is known but detailed progress activities are lacking.
WBS Dictionary
Includes account code identification, work description, assumptions and constraints, responsible person or organizational unit, schedule milestones, related schedule activities, required resources, cost estimates, quality requirements, acceptance criteria, technical references, and agreement information
decomposition activities
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
Verify that the level of decomposition of deliverables is appropriate
8 aspects to pay attention to
WBS must be deliverable oriented
The WBS must fit within the scope of the project
The underlying layer of the WBS should support planning and control
There must be one person, and only one person, responsible for the elements in the WBS
WBS guidance. As a guideline rather than a principle, WBS should be controlled at 4 to 6 layers
The WBS should include project management work as well as subcontracted work.
The preparation of WBS requires the participation of all (main) project stakeholders and the participation of project team members.
WBS is not static
5.5 Confirmation scope
definition
The process of formal acceptance of completed deliverables by project stakeholders
Tools & Techniques
examine
group decision making techniques
step
Determine when scope validation is needed
Identify what inputs are needed for scoping validation
Determine the formally accepted criteria and elements for scoping
Determine the organizational steps for a scoping meeting
Organization scope confirmation meeting
Difference from quality control
Validation scope emphasizes the acceptance of deliverables; quality control emphasizes the correctness of deliverables;
Quality control is usually carried out before the scope is confirmed, or at the same time; the scope is usually confirmed at the end of the stage;
Quality control is an internal inspection; the scope is confirmed and the deliverables are accepted by the project stakeholders;
Difference from closing
Scope confirmation emphasizes verification and acceptance of deliverables; closing emphasizes the process of ending the project or phase.
Confirmation scope emphasizes acceptance of deliverables; closing emphasizes acceptance of products
5.6 Control scope
Controlling scope is the process of monitoring the scope status of projects and products and managing changes to the scope baseline. Its primary role is to maintain the scope baseline throughout the project
The main work
Influence the factors that lead to scope changes and try to make these factors develop in a favorable direction
Determine whether a scope change has occurred
Manage actual changes when scope changes occur, ensuring that all requested changes are processed in accordance with the project's overall change control process