Project Integration Management Overview

A project is defined as a sequence of tasks that must be completed within certain boundaries to attain a specific outcome with a definite beginning and end.
Projects have a definite outcome, clear start and end dates, scope of size, time, budget, resources, quality and functionality.
Projects involve one or many people.

It is the coordination of all elements of a project, including tasks, resources, stakeholders, and other project elements.
It also involves managing conflicts between different aspects of the project, making tradeoffs, and evaluating resources.

Define the Problem: Clearly define the problem to be solved.
Develop Solution Options: Brainstorm ideas and potential solutions.
Plan the project: What must be done, who will do it, how will it be done, when it must be done, how much will it cost, what do we need to do it.
Execute the Plan: Put the plan into action or put the solutions into effect.
Monitor and control Progress: Track progress against the plan and make adjustments as needed, asking the question are we on target? If not, what must be done? Should the plan be changed?
Close Project: Evaluate the project and assess what was done well and what could be improved.

The project manager is responsible for ensuring that all project work is completed on time, within budget, and scope.

Ten project management skills are listed including Time Management, Goal Setting, Strong Collaboration, Problem Solving, Team Building, Conflict Resolution, Leadership Skills, Negotiation Skills, Communication Skills, Critical Thinking and Adaption.
Organization Skills and Skills Management are also referenced in the slides.

Includes Initiation (Develop Project Charter), Planning (Develop Project Management Plan), Executing (Direct and manage project work/Manage project knowledge), Monitoring and Controlling (Monitor & Control project work/Perform Integrated change control) and Closing (Close Project or Phase).

Uses outputs from other planning processes to create a consistent and coherent document to guide project execution and control.
Initial drafts may include generic resources and undated durations, while the final plan should incorporate specific resources and explicit dates.

A project plan contains all details in one document.
A project charter authorizes work, defines project team authorities, responsibilities, and accountabilities, and establishes scope boundaries.
When these documents aren't developed, team members may misinterpret requirements.

Specific: Concrete and tangible goals that everyone understands.
Measurable: Goals with objective measures of success.
Attainable: Goals that are challenging but achievable with available resources.
Relevant: Goals that contribute to the larger mission or objectives.
Timely: Goals with deadlines or timelines for progress.

Financial: Rising material costs, additional labor and resources, budget needs.
Strategic: Project dependencies, use of new technologies.
Performance: Missed deadlines, outdated market research, project quality, customer satisfaction.
External: Employee leave-taking/illness, major weather conditions, changing laws.

A component of the project plan that sets out the scope, budget, and schedule of a project.
The progress of the work is measured against the baseline.
Helps the project manager and stakeholders determine the project's status against the schedule, budget, and scope.

Identify project objectives, deliverables, and requirements.
Document the scope statement, outlining what is included and excluded from the project.
Develop a Work Breakdown Structure (WBS).
Break down project deliverables into smaller tasks.
Organize tasks hierarchically using the WBS.

Identify all project costs including labor, materials, equipment, and overhead.
Estimate costs for each activity based on resource requirements and market rates.
Aggregate estimated costs to create a cost baseline;
Include contingency reserves for uncertainties and risks.
Document the performance measurement baseline (PMB).

Envision: Identify client requirements, resources, and project goals. Then brainstorm expected timeline and project approach.
Speculate: Identify and document all decisions, creating solutions to meet the project needs.
Explore: Work on project deliverables, exploring and defining alternatives.
Adapt: Review project results to make adjustments based on feedback. Also identify what has been learned.
Close: Formalize project completion and compile key lessons learned.

7 steps to guide integration management including: Develop project charter, develop a project management plan, direct and manage the project, manage project knowledge, monitor and control project work, perform integrated change control, and close the project.
The Agile process emphasizes dynamic baselines, self-organizing teams, active knowledge gathering, daily stand-up meetings for planning. The process also emphasizes establishing a process for approving changes and conducting a final retrospective for project closure.

Scrum: iterative, time-boxed approach with sprints.
Kanban: workflow visualization system without sprints, emphasizing continuous flow.

Waterfall: Linear, sequential process with defined phases, with very little flexibility to adjust plans during implementations.
Agile: iterative process focused on adapting to changes, with frequent feedback loops and continuous improvement.