MindMap Gallery Project integration management
Project integration management mind map, including formulating project charter, formulating project management plan, guiding and managing project work, managing project knowledge, monitoring project work, etc.
Edited at 2021-11-23 14:15:58One 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.
04 items Integrated management
Have the big picture in mind! Plan carefully! Be flexible and make changes!
The most important thing for a project manager is integration ability
4.1 Develop project charter
Purpose: To formally approve the project and authorize the project manager to use resources
enter
Business case document, benefit management plan
The project manager cannot make necessary updates or modifications to business documents and can only make relevant suggestions.
Agreement/Contract
business environment factors
Government or industry standards, market conditions, organizational culture and political climate
Risk thresholds, stakeholder expectations
organizational process assets
The organization’s standard policies, processes and procedures
output
Project Charter
who drafted
Drafted by the sponsor or authorized project manager
who issued
Issued by promoters and senior executives
Two effects
Confirm project manager candidate; authorize project manager to use resources
Whoever issued it has the right to modify it
The project charter cannot be a contract
Contents of the project charter
Project goals, measurable success criteria, high-level requirements, Overall project risk, overall milestone schedule, pre-approved financial resources, List of key stakeholders, project approval requirements, project exit criteria, Delegated project manager and his/her responsibilities and authorities
Hypothetical log
Assumptions
The characteristic is that it is likely to occur
Constraints
Features already exist
Tools & Techniques
expert judgment
data collection
Brainstorming
A lot of creativity, face to face, fast, not objective
Does not include voting or ranking per se and is often used with other techniques
Interview
focus group
Gather 6 to 10 people with the same background in a certain area to discuss the questions raised by the host
Interpersonal and team skills
conflict management
guide
Neutral person, promotes the team to actively and equally participate in discussions and reach consensus
Conference management
Meeting
Conduct meetings with key stakeholders to identify project objectives, success criteria, key deliverables, high-level requirements, overall milestones and other summary information
kick-off conference (become excited)
It is held at the end of the initiation process, convened and organized by the project sponsor, and the participants are the main stakeholders
main agenda
Distribute the project charter to ensure a shared understanding of the project purpose
Announce the candidate for the project manager and give an inaugural speech to announce the official launch of the project
4.2 Develop project management plan
Purpose: Define, prepare, and coordinate all components of the project plan and integrate them into a comprehensive project management plan
enter
Project charter, enterprise environmental factors, organizational process assets
Other sub-management plans
output
project management plan
10 2 Sub plan
scope management plan, requirements management plan, schedule management plan, cost management plan, quality management plan, resource management plan, Communication management plan, risk management plan, procurement management plan, Stakeholder Engagement Plan
configuration management plan, change management plan
3 1 benchmark
Scope Baseline
Create output of WBS
progress baseline
Develop schedule output
cost basis
Budget output
performance measurement benchmarks,
Integrated three major benchmarks for PM assessment, often using earned value
3 components
Project life cycle, development methodology, management review
approve
Once the project management plan is developed, it should be formally approved by all key stakeholders before it can be executed.
Tool technology
Consistent with developing the project charter
Project opening ceremony
The planning phase ends and is held before the execution phase
It means that startup is over and execution starts immediately
Organized by the project manager and project sponsor, with participants being major stakeholders
main agenda
Introduce the project plan so that all relevant parties have a common understanding of the project
Gain stakeholder commitment to goals
Officially declare that the project has entered the execution stage
4.3 Direct and manage project work
Purpose: Direct and manage planned work and implement approved changes
enter
project management plan
Approved change request
Corrective Actions, Preventive Actions, Defect Remediation, Updates
output
Deliverables
Deliverable products, deliverable documents
Can be project management plan, project documents
Clues to change: 1 Deliverables (direct and manage project work) 2 Verified deliverables (control quality) 3 Acceptance deliverables (confirmation scope) 4 Final deliverable handover (end project or phase)
job performance data
Raw data collected during execution, usually at the lowest level of detail. Such as: planned time, actual time, progress, number of changes
1. Integrate and analyze original data to obtain work performance information
2. To make decisions, raise questions, take action or draw attention, Compile job performance information to form job performance reports
Source: (6 3 1) Control scope, control progress, control cost, control quality, control resources, control procurement, Supervise communication, supervise risks, supervise participation of relevant parties, Confirm scope
Clues of change (lines of work): 1 Job performance data (directing and managing project work) 2 work performance information (6 controls, 3 supervision, 1 confirmation) 3 Work performance report (supervise project work) 4Implement overall change control, manage team, manage communication, and control risks
Problem log
One of the three major logs, in directing and managing project work (first created)
Logging and rooting all issues into project files
Content includes: type of question; who raised it and when; Description; priority; who is responsible for resolving the problem; Target problem solving; problem status; remarks
change request
Concept: A formal proposal to modify any document, deliverable, or baseline
Any interested party can submit a change request
changed 4 types
Corrective Action
For deviations that have actually occurred
Precaution
for deviations that may occur in the future
Defect Remedies
Quality defects for deliverables
renew
Modifications to a formally controlled project management plan or project documents
If there are too many changes, the reasons must be found from the three constraints. Scope is the leader. First, review the scope.
Tools & Techniques
project management information system
Automated software tools for collecting and publishing a variety of data
4.4 Managing project knowledge
Purpose: Use existing knowledge and generate new knowledge to achieve project goals
explicit knowledge
Glyphs that are easy to edit using text, pictures and numbers
tacit knowledge
Individual knowledge and knowledge that is difficult to articulate, such as beliefs, insights, experience, and know-how
enter
Project management plan, project documents
Lessons Learned Register, Project Team Dispatch Work Orders, Resource Breakdown Structure, Stakeholder Register
organizational process assets
The organization’s standard policies, processes and procedures, personnel management systems, Organizational communication requirements, knowledge sharing and information sharing procedures
Deliverables, career environment factors
output
Lessons Learned Register
Content: Challenges and Opportunities, Lessons Learned, Types, Action Plans and Recommendations
Tool technology
expert judgment
knowledge management
Methods used to promote employees to share tacit knowledge, integrate personal knowledge and cooperation, and create new knowledge
The transfer of tacit knowledge is the relationship between people. Face-to-face interaction is best for building the trusting relationships required for knowledge management
Interpersonal interactions, seminars, wrap-up sessions, storytelling, discussion forums such as focus groups
Work following and following guidance
Creativity and Idea Management Techniques
Knowledge sharing activities such as lectures and conferences, interactive training
information management
Various methods used to facilitate the sharing of explicit knowledge, belonging to the connection between people and knowledge
Methods for compiling explicit knowledge, registers of lessons learned
Library services, information collection, project management information systems
Interpersonal and team skills
Active listening, guidance, leadership, interpersonal communication, political awareness
4.5 Monitor project work
Purpose
supervise
Compare actual execution with plan to identify deviations
control
Analyze deviations and make necessary change requests
enter
job performance information
Identify the extent of deviations, analyze causes, and predict future performance
protocol
For outsourced work, supervision of the contractor’s work is required
Project management plan, project documents, enterprise environmental factors, organizational process assets
output
job performance report
A document that compiles job performance information
Analysis of past performance, performance information on percent complete, Status information for each area (scope-schedule-cost-quality)
Summary of work completed during this period and changes approved during this reporting period
Current risk and issue status
Forecast analysis of work to be completed in the next period, time and cost
Purpose: To make decisions, take action or attract relevant attention
Change requests, project management plan updates, project document updates
Tools & Techniques
data analysis
Deviation analysis
Determine the deviation between actual and target. Conduct comprehensive analysis of cost, schedule, technology and resource variances. In order to understand the overall deviation situation and take appropriate measures
Alternatives Analysis
Used to select the combination of corrective and preventive actions to be implemented when a deviation occurs
Cost-benefit analysis
Determine the most cost-effective corrective measures when deviations occur
Earned value analysis, root cause analysis, trend analysis
Expert judgment, decision-making, meetings
4.6 Implement holistic change control
Purpose: Approval of various change requests
enter
job performance report
Includes: resource availability, schedule and cost data, earned value reports, burn charts or burndown charts
Change requests, business environment factors, organizational process assets, project management plan, project documents
output
Approved change request, project management plan
Project file updates
Change log
Changes that occur during the project, whether approved or not, must be updated in the change diary
Content: description, approval status (approved/rejected/postponed), processing results
Tools & Tips
expert judgment
change control tools
For example: change tracking software and version control software
data analysis
Alternatives analysis, cost-benefit analysis
decision making
vote
majority consent
autocratic decision making
One person is responsible for making decisions for the group
Multi-criteria decision analysis
Use the decision matrix to systematically analyze changes using predefined criteria
Meeting
Convene change control meetings with the change control committee
Change special items
What are the types of change requests?
Corrective Actions, Preventive Actions, Defect Remediation, Updates
Who can make a change request?
Anyone who must do so in writing
Changes that have been implemented in an emergency, or if a team member is gold-plated, a change request must also be submitted
Who has the authority to approve changes?
Changes to the project charter, the person who signed or approved the charter has the authority to approve
Changes to the baseline are approved by the Change Control Board CCB
The project manager has the authority to approve changes that do not change the project baseline or in emergency situations
Changes to terminate the project early can only be approved by the sponsor
Approval of changes Processes and principles?
triple constraints relation
A single move affects the whole situation
scope, time, cost, quality, Risks, resources, stakeholder satisfaction
Whether the change is approved or not depends on what stage of the project it is at and what impact it will have on the project?
At the end of the project, it is not appropriate to make major changes. For major changes, it may be recommended to sign a new contract.
How do project managers deal with change?
When empowered: Be proactive - approve, deny or defer
When you have no authority: make suggestions after analysis and then report to superiors
Things that cannot be done outside the scope
Follow instructions from senior management
Political factors, sponsor funding issues, organizational strategic adjustments
change control boardccb
A group composed of the project's key stakeholders that primarily approves changes to the baseline
Responsible for reviewing and evaluating decisions to approve, reject, and postpone changes
Change process
1. Identify changes (any changes should be reported to the project manager first) 2. Formally propose and record the change (the change request is updated to the change log first) 3. Analyze and evaluate changes; (first review the impact in the field and then conduct a comprehensive review) 4. The project manager submits the changes to the Change Control Board (CCB); (changes involving baselines) 5.CCB approves or rejects the change request and updates the change log; a written decision to approve, reject or suspend the change request 6. Update project management plan and project documents 7. Notify the relevant parties of the changes 8. Implement change requests 9. Review whether approved change requests are implemented in place 10. Summarize experiences and lessons learned.
The foothold of change management
Manage changes at source to reduce unnecessary changes
Communicate fully with customers, keep the same if possible, change as little as possible, and formally propose and implement the change process if changes are necessary.
Communicate the results of change processing
During the change process and after the change is completed, relevant parties must be notified in a timely manner, and the change implementation status must be tracked and recorded.
During the implementation of the change process, continuous communication with relevant parties is required
4.7 End project or phase
What work needs to be done?
Obtain final acceptance of project deliverables from key stakeholders
Hand over project deliverables to designated stakeholders
Prepare and distribute final project performance report
Collect, organize and archive project data and update organizational process assets for reference in future projects
Collect feedback on the project from all relevant parties to understand satisfaction
Conduct post-project evaluations, summarize experiences and lessons learned, and update organizational process assets
Carry out financial, legal and administrative closure, declare the project officially closed and ensure the transfer of responsibilities
Release resources and disband the project team
enter
Project Charter
Documents project success criteria, approval requirements, and who will sign off on project closure
project files
Assumption log, project communication record, quality control measurement results, change log quality report, issue log (used to confirm that there are no unresolved issues) risk register, lessons learned register, risk report
Deliverables for acceptance
Includes approved product specifications, delivery receipts and work performance documentation
business documents
Business case to determine whether the project achieves the expected results of the economic feasibility study
Benefit management plan, measuring whether the project has achieved planned benefits
protocol
Requirements for formal closing of procurement defined in contract terms
Procurement documents
To close the contract, all procurement documents need to be collected and indexed
output
Lessons Learned Register
Handover of final product results
Handed over to designated parties to operate, maintain and support the product throughout its lifecycle
final report
Summarize project performance with final report
Organizational process asset updates
Project or phase closing documents; if the project is terminated early, the reasons must be stated, and hand over completed/unfinished results
Project documents, operational and support documents, lessons learned knowledge base
Tools & Techniques
data analysis
Document analysis, summarizing lessons learned, sharing knowledge, and improving future projects
Regression analysis: Analyze the relationship between variables and results to improve future project performance
Trend analysis: Confirm the effectiveness of the organizational model and make adjustments for the future
Deviation Analysis: Analyze deviations to improve your organization’s measurements
Meeting
Closing report meeting, customer summary meeting, experience and lesson summary meeting, celebration party, etc.