PMP Project Management Foundations Course

A project creates a unique product, service, or result within defined constraints. The most common constraints are scope, schedule, cost, quality, resources, and risk. Projects are organized into five process groups: initiating, planning, executing, monitoring and controlling, and closing.

Knowledge areas describe the specialized practices you apply, including integration, scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder management. The project manager selects a life cycle that fits the work: predictive, iterative, incremental, agile, or hybrid.

The project charter formally authorizes the project and gives the project manager authority. The business case explains why the project should exist, while stakeholder identification begins early so needs and expectations are understood.

Process group drill: map each activity to one of the five process groups: initiating defines the project, planning sets baselines, executing does the work, monitoring controls changes, and closing finalizes deliverables. Use the knowledge areas to organize the professional practices.

Scope management turns requirements into a clear deliverable list. The work breakdown structure (WBS) breaks work into manageable components, and the scope baseline is controlled through change requests. Scope creep occurs when unapproved changes expand the work.

Schedule management builds a network diagram of activities, dependencies, and durations. The critical path is the longest path of dependent activities; a delay on the critical path delays the project. Float measures how long an activity can slip without affecting the finish date.

Cost management estimates, budgets, and controls spending. Earned value management compares planned value (PV), earned value (EV), and actual cost (AC). Schedule performance index (SPI) and cost performance index (CPI) show whether the project is ahead or behind on schedule and budget.

Baseline loop: define scope in the WBS, build the schedule from dependencies and durations, and estimate cost with bottom-up techniques. Any change must update the baselines through a formal change request to avoid scope creep and uncontrolled cost.

Quality management ensures deliverables meet requirements, not just that work is complete. Quality assurance evaluates processes, while quality control inspects outputs. The cost of quality includes prevention, appraisal, and failure costs; investing in prevention is usually cheaper than correcting defects later.

Resource management plans how team members and physical resources are acquired, developed, and released. A RACI chart defines who is responsible, accountable, consulted, and informed for each task. Resource calendars show availability and constraints.

Communication management matches information to the right audience. A communication plan states what is shared, with whom, through which channel, and how often. Clear communication reduces misunderstandings, and conflict resolution should focus on issues rather than personalities.

Quality and resource drill: use QA to improve processes and QC to inspect outputs; invest in prevention to reduce failure costs. Use a RACI matrix to clarify roles, plan team acquisition and development, and tailor communication to each stakeholder.

Risk management identifies uncertain events that could affect the project. Qualitative analysis scores probability and impact, while quantitative analysis models overall exposure. Risk responses include avoid, mitigate, transfer, accept, and exploit. The risk register tracks each risk, its owner, and the response plan.

Procurement management selects vendors and manages contracts. Contract types include fixed-price, cost-reimbursable, and time and materials; each shifts risk between buyer and seller. Procurement documents define scope, acceptance criteria, and responsibilities.

Stakeholder engagement maps stakeholders by power and interest, then plans communication and involvement. Engagement levels range from unaware, resistant, neutral, and supportive to leading. Change control reviews requests and protects the approved baselines.

Risk response drill: for threats choose avoid, mitigate, transfer, or accept; for opportunities choose exploit, enhance, share, or accept. Track each risk in the register with an owner and response plan, and choose the contract type that matches the procurement risk.

Agile approaches deliver value in short iterations and welcome changing requirements. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change. Scrum uses sprints, roles such as product owner and scrum master, and events such as sprint planning, daily stand-up, sprint review, and retrospective.

Kanban visualizes work and limits work in progress. Hybrid approaches combine predictive planning with iterative delivery when requirements are uncertain but some constraints are fixed. The project manager acts as a servant leader, removing obstacles and empowering the team.

Professional responsibility includes honesty, transparency, and ethical decision-making. Project managers protect confidential information, disclose conflicts of interest, and apply the PMI Code of Ethics even when no one is watching.

Approach selection: use agile when requirements are uncertain and value can be delivered in increments; use predictive when scope is stable; use hybrid when parts of the project are fixed and others benefit from iteration. Always act with honesty and respect stakeholders.