Mindmap
4. PROJECT INTEGRATION MANAGEMENT
Inhalt der Mindmap
4. PROJECT INTEGRATION MANAGEMENT
4.1 Develop Project Charter
- Process of developing a document that formally authorizes the existence of a project and provides the project manager
- 1 Inputs
- Agreements
- Used to define initial intentions for a project,
- Enterprise environmental factors
- Government or industry standards
- Legal and regulatory requirements and/or constraints
- Marketplace conditions
- Organizational culture and political climate
- Organizational governance framework
- Stakeholders’ expectations and risk thresholds
- Business case
- Organizational process assets
- Historical information and lessons learned repository
- Agreements
- 2 Tools & Techniques
- Expert judgment
- Data-gathering
- Brainstorming
- Is used to identify a list of ideas in a short period of time
- Focus groups
- Bring together stakeholders and subject matter experts to learn about the perceived project risk, success criteria
- Interviews
- Used to obtain information on high-level requirements, assumptions or constraints, approval criteria
- Brainstorming
- Interpersonal and team skills
- Conflict management
- Facilitation
- Meeting management
- Meetings
- Are held with key stakeholders to identify the project objectives, success criteria, key deliverables, high-level requirements, summary milestones, and other summary information
- Assumptions log
- 3 Outputs
- Project Charter
- It documents the high-level information on the project and on the product, service, or result the project is intended to satisfy
- The document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities
- Project Charter
- Benefits: provides a direct link between the project and the strategic objectives of the organization, creates a formal record of the project, and shows the organizational commitment to the project
4.2 Develop Project Management Plan
- Process of defining, preparing, and coordinating all plan components and consolidating them into an integrated project management plan.
- 1 Inputs
- Outputs from other processes
- Are integrated to create the project management plan
- Outputs from other processes
- 2 Tools & Techniques
- Expert judgment
- Data-gathering
- Checklists.
- Meetings
- 3 Outputs
- Project management plan
- Describes how the project will be executed, monitored and controlled, and closed.
- integrates and consolidates all of the subsidiary management plans and baselines, and other information necessary to manage the project
- Project management plan
- Benefits: this process is the production of a comprehensive document that defines the basis of all project work and how the work will be performed
4.3 Direct and Manage Project Work
- Process of leading and performing the work defined in the project management plan and implementing approved changes to achieve the project’s objectives.
- 1 Inputs
- Project management plan
- Any component of the project management plan
- Approved change requests
- May be a corrective action, a preventive action, or a defect repair
- Project management plan
- 2 Tools & Techniques
- Expert judgment
- Meetings
- Project management information system
- PMIS provides access to information technology (IT) software tools
- 3 Outputs
- Deliverables
- Work performance data
- Are the raw observations and measurements identified during activities being performed to carry out the project work.
- Change requests
- is a formal proposal to modify any document, deliverable, or baseline.
- Corrective action
- Preventive action
- Defect repair
- Updates
- Defect repair
- Preventive action
- Project management plan updates
- Project documents updates
- Issue Log
- is a project document where all the issues are recorded and tracked.
- Benefits: is that it provides overall management of the project work and deliverables, thus improving the probability of project success.
4.4 Manage Project Knowledge
- Process of using existing knowledge and creating new knowledge to achieve the project’s objectives and contribute to organizational learning.
- 1 Inputs
- Project management plan
- Project documents
- Deliverables
- Enterprise environmental factors
- Organizational process assets
- 2 Tools & Techniques
- Expert judgment
- Knowledge management
- Information management
- Interpersonal and team skills
- Active listening
- Facilitation
- Leadership
- Networking
- Political awareness
- 3 Outputs
- Lessons learned register
- Project management plan updates
- Any component
- Organizational process assets updates
- Benefits of this process are that prior organizational knowledge is leveraged to produce or improve the project outcomes, and knowledge created by the project is available to support organizational operations and future projects or phases.
4.5 Monitor and Control Project Work
- Process of tracking, reviewing, and reporting overall progress to meet the performance objectives defined in the project management plan.
- 1 Inputs
- Project documents
- Assumption log
- Basis of estimates
- Cost forecasts
- Issue log
- Lessons learned register
- Milestone list
- Quality reports
- Risk register adn Risk report
- Schedule forecasts
- Project documents
- 2 Tools & Techniques
- Data analysis
- Alternatives analysis
- Cost-benefit analysis
- Earned value analysis
- Root cause analysis
- Trend analysis
- Variance analysis
- Data analysis
- 3 Outputs
- Work performance reports
- is combined, recorded, and distributed in a physical or electronic form in order to create awareness and generate decisions or actions
- Project documents updates
- Cost forecasts • Issue log • Lessons learned register • Risk register • Schedule forecasts
- Work performance reports
- Benefits: this process are that it allows stakeholders to understand the current state of the project, to recognize the actions taken to address any performance issues, and to have visibility into the future project status with cost and schedule forecasts
4.6 Perform Integrated Change Control
- Process of reviewing all change requests; approving changes and managing changes to deliverables, organizational process assets, project documents, and the project management plan; and communicating the decision
- 1 Inputs
- Project management plan
- - Change management plan • Configuration management plan • Scope baseline • Schedule baseline • Cost baseline
- Project documents
- • Basis of estimates • Requirements traceability matrix • Risk report .3 Work performance
- Project management plan
- 2 Tools & Techniques
- Data analysis • Alternatives
- • Alternatives analysis • Cost-benefit analysis
- Decision making
- • Voting • Autocratic decision making • Multicriteria decision analysis
- Data analysis • Alternatives
- 3 Outputs
- Approved change requests
- are processed according to the change management plan by the project manager,
- Approved change requests
- Benefits: this process is that it allows for documented changes within the project to be considered in an integrated manner while addressing overall project risk, which often arises from changes made without consideration of the overall project objectives or plans.
4.7 Close Project or Phase
- The process of finalizing all activities for the project, phase, or contract.
- 2 Tools & Techniques
- Data analysis
- • Document analysis • Regression analysis • Trend analysis • Variance analysis
- Data analysis
- 3 Outputs
- Final product, service, or result transition
- 1 Inputs
- Project documents
- • Assumption log • Basis of estimates • Change log • Issue log • Lessons learned register • Milestone list • Project communications • Quality control measurements • Quality reports • Requirements documentation • Risk register • Risk report .4 Accepted deliverables
- Business documents
- • Business case • Benefits management plan
- Project documents
- Benefits: this process are the project or phase information is archived, the planned work is completed, and organizational team resources are released to pursue new endeavors.
Informationen
- Beschreibung
- Mindmap am 4. PROJECT INTEGRATION MANAGEMENT, erstellt von MARILUZ TAYPE ALMONACID am 28/03/2018.
- Erstellt von
- MARILUZ TAYPE ALMONACID
- Aufrufe
- 1
- Bewertung