Integration Management Flashcards
Project Integration Management
includes the processes needed to identify, define, authorize, and coordinate the various processes and project management activities across the project management process groups. the processes in this knowledge area set the foundation for how all other processes will be performed and interact with one another
the only knowledge area that includes processes from all five process groups
Project Integration Management
- Processes
- Develop Project Charter (Initiating)
- Develop Project Management Plan (Planning)
- Direct and Manage Project Work (Executing)
- Manage Project Knowledge (Executing)
- Monitor and Control Project Work (Monitoring and Controlling)
- Perform Integrated Change Control (Monitoring and Controlling)
- Close Project or Phase (Closing)
Develop project charter
a process for the project sponsor (champion) to document the formal authorization of a project, name, and authorize the project manager, and provide high-level descriptions of the project needs, initial requirements, and expected outcome
Develop project charter
- key inputs
- Business documents
- business case
- benefits management plan
- agreements
Develop project charter
- key outputs
- project charter
project management business documents
include the business case and benefits management plan. while the sponsor and/or program manager may play an active role in developing and maintaining these documents, the project manager is responsible for ensuring their alignment with the project management plan and charter
business case
documentation detailing the project as it fits into the performing organization’s strategic goals, and why it was chosen. Typically the business case will be economically focused and should list the objectives and reasons for project initiation based on a needs assessment. major components may include: business needs, analysis of environment, options or alternatives, recommendation, and measurement approach
benefits management plan
describes how and when the business value will be realized, measures, and transitioned to the organizations ongoing operations. major components may include: target benefits, strategic alignment, timeframe for realizing benefits, benefits owner, metrics, assumptions, risks
Organizational process assets
project related assets that may be used to influence the project’s success. these assets include formal and informal plans, methodologies/processes, policies, procedures, and guidelines. the process assets also include the organization’s knowledge bases such as historical data, templates, and past project documentation. Organizational process assets may also commonly be referred to as lessons learned
enterprise environmental factors
conditional outside of the projects direct control that can influence the execution of the project. these can include conditions internal to the performing organization such as organizational structure, culture, governance, and existing systems. these can also include the surrounding project environment such as physical geography, marketplace conditions, government standards, political/social climates, and evolving technology
standards
common guidelines used to determine the “best practices” for a process. they can be general or industry specific
regulations
a formal requirement mandated by the federal, state, or local government
expert judgment
provided from an individual or group with specialized knowledge
data gathering
can include:
brainstorming
focus groups
interviews
conflict management (interpersonal and team skill)
a technique to create alignment on objectives, success criteria, requirements, and other elements of the charter
facilitation (interpersonal and team skill)
a technique to use a facilitator to help drive group decisions by ensuring participation, all contributions considered, mutual understanding of ideas, and conclusion with buy-in
meeting management (interpersonal and team skill)
ensuring meeting agendas, that key stakeholders are invited, and sending follow-up minutes and actions.
project charter
a document signed by the project sponsor that formally initiates the project, names and authorizes the project manager and provides high-level stakeholder requirements and expectations.
other elements could include
- measurable project objectives
- success criteria
- assumptions and constraints
- high-level risks
- high-level cost expectations
can be used to identify initial stakeholders such as the sponsor, project manager, customer, and end users
assumptions log
a document of high-level strategic assumptions about the projects found in the charted and will be used to track more tactical assumptions and constraints about the projected throughout the project lifecycle
develop project management plan
developing a project plan includes the actions necessary to initiate and revise all subsidiary plans into a single document.
the primary purpose is to document the tailored management approach (how) and the approved baselines (what). the project management plan is an input to a total of 21 other processes.
includes all management plans and baselines and stakeholder engagement plan
develop project management plan
- key inputs
- project charter
- outputs from other processes
develop project management plan
- key outputs
- project management plan
outputs from other planning processes
subsidiary plans re created in other project planning processes and once developed are considered to be part of the project management plan. includes all management plans and baselines and stakeholder engagement plan.
expert judgement
can be used to help define a management approach that is tailored to unique needs and requirements or the project
data gathering - checklists
an organizational document that may have steps or requirements defined to ensure all required information is included in the project management plan
are structured documents used to verify that required actions are performed during an inspection. quality checklists will serve as an input to the quality control process
help provide standardization during inspection
project management plan
a formal, approved document that defines how the project is executed, monitored, and controlled. depending on the complexity of the project, it may be detailed or summarized, it should include how project management processed will be tailored to the uniqueness of the project, which processes will be used for each phase, and which tools and techniques will be utilized.
includes all management plans and baselines and stakeholder engagement plan.
change management plan
defines the formalized change control system that will be used to control, change, and approve project baselines
configuration management plan
defines technical and administrative direction for the identification, control, tracking, and approval levels of items requiring change throughout the project, such as project documents and deliverables
project lifecycle description
defines the phase relationship of the work such as: predictive, iterative, agile, or hybrid approach
project development approach
describes a series of phases that the project will progress through the beginning to the end of the project
direct and manage project work
this process is the execution of work packages in accordance with the baselines established by the project management plan. This is where the project manager provides the overall management of the project work. Approved changes must also be properly integrated into the project execution throughout the project lifecycle.
direct and manage project work
- key inputs
- project management plan
- approved change requests