Wondershare EdrawMind
EdrawMindPMP-5 Scope Management
MindMap Gallery PMP-5 Scope Management
- 10
PMP-5 Scope Management
This mind map is for Xisai PMP project management. Chapter 5: Overview of Scope Management Knowledge Points, At the same time, there are PMP test questions with relevant knowledge points. From knowledge points to corresponding test questions, deepen your understanding of knowledge points!
Edited at 2023-03-31 17:36:42- 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.
PMP-5 Scope Management
- 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
PMP-5 Scope Management
definition
Including the various processes that ensure the project does and only does all the work required to successfully complete the project
scope
Steps to scope management
The various processes of scope management
1. Planning scope management
definition
Document how project scope and product scope are defined, validated and controlled
output
demand management plan
How to collect, record and manage requirements
scope management plan
How to manage scope methodology
main effect
Provide guidance and direction on how to manage scope throughout the project
This process is performed only once or only at predefined points in the project
2. Gather requirements
connotation
It is the process of identifying, documenting and managing the needs and demands of relevant parties to achieve goals.
The needs of all relevant parties should be collected in advance
main effect
Establishes the basis for defining product scope and project scope and does it only once or only at predefined points in the project
Tool technology
data collection techniques
1. Brainstorming
A technique used to generate and collect diverse ideas for project requirements and product requirements
It is a tool for innovation and creativity
2. nominal group
A technique used to facilitate brainstorming by voting to rank the most useful ideas for further brainstorming or prioritization
3. Interview
a formal or informal method of obtaining information through direct conversation
Interviews are often "one-to-one" or "one-to-many"
"One-to-one", "One-to-many"
Suitable for small groups of people
Interviews can also be used to obtain confidential information
Get confidential information
Speak directly with interviewees and maintain confidentiality
Interviews can be conducted in an environment of confidentiality and trust, with the goal of obtaining authentic and credible information
4. focus group
A trained moderator leads the interactive discussion
Host-guided, interactive discussion
6 to 10 people, not suitable for large teams
Focus groups tend to be more lively than “one-on-one” interviews
more enthusiastic
Convene meetings with scheduled stakeholders or experts to gain more expectations
5. Questionnaire
The audience is diverse, the survey needs to be completed quickly, the respondents are geographically dispersed, and it is suitable for statistical analysis
Complete quickly
Geographically dispersed
Suitable for quickly completing surveys, where respondents are geographically dispersed and there are many relevant parties
6. Delphi technique
A group of selected experts answer the questionnaire and provide feedback on the results of each round of requirements gathering in order to reach a consensus.
Experts answer questionnaire
Expert responses can only be given to moderators to maintain anonymity
Anonymous status
Expert, anonymous, multiple rounds
7. Benchmarking
Compare actual or planned products, processes and practices to those of other comparable organizations in order to identify best practices
Comparables are needed to identify the best opinion
8. expert judgment
Expert judgment refers to a reasonable judgment about current activities based on professional knowledge in an application field, knowledge field, discipline, industry, etc.
I really have no choice but to choose
9. Summarize
Data decision technology
1. vote
2. unanimously agreed
3. most principles
4. relative majority rule
5. dictatorship
6. It is to classify and sort the collected requirements.
data representation technology
Affinity diagram
Techniques used to group large numbers of ideas
mind Mapping
It reflects the commonalities and differences between creative ideas
analytical skills
1. Joint Application Design or Development (JAD)
Suitable for software development industry
This workshop focuses on bringing together business subject experts and development teams to gather requirements and improve the software development process
2. Quality Function Deployment (QFD)
The manufacturing industry uses QFD as a guidance skill to help determine the key features of new products.
QFD begins by collecting customer needs (also known as the "voice of the customer"), then objectively classifying and ranking these needs, and setting goals for achieving these needs.
3. User stories
User stories are short written descriptions of required functionality, often generated in requirements workshops
User stories describe which stakeholder will benefit from the functionality (role), what he needs to achieve (goal), and what benefits he expects to gain (motivation)
Data modeling technology
System interaction diagram
A visual depiction of the product scope that shows how business systems and their people and other systems (actors) interact with each other
prototype method
1. It refers to building a prototype of the intended product and soliciting early feedback on requirements before actually manufacturing the product.
2. Prototype includes
miniature products
Computer-produced two- and three-dimensional models
mockup
simulation
3. The prototype method supports the idea of progressive elaboration
4. Storyboard
Is a prototyping technology that demonstrates a sequence or navigation path through a series of images or diagrams
Interpersonal and team skills
observe
Also known as "job following," applies when product users are difficult or unwilling to articulate their needs
spectator
participant observer
guide
1. Keywords
is a consensus
Used when many interested parties disagree
Reach consensus among relevant parties
2. Three usage scenarios
JAD, QFD, user stories
3. Facilitation is used in conjunction with theme workshops to bring key stakeholders together to define product requirements.
4. Workshops can be used to quickly define cross-functional requirements and coordinate differences in needs among relevant parties
5. Compared with distributed meetings, seminars can identify and solve problems earlier
nominal group technique
Rank the most useful ideas by voting
Key words
It's a vote
output
requirements document
1. Requirements document, describing how various single requirements will meet the business needs related to the project
2. Only requirements that are clear (measurable and testable), traceable, complete, coordinated, and willing to be recognized by major stakeholders can be used as a benchmark.
3. Requirements can be divided into
business solutions
It is the needs of relevant parties
Business needs
Technical solutions
Refers to how to realize these needs
product demand
4. Category of needs
Business needs
Stakeholder needs
Solution requirements
1. Functional Requirements
2. non-functional requirements
Transition and readiness needs
Project requirements
quality requirements
Requirements Tracking Matrix
1. A form that connects product requirements from their sources to the deliverables that satisfy the requirements.
2. Provides a method to track requirements throughout the project life cycle, helping to ensure that each approved requirement in the requirements document can be delivered at the end of the project
3. Requirements tracking matrix also provides a framework for managing product scope changes
4. Corresponding tables of requirements and deliverables, each requirement is in line with the original business value
3. Define scope
definition
Is the process of developing detailed descriptions of projects and products
1. Break down the scope of the project
2. Hierarchical breakdown of the entire scope of work
effect
Describe the boundaries and acceptance criteria for a product, service, or outcome
process
The define scope process selects the final project requirements from the Requirements Document and then develops the boundaries and acceptance criteria for the project and its products, services, or results.
output
scope statement
What's included
1. Product range description
Project and product scope
2. Deliverables
Scope statement does not contain all requirements, only specific deliverables
3. Acceptance Criteria
A series of conditions that must be met before the deliverables are accepted
4. Project Exclusions
Identify content to exclude from projects
Clearly stating what is outside the scope of the project helps manage stakeholder expectations and reduce scope creep
5. project boundary baseline
Provides a baseline for evaluating whether change requests or additional work exceed project boundaries
Comparison with project charter
4. Create WBS
definition
1. Create a work breakdown structure (WBS)
Project deliverables
project work
The process of breaking down into smaller, more manageable components
2.Work Breakdown Structure (WBS)
3. The WBS organizes and defines the overall scope of the project and represents the work specified in the approved current project scope statement
effect
Provides a framework for what is to be delivered, which is done only once or only at predefined points in the project
WBS decomposition technology
1. top down
Decomposition layer by layer
2. bottom up
Used to merge lower level components
3. rolling planning
Deliverables or components that are to be completed far into the future and may not be decomposable currently
Deliverables that cannot be agreed upon currently will only be broken down in the far future
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.
4. in principle
8-80 (hours) principle
100% principle
Output: range base
1. WBS
The lowest level component of WBS is called
work package
Smaller than work packages are called activities
WBS levels: milestones, control accounts, planning packages, work packages
2. WBS Dictionary
3. scope statement
5. Confirm scope
definition
1. Is the process of formal acceptance of completed project deliverables
Confirm that deliverables meet business requirements and meet acceptance criteria
2. The process of formal acceptance by the client or sponsor
3. Key words
Before the closing phase, after completing the deliverables
4. This process should be carried out regularly throughout the project, as needed
effect
1. Make the acceptance process objective
2. At the same time, by confirming each deliverable, it increases the likelihood that the final product, service or result will be accepted.
concept
Review of verified deliverables output from the control quality process by the customer or sponsor is the validation and final acceptance of the deliverables
1. Control quality
Focus on the correctness of deliverables and whether they meet quality requirements
2. Confirm scope
Focus on acceptance of deliverables
3. Case
When the customer is inspecting the deliverables, they put forward new requirements and refuse to accept them.
At this point, the acceptance criteria for the project can be shared with the client.
WBS Dictionary
project scope statement
enter
1. Scope Baseline
Reference documents for acceptance of deliverables
2. Verified deliverables
Verified deliverables output from Control Quality for acceptance
Tool technology
examine
Check that deliverables meet acceptance criteria
method
implement
1. time
Validate scope as each deliverable is produced, or at phase review points (at the end of the phase)
2. event
Carry out activities such as measurement, review and validation through inspections to determine whether work and deliverables meet requirements and product acceptance standards
3. figure
Deliverables that meet the acceptance criteria should be formally signed and approved by the client or sponsor
Formal documentation should be obtained from the client or sponsor evidencing formal acceptance of the project deliverables by the relevant parties
output
1. Deliverables for acceptance
Results formally signed and approved by the client or sponsor
2. change request
Deliverables that have not passed acceptance require changes.
6. Scope of control
Predictive
Define deliverables at the outset and manage all scope changes incrementally (change) along the way
definition
It is the process of monitoring the scope status of projects and products and managing baseline changes.
Supervision scope and management scope baseline changes
Key words
New features, missing features, missing requirements
effect
Maintain the scope baseline throughout the project and as needed throughout the project
scope creep
Uncontrolled expansion of product or project scope (without corresponding adjustments to time, cost, and resources)
1. gold plated
Content added spontaneously within the team without following the process
Inside the team
2. scope creep
The scope to be added was requested by the team outside and was not implemented through the process.
outside the team
tool
1. Deviation analysis
2. trend analysis
scope change
1. Verify first, then analyze and submit application
2. If there is a change, go through the process
1. Customers propose new demands and changes
2. Scope creep needs to be changed during execution
3. Changes are required if the acceptance does not meet expectations.