MindMap Gallery Project management and agile practices
Project management and agile practices were compiled by myself and passed the PMP exam 2A1T. PDCA and Six Sigma are the two quality improvement tools most commonly used to analyze and evaluate improvement opportunities. P: plan D: implementation C: Check (confirm) A: Measures Agile methods that focus on working in small batches; the purpose of small batch systems is to detect inconsistencies and quality issues early in the project life cycle.
Edited at 2023-07-29 11:58:42This 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.
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.
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.
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.
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.
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.
project management
4. Project integration management
1. 4.1 Develop a project charter
enter
business case
1. Investment decision
2. Goals and reasons for project launch
3. Opportunities, threats, strengths, weaknesses (SWOT analysis)
4. Multiple solutions to meet business needs (alternative solution analysis)
5. Recommended solutions (cost-benefit analysis)
6. Evaluate target benefits
Benefit Management Plan
1. Target benefits
2. Strategic consistency
3. Person responsible for benefits
4. Time node (benefit time)
5. Measurement indicators
6. Risk
protocol
organizational process assets
business environment factors
Tools & Techniques
1. Expert judgment
2. Data collection
1. Brainstorming
2. Focus group
3. Interview
3. Interpersonal and team skills
1. Conflict management
2. Guidance
3. Meeting management
4. Meeting
output
1. Project charter
1. Content:
1. Project purpose and goals
2. Criteria for project success and exit
3. High-level information (requirements, schedule, budget, risks, relevant parties...)
4. Project manager and authority
5. Articles of Association Approval Information
2. Approval: sponsor, PMO, senior management (steering management committee)
3. Function: Start the project and authorize PM
2. Hypothesis log
2. 4.2 Develop project management plan
enter
Project Charter
Hypothetical log
business environment factors
organizational process assets
Tools & Techniques
1. Expert judgment
2. Data collection
1. Brainstorming
2. Checklist
3. Focus group
4. Interview
3. Interpersonal and team skills
1. Conflict management
2. Guidance
3. Meeting management
4. Meeting
output
project management plan
1. Sub-plans in 9 areas
1.1. Scope management plan
1.2. Progress management plan
1.3. Cost management plan
1.4. Quality management plan
1.5. Resource management plan
1.6. Communication management plan
1.7. Risk management plan
1.8. Procurement management plan
1.9. Stakeholder participation plan
2. 3 independent plans
2.1. Demand management plan
2.2. Change management plan
2.3. Configuration management plan
3. 3 benchmarks
3.1. Scope benchmark
3.2. Progress benchmark
3.3. Cost basis
Pack
4. 1 packaging benchmark
performance measurement benchmarks
3. 4.3 Direct and manage project work
enter
project management plan
Approved change request
Tools & Techniques
1. Expert judgment
2. Project management information system
3. Meeting
output
1. Deliverables
2. Original work performance data
3. Problem log
1. Describe the problem
2. Person in charge
3. Time limit
4. Change request (written request)
1. Preventive measures: Ensure that future performance is consistent with the project management plan
2. Corrective measures: If performance has deviated, take measures to correct it.
3. Defect remedy: product is defective
4. Update: Modify formal controlled documents
written request
4. 4.4 Management knowledge
enter
All project files
Tools & Techniques
1. Expert judgment
2. Knowledge management
3. Information management
4. Interpersonal and team skills
1. Active listening
2. Guidance
3. Leadership
4. Interpersonal communication
5. Political awareness
output
Lessons Learned Register
5. 4.5 Monitor project work
enter
1. Cost forecast
2. Progress forecast
3. Quality report
4. Risk report
5. Work performance information
Tools & Techniques
1. Expert judgment
2. Data analysis
Earned value analysis
Deviation analysis
Root Cause Analysis
Alternatives analysis
Cost-benefit analysis
trend analysis
3. Decision-making
4. Meeting
output
job performance report
1. Performance information
2. Forecast information
3. Overall defects
4. Overall risk
5. Solutions
6. 4.6 Implement overall change control
enter
1. Project management plan
change management plan
configuration management plan
Scope Baseline
progress baseline
cost basis
2. Project files
Estimate basis
Requirements Tracking Matrix
risk report
3. Work performance report
4. Change request
Tools & Techniques
expert judgment
change control tools
1. Identify changes (submit change requests)
2. Record changes (change log)
3. Comprehensive assessment of changes (PM Dev overall assessment)
4. Consider exerting influence (feedback: favorable --> approver, unfavorable --> submitter)
5. Submit change request (PM, CCB)
6. Approval or rejection
7. Update (veto: change log; approve: change log, plan, document)
8. Notify relevant parties
data analysis
Alternatives analysis
Cost-benefit analysis
decision making
vote
autocratic decision making
Multi-criteria decision analysis
Meeting
output
Approved change request
Change log
Project Management Plan Update
7. 4.7 End the project or phase
enter
All files
Tools & Techniques
output
Organizational process asset updates
final report
handover results
5. Project scope management
5.1 Planning scope management
enter
Tools & Techniques
output
demand management plan
scope management plan
Explain how to do the work
5.2 Collect requirements
enter
Project Charter
business documents
protocol
project management plan
Tools & Techniques
1. Expert judgment
2. Data collection
Brainstorming
Interview
focus group
Questionnaire
Benchmarking
3. Data analysis
File analysis
4. Decision-making
vote
Delphi technique
autocratic decision analysis
Multi-criteria decision analysis
5. Data performance
Affinity diagram
mind Mapping
6. Interpersonal and team skills
nominal group
observe/talk
guide
Joint Application Development JAD
Quality function expansion
user stories
7. System interaction diagram
8. Prototype method
output
requirements document
Requirements Tracking Matrix RTM
1. Demand traceability: where it comes from and what business goals it is based on
2. Backward tracking: Track whether the results of current requirements are designed, developed, and tested
3. Connect with business goals to ensure that each requirement has commercial value
5.3 Define scope
enter
1. Project charter
2. Project management plan
scope management plan
3. Project files
Hypothetical log
requirements document
risk register
4. Business environment factors
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data collection
Alternatives analysis
3. Decision-making
Multi-criteria decision analysis
4. Interpersonal and team skills
guide
5. Product analysis
output
project scope statement
1. Project scope description (product scope description)
2. Project deliverables
3. Acceptance standards
4. Project exclusions (exclusions)
Project file updates
Hypothetical log
requirements document
Requirements Tracking Matrix
Lessons Learned Register
5.4 Create WBS
enter
1. Project management plan
scope management plan
2. Project files
project scope statement
requirements document
3. Business environment factors
4. Organizational process assets
Tools & Techniques
expert judgment
break down
1. Relevant parties should participate as much as possible (all employees participate)
2. Rolling planning (the work package is the lowest work package)
3. Top-down and layer-by-layer detailed decomposition (assignment of codes)
4. 100% principle (bottom-up summary)
output
Scope Baseline
scope statement
WBS
WBS Dictionary
Resource requirements
Acceptance Criteria
Job Description
Logic
Project file updates
Hypothetical log
requirements document
5.5 Confirmation scope
enter
Verified deliverables
Tools & Techniques
examine
decision making
output
Deliverables for acceptance
Project file updates
Lessons Learned Register
requirements document
Requirements Tracking Matrix
job performance information
change request
5.6 Control scope
enter
project management plan
project files
job performance data
organizational process assets
Tools & Techniques
data analysis
Deviation analysis
trend analysis
output
job performance information
Project file updates
Requirements Tracking Matrix
6. Project progress management
6.1 Planning progress management
enter
Tools & Techniques
output
progress management plan
Accuracy
unit of measurement
Measurement rules
report format
Organization Program Links
release iteration length
control threshold
How to carry out progress management work
6.2 Define activities (what to do)
enter
Tools & Techniques
break down
rolling planning
output
Activity list
Activity properties
Milestone List
6.3 Sequence activities (what to do first)
enter
project management plan
progress management plan
Scope Baseline
project files
Activity properties
Activity list
Hypothetical log
Milestone List
business environment factors
organizational process assets
Tools & Techniques
predecessor relationship drawing method
Finish to start (most used)
start to start
complete to complete
parallel relationship
Start to finish (rarely encountered)
Determine and integrate dependencies
Mandatory dependencies: hard logic, objective logic, user/contract requirements.
Selective dependence: soft logic, best practices, and experience
External dependencies: non-project activities, not within the scope of project team management
Internal dependencies: relationships within project activities that are controllable by the team
lead and lag
Advance amount: The amount that can be advanced before and after
Lag amount: The amount by which the immediate predecessor and the immediate successor can be delayed
project management information system
output
Project progress network diagram
Project file updates
Activity properties
Activity list
Hypothetical log
Milestone List
6.4 Estimate the activity time (how long the activity will take)
enter
project management plan
progress management plan
Scope Baseline
project files
Activity properties
Activity list
Hypothetical log
Lessons Learned Register
Milestone List
Project team dispatches work orders
resource breakdown structure
Resource Calendar
Resource requirements
Resource quantity
type
Very important
business environment factors
organizational process assets
Tools & Techniques
1. Expert judgment
2. Analogous estimation
3. Parameter estimation
4. Three-point estimation
Triangular distribution: average estimate = (most optimistic most likely + most pessimistic)/3
(Default) Beta distribution: mean estimate = (most optimistic 4 * most likely + most pessimistic) / 6
Standard deviation = (most pessimistic - most optimistic)/6
Consider duration based on risk
5. Bottom-up estimation: first decompose from top to bottom and then summarize, which is costly, time-consuming and more accurate.
6. Data analysis
Alternatives analysis
Reserve analysis
Contingency Reserve: Included in Baseline
Management reserves: not included in baseline
7. Decision-making
8. Meeting
output
1. Duration estimation
2. Estimation basis: including assumptions, constraints, and confidence levels
3. Project file update
Activity properties
Hypothetical log
Lessons Learned Register
6.5 Develop a schedule (how long will the project take)
enter
1. Project management plan
progress management plan
Scope Baseline
2. Project files
1. Activity attributes
2. Activity list
3. Hypothesis log
4. Basis for estimation
5. Duration estimation
6. Register of experiences and lessons learned
7. Milestone List
8. Project progress network diagram
9. The project team dispatches work orders
10. Resource calendar
11. Resource requirements
12. Risk register
3. Agreement
4. Business environment factors
5. Organizational process assets
Tools & Techniques
1. Progress network analysis
Combine the following methods
2. Critical path method
The path with the longest total construction period in the network diagram determines the shortest construction period of the project
There can be multiple critical paths, and the activity time difference on the critical path is generally 0
If the activity time difference of the critical path is negative, it indicates that the progress is delayed.
The critical path is relative and can vary
The more critical paths there are, the greater the risk of the project
3. Resource optimization
resource balancing
resource smoothing
4. Data analysis
What-if scenario analysis
simulation
Monte Carlo analysis (choose it when it comes to simulations, models, and entire projects)
5. Advance and lag
6. Progress compression (on the critical path)
Quick follow-up (soft logic is the premise)
Convert serial work to parallel work. Risks increase. If counter-work occurs, costs will rise. (Partial parallelism, complete parallelism, reduced requirements)
Rushing (hard logic)
Trading resources for time will increase costs and risks (Add resources, work overtime, expedite)
7. Project management information system
8. Agile release planning (focusing on agile)
output
1. Progress benchmark
2. Project progress plan
1. Milestone chart
2. Gantt chart
3. Progress network diagram
3. Progress data
alternative schedule
progress reserve
4. Project calendar
Days and shifts on which activities are carried out
Separate available and unavailable time periods
For the entire team
Includes statutory holidays
5. Change request
6. Project management plan update
7. Project file update
1. Activity attributes
2. Hypothesis log
3. Duration estimation
4. Register of experiences and lessons learned
5. Resource requirements
6. Risk register
6.6 Control progress
enter
1. Project management plan
progress management plan
progress baseline
Scope Baseline
performance measurement benchmarks
2. Project files
Lessons Learned Register
Project Calendar
Project schedule
Resource Calendar
progress data
3. Work performance data
4. Organizational process assets
Tools & Techniques
1. Data analysis
1. Earned value analysis
2. Iterative burndown chart
Story points remaining
3. Performance review
4. Trend analysis
5. Deviation analysis
6. What-if scenario analysis
2. Critical path method
3. Project management information system
4. Resource optimization
5. Advance and lag
6. Progress compression (change request must be made)
output
1. Work performance information
2. Progress forecast
3. Change request
4. Project management plan update
5. Project file update
Project schedule
7. Project cost management
7.1 Planning cost management
enter
Tools & Techniques
output
cost management plan
Accuracy
unit of measurement
Accuracy
report format
organizational procedures
performance measurement rules
control threshold
7.2 Estimating costs
enter
project management plan
cost management plan
quality management plan
Scope Baseline
project files
Lessons Learned Register
Project schedule
Resource requirements
risk register
business environment factors
organizational process assets
Tools & Techniques
expert judgment
analogy estimation
parameter estimation
Bottom-up estimation
three point estimate
data analysis
Alternatives analysis
Reserve analysis
contingency reserve
management reserve
quality cost
consistency cost
non-conformity cost
project management information system
decision making
vote
output
Cost Estimate
Estimate basis
Project file updates
Hypothetical log
Lessons Learned Register
risk register
7.3 Develop a budget
enter
project management plan
cost management plan
resource management plan
Scope Baseline
project files
Estimate basis
Cost Estimate
Project schedule
risk register
business documents
business case
Benefit Management Plan
protocol
business environment factors
organizational process assets
Tools & Techniques
expert judgment
cost summary
data analysis
Reserve analysis
Historical information review
Funding limit balance
Financing
output
cost basis
Project funding requirements
Project file updates
Cost Estimate
Project schedule
risk register
7.4 Control costs
enter
project management plan
cost management plan
cost basis
performance measurement benchmarks
project files
Lessons Learned Register
Project funding requirements
job performance data
organizational process assets
Tools & Techniques
expert judgment
data analysis
Earned value analysis
Deviation analysis
trend analysis
Reserve analysis
Performance index to completion
project management information system
output
job performance information
cost forecast
change request
Project Management Plan Update
cost management plan
cost basis
performance measurement benchmarks
Project file updates
Hypothetical log
Estimate basis
Cost Estimate
Lessons Learned Register
risk register
8. Project quality management
8.1 Planning quality management (QP process)
enter
1. Project charter
2. Project management plan
·Demand Management Plan
·Risk management plan
Stakeholder Engagement Plan
Scope Baseline
3. Project files
Hypothetical log
requirements document
Requirements Tracking Matrix
risk register
Interested Party Register
4. Factors affecting career prospects
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data collection
Benchmarking
Brainstorming
Interview
3. Data analysis
Cost-benefit analysis
quality cost
Consistency cost (improvement)
prevention cost
training
Documentation of process
equipment
Evaluate costs
test
destructive testing
examine
Cost of non-conformity (avoided)
internal failure costs
Rework
scrap
external failure costs
responsibility
Warranty
business loss
4. Decision-making
Multi-criteria decision analysis
5. Data performance
Flow chart (visualization)
logical data model
Matrix diagram
Demonstrate strong and weak relationships between factors, causes, and goals
mind Mapping
6. Planning of tests and inspections
7. Meeting
output
1. Quality management plan
Main procedures related to the project
Quality standards adopted by the project
Project quality goals
Quality roles and responsibilities
Project deliverables and processes requiring quality review
Quality control and quality management activities planned for the project
Frequent updates
Quality tools used in the project
2. Quality measurement indicators
3. Project management plan update
risk management plan
Scope Baseline
4. Project file update
Lessons Learned Register
Requirements Tracking Matrix
risk register
Interested Party Register
8.2 Management quality (QA process, quality improvement for the process)
enter
1. Project management plan
quality management plan
2. Item self-document
Lessons Learned Register
Quality control measurement results
quality measures
risk report
3. Organizational process assets
Tools & Techniques
1. Data collection
Checklist
2. Data analysis
Alternatives analysis
File analysis
Process Analysis (PDCA)
Root Cause Analysis
3. Decision-making
Multi-criteria decision analysis
4. Data performance
Affinity diagram
cause and effect diagram
Flowchart (Process Chart)
Histogram
Matrix diagram
Scatter plot
5. Audit (quality assurance)
Identify best practices
Under identification
Share good practices from similar projects
Actively improve the process
Contribute to the accumulation of knowledge base of lessons learned
Confirm implementation of approved changes
6. X-oriented design DFX (product design)
7. Problem solving
Define the problem (recorded in the problem log)
Identify root causes (cause and effect diagrams, flow charts, histograms)
Generate possible solutions (alternative analysis)
Select the best solution (cost-benefit analysis, multi-criteria decision analysis)
Execute the solution (submit change request, responsible person, time)
Verify solution effectiveness (track solutions)
8. Quality improvement methods (process improvement)
output
1. Quality report
Overview of findings during quality control
2. Testing and evaluation documents
Used to evaluate achievement of quality objectives, including checklists and requirements tracking matrices
3. Change request
4. Project management plan update
quality management plan
Scope Baseline
progress baseline
cost basis
5. Project file update
Problem log
Lessons Learned Register
risk register
8.3 Control quality (QC process, quality improvement based on results)
enter
1. Project management plan
quality management plan
2. Project files
Lessons Learned Register
quality measures
Test and Evaluation Documents
3. Approved change request
4. Deliverables
5. Work performance data
6. Business environment factors
7. Organizational process assets
Tools & Techniques
1. Data collection
Checklist
Checklist (count)
statistical sampling
Variable sampling (level of eligibility)
Attribute sampling (qualified or not)
Questionnaire
2. Data analysis
performance review
Get quality metrics
Root Cause Analysis
3. Check
4. Testing/Product Evaluation
5. Data performance
cause and effect diagram
Control Charts
Discover the stability of the process
performance predictions
Histogram
Scatter plot
6. Meeting
output
1. Quality control measurement results
2. Verified deliverables
3. Work performance information
4. Change request
5. Project management plan update
quality management plan
6. Project file update
Problem log
Lessons Learned Register
risk register
Test and Evaluation Documents
Agile and Hybrid Guide
1. Development method
Predictive
iterative
Incremental
Agile
Agile based on iteration
Process-based agile
Hybrid
Use a combination of agile and predictive methods simultaneously
Focus on agility, supplemented by prediction
Prediction first, agility second
2. Agile thinking (value-driven)
4 major values
Individuals and interactions over processes and tools
Working software trumps thorough documentation
Customer cooperation takes precedence over contract negotiation
Responding to change over following a plan
12 principles
1. MVP (minimum usable product)
1. Quickly deliver business value
2. Release prototypes and clarify requirements
3. Trial and error quickly to improve quality
4. Identify risks as early as possible
MMF (Minimum Merchant Function)
1. Continuously deliver valuable software as early as possible to meet customer needs
2. Welcome changes in requirements
3. Deliver usable software frequently, in as short a time as possible
4. Business personnel and developers must always collaborate (communicate frequently)
5. Motivate project personnel, give them the environment and support they need, and believe in them
6. Face to face conversation
7. The primary criterion for measuring progress using software
8. Promote sustainable development and always maintain a stable pace
9. Continuously improve technology and design
10. Concise and reduce unnecessary work as much as possible
11. Self-organizing team
12. Regularly reflect and adjust the team’s behavior
3. Agile Team
sponsor
set a goal
Provide resources
Provide guidance to product owners
Participate in iteration reviews and determine delivery of incremental results
Keep an eye on value and cost
Scrum process and roles
External customer needs
Product Owner PO
Record customer requirements to product backlog list (PBL)
Make sure the team is doing the right (valuable) things
Create a to-do list with the team (participatory decision-making)
Develop a release plan
Acceptance of Product Increment (MVP)
Provide product feedback (clarify requirements)
Get workflow training
Product Backlog (PBL)
1. Business value
2. Delayed delivery cost
3. Current organizational strategy
4. Market development trends
Requirements ranking
sprint planning meeting
1. PO clarifies requirements
2. Development team claims requirements (decomposition and estimation)
Sprint Backlog SBL
Iterate
Daily stand-up meeting
Agile coach
Form a cross-functional, multi-skilled team
education stakeholders
Servant leadership, service delivery
Guide, guide and remove obstacles
project team
Generalist experts, working in cross-functional teams without external support
3~9 people, full-time staff
Work in a self-organizing way
Frequent development and delivery
Deliver completed value (MVP) as an independent team
Integrate all work activities
When the team leader proposes a solution that is inconsistent with the team's, the team's choice is usually respected
Product function refinement
working software
Jury
1. Team presentation
2. PO, customer, sponsor---->Feedback
3. Put unsatisfied functions back into PBL
4. Put new requirements into PBL
Review meeting
PDCA
Agile work environment
Information emission source (transparent communication)
Kanban (pull production)
Facilitate process visualization
Help value stream analysis
Limit the quantity of work in progress and reduce waste
Avoid swarming and swarming
Cumulative flow graph
burn down chart
Know how many story points are left
It takes 4~8 iterations to reach a stable speed
Ignition chart
View the current completed story points
Function diagram
See completed features, remaining features, and total number of features
Product Backlog Ignition Chart
ABC project progress chart
Scrumban
A hybrid agile framework and approach
Scrum board
Physical board, information emission source
Team environment and collaboration
Centralized office
Distributed office
chase the sun
Public area
private area
team performance
Focus on process efficiency
Measured by average speed
4. Agile practice
Project Charter
Project Vision
Publishing standards
Workflow
Team and project manager develop together
Team Charter (Team Social Contract)
The way team members interact with each other
Sustainable development speed and core work hours
How is "Ready" (DoR) defined?
How "Done" (DoD) is defined (Acceptance Criteria)
Consider timeboxing
release plan
Specify how many versions to release and how many iterations of each version
Probing (probe, exploration)
When the team learns key technical or functional elements
Product backlog preparation and refinement
PO introduces the story to the team, PO is unsure about dependencies, and the team does the spying
Agile team discussion refinement
user stories
Role, Goal, Business Value
3C principle
The story is concise and written on small cards
The details of the story are negotiated with the user and written on the back.
Acceptance criteria and links
invest characteristics
independent
negotiable
valuable
estimable
small
estimable
sprint planning meeting
PO does requirements sorting and clarification
The team claims and categorizes tasks into tasks, and estimates task hours
Daily stand-up meeting
1. Raise problems and obstacles, but do not solve them at the meeting
2. Synchronize and coordinate work to prevent gold plating
3. Involve relevant parties to understand the latest progress
4. Failure to report the overall status of the project
5. There are many problems, so prioritize them.
6. Anti-pattern--->State meeting
Review meeting (can see the value reflected)
Review the MVP and adjust the product backlog as needed
Learn about project progress
Review meeting
Help teams learn, improve and adapt their processes
1. Reflection--------improvement--------plan
2. There are many improvement items, sort them
3. Review board
pair programming
PDCA
pair programming
Daily stand-up meeting
demo meeting
review meeting
Risk Management
Record in Risk Adjustment Backlog
Problem solving
1. Collect data
2. Analyze the reasons (root cause analysis)
3. Take action
technical debt
The deferred costs of failure to complete work early in the product life cycle
Technical debt issues are added to the product backlog and prioritized against other backlog requirements.
Development teams address technical debt through refactoring
5. Challenges and solutions to agile implementation
6. PMBOK Guide and Agile Comparison
Project integration management
project scope management
Project progress management
project cost management
planning poker
lightweight estimating
Project quality management
MVP
DOD
Review meeting
Project resource management
Project communication management
Project Procurement Management
1. Multi-layer structure
2. Total price increase
3. Cancel the plan in advance
4. Team expansion
Sharing risks and sharing benefits
Project stakeholder management
13. Project stakeholder management
13.1 Identifying interested parties
enter
1. Project charter
2. Business documents
business case
Benefit Management Plan
3. Project management plan
communications management plan
Stakeholder Engagement Plan
Regular identification
4. Project files
Change log
Problem log
requirements document
Regular identification
5. Agreement
6. Business environment factors
7. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data collection
Questionnaire
Brainstorming
3. Data analysis
Stakeholder analysis
File analysis
4. Data performance
Stakeholder mapping analysis/performance (group classification)
5. Meeting
output
1. Related party register
Name
Position
Role
Contact information
Basic Information
need
expect
Influence
Benefit relationship
Assessment information
Classification
Stakeholder classification
2. Change request
3. Project management plan update
demand management plan
communications management plan
risk management plan
Stakeholder Engagement Plan
4. Project file update
Hypothetical log
Problem log
risk register
13.2 Planning stakeholder participation
enter
1. Project charter
2. Project management plan
resource management plan
communications management plan
risk management plan
3. Project files
Hypothetical log
Change log
Problem log
Project schedule
risk register
Interested Party Register
4. Agreement
5. Business environment factors
6. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data collection
Benchmarking
3. Data analysis
Assumptions and constraints analysis
Root Cause Analysis
4. Decision-making
Prioritization/Grading
5. Data performance
mind Mapping
Stakeholder Engagement Assessment Matrix
Unaware
be opposed to
neutral
support
lead
6. Meeting
output
1. Stakeholder participation plan
13.3 Management of stakeholder participation – communication (not important)
enter
1. Project management plan
communications management plan
risk management plan
Stakeholder Engagement Plan
change management plan
2. Project files
Change log
Problem log
Lessons Learned Register
Interested Party Register
3. Business environment factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Communication skills
feedback
3. Interpersonal and team skills
conflict management
cultural awareness
negotiation
observe/talk
political awareness
4. Basic rules
5. Meeting
output
1. Change request
2. Project management plan update
communications management plan
Stakeholder Engagement Plan
3. Project document update
Change log
Problem log
Lessons Learned Register
Interested Party Register
13.4 Supervise stakeholder participation (not important)
enter
1. Project management plan
resource management plan
communications management plan
Stakeholder Engagement Plan
2. Project files
Problem log
Lessons Learned Register
Project communication records
risk register
Interested Party Register
3. Work performance data
4. Business environment factors
5. Organizational process assets
Tools & Techniques
1. Data analysis
Alternatives analysis
Root Cause Analysis
Stakeholder analysis
2. Decision-making
Multi-criteria decision analysis
vote
3. Data performance
Stakeholder Engagement Assessment Matrix
4. Communication skills
feedback
Demo
5. Interpersonal and team skills
active listening
cultural awareness
leadership
interpersonal communication
political awareness
6. Meeting
output
1. Work performance information
2. Please change
3. Project management plan update
resource management plan
communications management plan
Stakeholder Engagement Plan
4. Project file update
Problem log
Lessons Learned Register
risk register
Interested Party Register
Summarize
Structured combing to identify relevant parties
Stakeholder analysis (power, interests, influence, needs, expectations, attitudes)
Classification of relevant parties (mapping analysis/performance----》Power and interest grid)
Records (updating the interested party register)
Level of participation (Stakeholder Participation Assessment Matrix)
Develop an engagement strategy (stakeholder engagement plan)
Manage stakeholders (Communication -----> Communicate management plan and stakeholder engagement plan, resolve issues and conflicts -----> meet their needs)
Supervise stakeholders (stakeholder analysis, stakeholder participation assessment matrix)
Update strategy (submit change request--->change participation plan)
12.Project procurement management
12.1 Planning and Procurement Management
enter
1. Project charter
2. Business documents
business case
Benefit Management Plan
3. Project management plan
scope management plan
quality management plan
resource management plan
Scope Baseline
4. Project files
Milestone List
Project team dispatches work orders
requirements document
Requirements Tracking Matrix
Resource requirements
risk register
Interested Party Register
5. Business environment factors
6. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data collection
market research
3. Data analysis
Make-or-Buy Analysis
4. Supplier selection analysis
5. Meeting
output
1. Procurement management plan
2. Procurement strategy
3. Bidding documents
4. Procurement work instructions (Party A’s requirements)
5. Supplier selection standards
7. Independent cost estimation (purchasing budget)
Procurement documents
6. Make or buy decision
8. Change request
9. Project file update
Lessons Learned Register
Milestone List
requirements document
Requirements Tracking Matrix
risk register
Interested Party Register
10. Organizational process asset update
Contract classification
lump sum contract
Fixed price contract (fixed price)
Total price plus incentive fee contract
Total price plus economic price adjustment contract
Cost (compensation) contract
cost plus fixed fee contract
cost plus incentive fee contract
cost plus incentive fee contract
Work and materials contract
Comparison of contract types
12.2 Implement procurement
enter
1. Project management plan
scope management plan
demand management plan
communications management plan
risk management plan
Procurement Management Plan
configuration management plan
cost basis
2. Project files
Lessons Learned Register
Project schedule
requirements document
risk register
Interested Party Register
3. Procurement documents
4. Seller’s proposal
5. Business environment factors
6. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Advertisement
3. Bidders’ meeting
4. Data analysis
Proposal evaluation
5. Interpersonal and team skills
negotiation
output
1. Selected Seller
2. Agreement
3. Change request
4. Project management plan update
demand management plan
quality management plan
communications management plan
risk management plan
Procurement Management Plan
Scope Baseline
progress baseline
cost basis
5. Project file update
Lessons Learned Register
requirements document
Requirements Tracking Matrix
Resource Calendar
risk register
Interested Party Register
6. Organizational process asset update
12.3 Control purchasing
enter
1. Project management plan
demand management plan
risk management plan
Procurement Management Plan
change management plan
progress baseline
2. Project files
Hypothetical log
Lessons Learned Register
Milestone List
quality report
requirements document
Requirements Tracking Matrix
risk register
Interested Party Register
3. Agreement
4. Procurement documents
5. Approved change request
Direct and manage project work
QC
Control purchasing
3 data streams
6. Work performance data
7. Business environment factors
8. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Claims management
1. Negotiation (preferred method)
2. Third-party mediation
3. Court prosecution
3. Data analysis
Performance Review (Supplier Performance)
Earned value analysis
trend analysis
4. Inspection (supplier products)
5. Audit (both parties, for the procurement process)
output
1. Completed purchase
2. Work performance information
3. Purchasing document update
4. Change request
5. Project management plan update
risk management plan
Procurement Management Plan
progress baseline
cost basis
6. Project file update
Lessons Learned Register
Resource requirements
Requirements Tracking Matrix
risk register
Interested Party Register
7. Organizational process asset update
11. Project risk management
11.1 Planning risk management
enter
1. Project charter
2. Project management plan
All components
3. Project files
Interested Party Register
4. Business environment factors
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data analysis
Stakeholder Analysis (Risk Appetite)
3. Meeting
output
risk management plan
1. Risk management methodology
2. Roles and responsibilities
3. Risk Category (RBS)
4. Risk tolerance and critical points of relevant parties
5. Probability influence matrix
6. Funds and time arrangements
7. Report format and content
8. Regulations on risk tracking
11.2 Identify risks
enter
1. Project management plan
demand management plan
progress management plan
cost management plan
quality management plan
resource management plan
risk management plan
Scope Baseline
progress baseline
cost basis
2. Project files
Hypothetical log
Cost Estimate
duration estimate
Problem log
Lessons Learned Register
requirements document
Resource requirements
Interested Party Register
3. Agreement
4. Procurement documents
5. Business environment factors
6. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data collection
Brainstorming
Checklist
Interview
3. Data analysis
Root Cause Analysis
Assumptions and constraints analysis
SW0T Analysis
Strengths, Weaknesses, Opportunities, Threats
File analysis
4. Interpersonal and team skills
guide
5. Tip list
The rightmost column of the RBS risk breakdown structure
6. Meeting
risk seminar
1. Identify risks
2. Assess risks
output
1. Risk register
Individual risks identified
Potential countermeasures
Potential Risk Responsible Person
2. Risk report
3. Project file update
Hypothetical log
Problem log
Lessons Learned Register
11.3 Conduct qualitative risk analysis
enter
1. Project management plan
risk management plan
2. Project files
Hypothetical log
risk register
Interested Party Register
3. Business environment factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data collection
Interview
3. Data analysis
Risk data quality assessment
Risk probability and impact assessment
Assessment of other risk parameters
4. Interpersonal and team skills
guide
5. Risk classification
6. Data performance
Probability and Impact Matrix
hierarchical
7. Meeting
output
1. Project file update
Hypothetical log
Problem log
Risk Register V2
risk report
1. Risk preference
2. Risk threshold
3. Definition of probability impact
4. Probability influence matrix
planning
5. Probabilistic impact assessment
6. Data quality assessment
7. Query matrix
8. Evaluation of other characteristics
Qualitative
Steps in Qualitative Risk Analysis
11.4 Implement quantitative risk analysis
enter
1. Project management plan
risk management plan
Scope Baseline
progress baseline
cost basis
2. Project files
Hypothetical log
Estimate basis
Cost Estimate
cost forecast
duration estimate
Milestone List
Resource requirements
risk register
risk report
progress forecast
3. Business environment factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data collection
Interview
3. Interpersonal and team skills
guide
4. How uncertainty manifests itself
5. Data analysis
simulation
Monte Carlo analysis
Sensitivity analysis (tornado plots, ranking)
Determine which individual risks have the greatest potential impact on the project
Decision tree analysis
influence diagram
output
1. Project file update
risk report
11.5 Planning risk responses
enter
1. Project management plan
resource management plan
risk management plan
cost basis
2. Project files
Lessons Learned Register
Project schedule
Project team dispatches work orders
Resource Calendar
risk register
risk report
Interested Party Register
3. Business environment factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data collection
Interview
3. Interpersonal and team skills
guide
4. Threat response strategies
1. Avoid (extend the schedule, reduce the scope---change the plan to completely eliminate the risk)
2. Transfer (transfer responsibility to a third party)
3. Mitigate (reduce probability or impact)
4. Accept
initiative
emergency plan
contingency reserve
passive
contingency measures
management reserve
5. Report
Risks that have nothing to do with me
5. Opportunity response strategies
1. Improve (increase the probability or impact of an opportunity)
2. Development (allocate the most capable resources to the project)
3. Share (give opportunities to third parties for cooperation or joint bidding)
4. Accept
initiative
passive
5. Report
6. Emergency response strategies
7. Overall project risk response strategy
8. Data analysis
Alternatives analysis
Cost-benefit analysis
9. Decision-making
Multi-criteria decision analysis
output
1. Change request
2. Project management plan update
progress management plan
cost management plan
quality management plan
resource management plan
Procurement Management Plan
Scope Baseline
progress baseline
cost basis
3. Project file update
Hypothetical log
cost forecast
Lessons Learned Register
Project schedule
Project team dispatches work orders
Risk Register V4
secondary risk
residual risk
Bounce back plan
emergency plan
Trigger conditions/early warning signals (precursors)
risk report
11.6 Implement risk responses
The risk owner is responsible for implementation
11.7 Supervision risks
enter
1. Project management plan
risk management plan
2. Project files
Problem log
Lessons Learned Register
risk register
risk report
3. Work performance data
4. Work performance report
Tools & Techniques
1. Data analysis
Technical performance analysis
Reserve analysis (is it enough?)
2. Audit (on the process)
3. Meeting
risk review meeting
1. Reassess whether the probability and impact of currently identified risks have changed.
2. Identify new risks
3. Close obsolescence risk
4. Review the effectiveness of the emergency management plan
5. Audit
6. Summarize experiences and lessons
output
1. Work performance information
2. Change request
3. Project management plan update
any component
4. Project file update
Hypothetical log
Problem log
Lessons Learned Register
risk register
risk report
5. Organizational process asset update
10. Project communication management
10.1 Planning and communication management
enter
1. Project charter
2. Project management plan
resource management plan
Stakeholder Engagement Plan
3. Project files
requirements document
Interested Party Register
4. Business environment factors
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Communication needs analysis
3. Communication technology
4. Communication model
Cross-culture
5. Communication methods
Interactive communication: reaching consensus
Push communication: Failure to ensure audience understanding
Pull communication: large amount of information, large audience
6. Interpersonal and team skills
communication style assessment
political awareness
cultural awareness
7. Data performance
Stakeholder Engagement Assessment Matrix
8. Meeting
output
1. Communication management plan
Effective transmission of information, how to transmit information
Who needs to communicate
when to communicate
What information is communicated
where to find
what format
How to give
How to confirm understanding
2. Project management plan update
Stakeholder Engagement Plan
3. Project file update
Project schedule
Interested Party Register
10.2 Management communication (only look at red)
enter
1. Project management plan
resource management plan
communications management plan
Stakeholder Engagement Plan
2. Project files
Change log
Problem log
Lessons Learned Register
quality report
risk report
Interested Party Register
3. Work performance report
4. Business environment factors
5. Organizational process assets
Tools & Techniques
1. Communication technology (method)
2. Trench surge method
3. Communication skills (ability)
communication competency
feedback
nonverbal
Demo
4. Project management information system
5. Project report
6. Interpersonal and team skills
active listening
conflict management
cultural awareness
Conference management
interpersonal communication
political awareness
7. Meeting
output
1. Project communication records
2. Project management plan update
communications management plan
Stakeholder Engagement Plan
3. Project file update
Problem log
Lessons Learned Register
Project schedule
risk register
Interested Party Register
4. Organizational process asset update
10.3 Supervisory communication (only look at red)
enter
1. Project management plan
resource management plan
communications management plan
Stakeholder Engagement Plan
2. Project files
Problem log
Lessons Learned Register
Project communication records
3. Work performance data
4. Business environment factors
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Project management information system
3. Data analysis
Stakeholder Engagement Assessment Matrix
4. Interpersonal and team skills
observe/talk
5. Meeting
output
1. Work performance information
2. Change request
3. Project management plan update
communications management plan
Stakeholder Engagement Plan
4. Project file update
Problem log
Lessons Learned Register
Interested Party Register
9. Project resource management
9.1 Planning resource management
enter
1. Project charter
2. Project management plan
quality management plan
Scope Baseline
3. Project files
project progress plan
requirements document
risk register
Interested Party Register
4. Business environment factors
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Data performance
hierarchical
Responsibility Assignment Matrix RAM
text type
Document team member roles and responsibilities
3. Organization theory
4. Meeting
output
1. Resource management plan
Identify resources
Access to resources
Roles and Responsibilities
Project team resource management
Project organization chart
training
Team building
Resource control
accreditation scheme
How to carry out
2. Team charter
Team consensus
team values
Communication Meeting Guide
conflict resolution process
Decision Criteria and Process
Everyone in the team writes together
3. Project file update
Hypothetical log
risk register
9.2 Estimating activity resources
enter
1. Project management plan
resource management plan
Scope Baseline
2. Project files
Activity properties
Activity list
Hypothetical log
Cost Estimate
Resource Calendar
risk register
3. Business environment factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Bottom-up estimation
3. Analogous estimation
4. Parameter estimation
5. Data analysis
Alternatives analysis
6. Project management information system
7. Meeting
output
1. Resource requirements
2. Basis for estimation
3. Resource breakdown structure RBS
4. Project file update
Activity properties
Hypothetical log
Lessons Learned Register
9.3 Obtaining resources
enter
1. Project management plan
resource management plan
Procurement Management Plan
cost basis
2. Project files
Project schedule
Resource Calendar
Resource requirements
Interested Party Register
3. Business environment factors
4. Organizational process assets
Tools & Techniques
1. Decision-making
Multi-criteria decision analysis
2. Human relations and teamwork skills
negotiation
1. Functional manager
2. Other project management teams
3. Initiator
4. External organizations and suppliers
3. Pre-allocation
Personnel assigned by contract and project charter
4. Virtual Team
in different geographical locations
output
1. Material resource allocation list
2. The project team dispatches work orders
3. Resource Calendar (Availability)
4. Change request
5. Project management plan update
resource management plan
cost basis
6. Project file update
Lessons Learned Register
Project schedule
resource breakdown structure
Resource requirements
risk register
Interested Party Register
7. Update of business environment factors
8. Organizational process asset update
9.4 Building the team
enter
1. Project management plan
resource management plan
2. Project files
Lessons Learned Register
Project daily progress plan
Project team dispatches work orders
Resource Calendar
Team charter
3. Business environment factors
4. Organizational process assets
Tools & Techniques
1. Centralized office
The most powerful means to improve project performance
2. Virtual Team
Create an online environment
3. Communication technology
4. Interpersonal and team skills
conflict management
Influence
excitation
negotiation
Team building
5. Recognition and rewards
formal
award
refer to
expert
punish
6. Training
1. Insufficient ability and experience
2. New tools and new technologies
3. Resource management plan
4. Don’t abandon, don’t give up
7. Individual and team evaluation
8. Meeting
output
1. Team performance evaluation
Improvement of member skills
Improvement of team capabilities
Reduced member turnover rate
Strengthened team cohesion
2. Change request
3. Project management plan update
resource management plan
4. Project file update
Lessons Learned Register
Project schedule
Project team dispatches work orders
Resource Calendar
Team charter
5. Update of business environment factors
6. Organizational process asset update
9.5 Management Team
enter
1. Project management plan
resource management plan
2. Project files
Problem log
Lessons Learned Register
Project team dispatches work orders
Team charter
3. Work performance report
4. Team performance evaluation
5. Business environment factors
6. Organizational process assets
Tools & Techniques
1. Interpersonal and team skills
conflict management
1. Cooperation/resolution: Both parties reach an agreement and completely solve the problem
2. Avoidance/Procrastination: Let others solve it
3. Force/adopt: use power to solve urgent problems forcefully (adopt one side, sacrifice the other)
4. Relaxation/tolerance: seek common ground while reserving differences, sacrifice interests to satisfy the other party, and maintain relationships; Both parties have reservations and the problem may arise again. (does not resolve conflicts)
5. Compromise/Mediation: Partially resolve the conflict and be relatively satisfied to a certain extent
Make decisions
Emotional intelligence
Influence
leadership
2. Project management information system
output
1. Change request
2. Project management plan update
resource management plan
progress baseline
cost basis
3. Project file update
Problem log
Lessons Learned Register
Project team dispatches work orders
4. Update of business environment factors
9.6 Controlling resources
management communication
Update communication plan
Update participation plan
Supervise interested parties
management communication
communication plan
Manage stakeholders
Participate in the program
Identify interested parties
change request
quality measures Quality control measurement results
Verified deliverables Quality control measurement results
quality report Assessment documents
quality management plan quality measures
quality measures Deliverables Approved change request
Project Charter project management plan requirements document Interested Party Register risk register
Control quality
Management quality
Plan quality management
project team members
Project stakeholders
Project communication records
Each project process
Project change control
floating theme
Overall project control
control process
Implementation process