PMP Certification Exam Preparation Full Course with 35 PDUs

Projects are temporary, unique endeavors that create a distinct product, service, or result, unlike operations. They start with initiation, are constrained by resources, and end when objectives are met.

Understand project management as applying knowledge, skills, tools, and processes to deliver the right product on time by managing risks, issues, changes, scope, quality, schedule, costs, and resources.

Explore the PMI talent triangle, uncovering ways of working, power skills, and business acumen as foundations for the PMP exam domains and value delivery, including social responsibility.

Explore the project life cycle and its phases from pre-project through closure, detailing deliverables and contrasting predictive versus adaptive development approaches.

Explore five project development approaches, from predictive (plan-driven, waterfall) to agile, and learn when to apply incremental, iterative, adaptive, and hybrid strategies.

Use Stacey Matrix, Ralph Stacey's model, to decide predictive, agile, or hybrid approaches mapping requirement uncertainty and solution complexity, and categorize projects as simple, complicated, complex, or chaotic (fuzzy).

Explore the Stacy model matrix, matching project types to requirement uncertainty and solution complexity. Learn when to apply predictive, incremental, iterative, adaptive, and hybrid approaches, avoiding chaos projects.

Plot nine attribute scores on a multivariate spider chart to decide agile, predictive, or hybrid projects. Identify the zones, connect the dots, and assess agile suitability.

Discover how the predictive development approach handles simple, low-complexity projects with clear requirements through upfront planning, a project charter, frozen baselines, and one-shot execution.

Learn the incremental development approach, splitting complex projects into small, independent increments like online banking features (account summary, money transfer, mobile notification), to deliver value early and gain client feedback.

Explore iterative development within an agile, incremental approach, using iterations and client feedback to progressively discover and elaborate requirements, demos, and refinements until a final product is shipped.

Adaptive development combines incremental and iterative methods to manage high complexity and uncertain requirements through feedback loops and small increments, forming the final product.

Discover the hybrid development approach, using predictive for mechanical and electrical components and agile for software, with guidance on product backlog, WBS, and when to choose each.

Compare the five development approaches in project management, with a downloadable pdf sheet from the resources tab to aid exam preparation.

Assess which development approach is unsuitable for incremental delivery by comparing incremental, adaptive, hybrid, iterative, and predictive methods, and identify why iterative development cannot deliver increments.

Explore the PMBOK 8th edition process map, consolidating 48 into 40 processes organized by seven performance domains and five focus areas to deliver value.

explore how agile way of working contrasts with predictive planning using small planning and execution cycles, increments, and iterations or sprints to deliver software piece by piece.

Explore the scrum framework and its time-boxed sprints, product backlog, sprint backlog, and ceremonies that drive incremental delivery through planning, execution, daily stand-ups, demos, and retrospectives.

Identify scrum ceremonies, artifacts, and roles, including sprint planning, daily stand up, sprint review, retrospective, product backlog grooming, sprint backlog, and responsibilities of product owner, scrum master, and development team.

Identify the sponsor's attributes and their authority above the project manager. See how sponsors approve charters, secure resources, align with business goals, and monitor benefit realization after closure.

Discover the attributes and responsibilities of a project manager, blending knowledge of processes, leadership, and interpersonal skills with proactive risk and change management across predictive and agile contexts.

Explore the attributes and responsibilities of the product owner in agile projects, including backlog ownership and prioritization, sprint goals, acceptance criteria, stakeholder engagement, and budget and benefit realization.

Explore the attributes and responsibilities of team members in cross-functional agile teams, including self-organizing work, estimation, task assignment, and collaboration within diverse teams governed by ground rules.

Identify the root cause of the scrum master's concern about a product owner's dual project assignment, and reinforce that a product owner must be 100% dedicated to one project.

Explore needs assessment to craft the business case and benefit management plan in the pre-project stage, secure go decisions, and initiate the project for eventual benefit realization.

Learn how needs assessment, conducted by the business analyst and sponsor, identifies problems or opportunities via stakeholder interviews, document reviews, and process observations, developing a situation statement and business case.

Explain how the business case document guides management through economic feasibility, $1 million investment, $4 million profit in two years, strategic alignment, and options with ROI and risk assessment.

Learn how the benefit management plan catalogs tangible and intangible benefits with profiles, owners, beneficiaries, metrics, and timelines, and how benefits are realized after project closure.

Learn how the project charter formally authorizes a project, links to the business case and benefit management plan, and defines scope, milestones, budget, risks, and sponsor authority for resources.

Explore rolling wave planning, an iterative approach that aligns planning with evolving requirements in agile and, occasionally, predictive projects, using sprint planning and backlogs to guide progressive scope definition.

Identify how enterprise environmental factors and organizational process assets influence projects, distinguishing internal and external factors, and learn to exploit opportunities or mitigate threats.

Learn the PMI code of ethics and professional conduct, emphasizing responsibility, respect, fairness, and honesty. Use exam tips to spot ethics in procurement and vendor selection.

Explore servant leadership in project management, focusing on leading through service to foster psychological safety, coaching, collaboration, and a high performance team in agile and predictive contexts.

A scrum master uses servant leadership to rapidly borrow spare software licenses from another team for five weeks, addressing a bottleneck during the sprint.

Master scope management for the PMP exam, covering predictive and agile approaches, scope statement, WBS, product backlog and user stories, acceptance criteria, and change management.

Distinguish product scope from project scope, identify final deliverables and features, and define the scope baseline using the project scope statement, WBS, and WBS dictionary to guide validation and control.

Identify how requirements define the how of a deliverable, not the scope of what will be produced. Learn to quantify customer and stakeholder needs—dimensions, material, and corrosion resistance—for a bolt.

Identify the predictive scope and requirements documents, including the scope management plan, requirements management plan, and the scope baseline: project scope statement, WBS, and WBS dictionary; review requirements traceability matrix.

Plan scope management defines how to manage project scope and requirements. It yields two subsidiary plans: the scope management plan and the requirements management plan.

Learn how the requirements management plan guides collecting, analyzing, documenting, and maintaining project and product requirements, tracking coverage, approvals, and change management with a traceability matrix.

Define the project scope statement as the key output of the defined scope process, detailing deliverables, constraints, assumptions, and acceptance criteria for a smart building project.

Explore the four major elements of the work breakdown structure—work packages, WBS codes, controller codes, and planning packages—and how they support cost, duration, resource planning, and earned value-based control.

Explore how work packages, the smallest WBS units, enable bottom-up estimation of cost, time, and resources for project planning, using examples like foundation, electrical, plumbing, and finishes.

Learn how WBS codes provide unique identifiers for all work breakdown structure components, from the total project scope to work packages, using hierarchical numbering and optional prefixes for uniqueness.

Define and apply control accounts within a work breakdown structure to consolidate scope, budget, actual cost, and schedule, enabling high-level earned value performance reporting for management.

Demonstrates how a requirement traceability matrix links requirements to project objectives and deliverables. Explore bidirectional linkage and filtering to map requirements to work packages and business goals.

Solve a practice scope management question to identify inputs for the define scope process: project charter, requirements, risk register, and note that the work breakdown structure is not an input.

Explore a sample product backlog with items, types, priority, and story points, and learn Moscow prioritization and planning poker to estimate and groom agile backlogs.

Explore why we create user stories in agile and how detailing purpose, application, and benefits guides software teams—developers, testers, and user interface designers—to implement the right features.

Explore the standard agile syntax for user stories, focusing on who, the goal, and the benefit. Transform features into user stories and map tasks like designing, developing, testing.

Convert features, risks, bugs, and refactoring into user stories via a dedicated workshop. Align with release planning, sprint planning, and backlog grooming; engage stakeholders to define acceptance criteria and value.

Identify epics as big user stories that contain many sub stories; decompose them into features and then into user stories to fit into iterations and deliver incrementally in agile projects.

Resolve scope disputes by consulting the project scope statement, which defines scope inclusion and exclusion, guiding evidence-based decisions in PMP practice questions.

Quantify stakeholder needs to form requirements within a formal requirements document. Follow the requirements management plan, practice progressive elaboration, and apply integrated change control to baselined plans.

Explore the spectrum of requirements, from product functional and non-functional requirements to project, quality, business, stakeholder, and transition needs. Understand how these categories guide design, testing, and validation.

Use focus groups to capture attitudes, opinions, and feelings through qualitative analysis, with group discussions moderated to reveal consumer concerns and product expectations.

Learn how interviews elicit stakeholder needs through targeted questions, capturing qualitative insights and, in some cases, quantitative data via surveys.

Use questionnaires and surveys to quickly collect objective requirements from geographically dispersed stakeholders. Share links for responses and apply basic statistical analysis; interviews and focus groups supplement these methods.

Brainstorming uses collective wisdom in a facilitated group to generate ideas, record them, analyze and eliminate duplicates, then vote to select the top ideas via nominal group technique.

Apply observation to uncover hard-to-articulate stakeholder needs, capture authentic user behavior through job shadowing, and inform secure banking app design and process automation.

Learn prototyping to align client expectations through early feedback, using product mockups, simulations, and 3D models to iteratively refine requirements and minimize project risk.

Create wireframes or story frames (storyboards) as low fidelity prototypes to secure early client feedback, align user interface expectations, and test flow.

Facilitate workshops to identify and reconcile conflicting requirements early, helping stakeholders reach consensus on safety versus fuel economy and cost.

Explore three decision making techniques: voting, autocratic decision making, and multi-criteria decision analysis, showing how stakeholders reach consensus, leverage expertise, and use data for informed choices.

Learn three voting techniques—unanimity, majority, and plurality—and when to apply each for consensus-driven decisions, from two-option to multi-option scenarios.

Learn multi-criteria decision analysis by ranking three phone brands across six attributes using a 1-to-5 scale, summing scores, and choosing the highest-score option.

Affinity diagram is a data representation technique similar to mind mapping that groups brainstorming ideas under header cards to address concerns and opportunities, with agile sizing applications.

Apply multi-criteria decision analysis and data-driven decision making to select a commercial database based on reliability, operational cost, and scalability in scope management.

Explore product backlog prioritization techniques—mask analysis, kernel analysis, and 100 point method—to identify high-value items and deliver them in early iterations, aligning with agile value delivery.

Master the Moscow prioritisation technique to rank backlog items as must have, should have, could have, and would have, prioritizing product functionality with final decisions by the product owner.

Master the 100 point method for product backlog prioritization, where stakeholders allocate $100 to features to quantify importance. This approach aligns with multi-criteria decision analysis and agile project management.

Master control scope in predictive and agile projects by preventing scope creep and gold plating, aligning work with the scope baseline, WBS, and product backlog, with progressive elaboration.

Learn how the validate scope process in predictive projects ensures deliverables meet acceptance criteria through control quality and verification, culminating in formal sponsor or customer acceptance of accepted deliverables.

Learn how to validate scope in agile through sprint demos, obtain product owner acceptance, and use the definition of done checklist to deliver verified, accepted increments.

Define acceptance criteria in agile with the product owner using the definition of done, obtain formal acceptance during the product demo and sprint review, and track velocity with story points.

Identify tangible and intangible value in projects, illustrate measurable financial benefits like ROI and cost savings, and highlight nonfinancial gains such as goodwill, compliance, sustainability, and reputation.

Explore how value planning, project life cycle, and benefit realization drive investment decisions, with needs assessment, business case, and benefits management guiding deliverables that create lasting value.

Project managers translate value into delivery by understanding stakeholder benefits, validating value through scope, and sustaining stakeholder engagement with reviews, acceptance criteria, and feedback.

Agile with incremental delivery accelerates value delivery by delivering usable increments and gathering early stakeholder feedback, though some projects still require a predictive approach.

Explore why product backlog prioritization drives value delivery in Agile projects, prioritizing high-value backlog items for early, incremental benefits using MASCO, KANU, and the 100-point method.

Link validate scope to value delivery by demonstrating completed deliverables against acceptance criteria and the definition of done, ensuring stakeholder satisfaction and intended benefits.

Adopt a value-driven mindset focused on value planning and value delivery to answer PMP exam scenarios that prioritize the option delivering the greatest value for stakeholders over convenience.

Close the scope module and transition to scheduling by planning the time, cost, and resources needed, determining the work order and deliverables.

Explore core schedule management concepts, from the schedule management plan and predictive scheduling to agile scheduling, sequencing activities, estimating durations, and mastering the critical path and schedule baseline.

Explore schedule management in predictive projects, covering planning the schedule management plan, defining activities, sequencing with dependencies, estimating durations, building the schedule network diagram, and establishing the schedule baseline.

Plan, develop, and control the project schedule with the schedule management plan, leveraging inputs such as project charter and scope management plan, and tools like WBS, estimation, EVM, and reporting.

Explain how the define activities process decomposes the work breakdown structure into verbs-based activities, creating an activity list and activity attributes to enable sequencing, estimation, and the project schedule.

Sequence and estimate project activities to build a schedule network diagram using dependency determination, the precedence diagramming method, and leads and lags.

Explore dependency determination technique as the first step in schedule network diagrams, contrasting mandatory vs discretionary dependencies and internal vs external dependencies.

Demonstrate the precedence diagramming method with an MS Project sheet, showing finish to start, start to start, finish to finish, and start to finish relationships between predecessors and successors.

Learn how leads enable schedule compression by advancing the start of a successor relative to the predecessor, creating overlap in finish-to-start tasks without extra resources.

Shows how leads and lags in MS Project adjust task starts, using finish-to-start and start-to-start relationships; negative lag yields a lead and positive lag causes a delay, enabling schedule compression.

Explore how to determine dependencies in a schedule network diagram using the dependency determination technique and precedence diagramming method, noting an external mandatory dependency between approvals and foundation work.

Explore how analogous estimation leverages similar past projects and historical data to generate rough, quick cost and time estimates, enabling top-down budgeting while noting its limited accuracy.

Learn how parametric estimation uses a formula with historical data to estimate cost and duration per unit of work, such as painting 5,000 ft², and understand its advantages and limitations.

Apply three point estimation using optimistic, pessimistic, and most likely values to forecast work duration; compare simple average and weighted beta (pert) methods, with a commuting time example.

Explore four estimation techniques—analogous, parametric, three-point, and bottom-up—and learn how time versus accuracy governs choice, with planning poker and absolute estimation techniques alongside relative sizing.

Identify the critical path—the longest schedule path that sets project duration. Learn to compute path lengths and float (slack) to measure schedule flexibility.

Practice exercise demonstrates identifying the five paths in a project schedule, finding the critical path, and calculating float by comparing path durations to the project duration.

Compute float as project duration minus path length, identify the critical path, and apply schedule compression and resource leveling while monitoring near-critical and non-critical paths to prevent delays.

Explore the difference between total float and free float in project schedules for PMP exam prep, comparing path lengths to the critical path and delays in parallel tasks.

Explore resource leveling and resource smoothing to balance demand and supply by adjusting task start dates under resource constraints, preventing overload, and maintain critical path for a feasible project schedule.

Apply resource smoothing to use floats on non-critical paths by reducing headcount without delaying the project end date, ensuring resource limits aren't exceeded and the critical path remains intact.

Crashing speeds up tasks by adding resources to compress the schedule; fast tracking is preferred first, but crashing incurs higher costs, overtime, and a change request on the critical path.

Explore exam tips on schedule compression techniques, including fast tracking, crashing, and resource optimization, and use the included PDF sheet to reinforce skill compression for the PMP exam.

Explore the Gantt chart format for presenting project schedules, showing tasks, durations, start and end dates, predecessors and successors, dependencies, and the critical path.

Use milestone charts to present project schedules to top management with a bird's-eye view. Represent milestones with a diamond on a Gantt chart and keep details abstract to avoid overload.

Baseline the schedule by listing activities, estimating, sequencing, and mapping network, identify the critical path and floats, and review with sponsors to baseline scope and cost through formal change control.

Learn planning poker as a relative estimation technique in agile projects, sizing user stories with Fibonacci-based story points to estimate backlog velocity and reach team consensus.

Learn velocity in agile project management, using story points and sprint demos to measure completed work. Discover how accepted stories determine velocity and how velocity guides agile planning.

Learn how to create an agile release plan using iterative scheduling and velocity, calculating total work from story points, and forecasting iterations and project duration.

Learn how velocity, a team-based, lagging metric, guides planning and replanning; avoid cross-team comparisons, focus on accepted story points, and track team progress through forming, storming, norming, and performing stages.

Apply on-demand scheduling by sizing backlog items evenly, estimate cycle time from the bottleneck, and determine throughput and lead time with Kanban pull and WIP limits.

Learn how to apply the control schedule process in predictive projects by baselining the plan, tracking actuals with a Gantt chart, and managing variance to keep work on track.

Learn to create burn up and burn down charts in excel to track release and iteration progress, using backlog, velocity, and story points.

Explore the finance management module for the PMP exam, covering cost management plans, cost estimation, budgets and reserves, burn rate, earned value management, and ROI, NPV, IRR.

Define plan cost management and create a cost management plan as the guide for estimating, budgeting, and controlling project costs, using project charter, schedule management plan, and risk management plan.

Explore the cost management plan, including its purpose, components, estimation methods, accuracy and baseline concepts, change control with the CCP, performance metrics, and Primavera integration to manage project costs.

Estimate costs by sizing each WBS work package and building the budget using inputs from scope baseline, risk register, quality plans, and estimation techniques like analogous, parametric, three-point, and bottom-up.

Understand known unknowns and unknown unknowns in project risk management and budgeting. Learn how contingency reserves fund risk responses and management reserves cover unplanned in scope work.

Identify and quantify project risks using probability impact analysis to determine the contingency reserve via expected monetary value, and learn how to apply and justify reserves within the cost baseline.

Explore how management reserve covers unplanned in-scope work, how contingency reserve uses expected monetary value to build the cost baseline, and how project budget equals cost baseline plus management reserve.

Learn how change management affects the cost baseline and management reserve, including moving funds from reserve to baseline and updating the contingency reserve for risks and rework.

Monitor risk processes to identify new risks and update risk register; move funds from the management reserve to the contingency reserve via a change request that affects cost baseline.

Learn how earned value management (EVM) integrates scope, schedule, and cost to assess project performance and progress.

Learn how to form the performance measurement baseline from scope, schedule, and cost baselines, then use work performance data to monitor and evaluate variances with EVM metrics.

Establish the performance measurement baseline by aligning scope, cost, and schedule baselines, and analyze planned value, earned value, and actual cost for EVM.

Calculate PV, EV, and AC to perform weekly EVM analyses and prepare the EVM report. Assess schedule and cost performance using earned value, planned value, and actual costs.

Examine a sample earned value management (evm) chart to compare earned value, planned value, and actual cost for calendar week 15, linking ev, pv, and ac to scope and budget.

Compute sv, spi, cv, and cpi from pv, ev, and ac using two of three values. Interpret negative values and values below one to judge schedule and cost performance.

practice inferring sv, spi, cv, and cpi values from three projects to judge schedule and cost performance, identifying ahead of schedule, on track, or behind and on budget or overspent.

Forecast project outcomes using eac, vac, and etc in earned value management. Analyze ac, pv, ev and cpi, spi to guide budget decisions.

Solve a cost management practice question using earned value metrics to determine the estimate to complete, given BAC, AC, and zero variance at completion, yielding ETC of 5 million.

Learn how to plan, acquire, manage, and release project resources—humans and non-human items—through resource management and procurement processes, including RACI, resource breakdown structure, make-or-buy, and contract types.

Define how to estimate, acquire, manage, and utilize organizational resources to produce the resource management plan, guiding project work with inputs like project charter and scope baseline.

Learn how the resource management plan guides identifying, acquiring, and managing internal and non-human resources, detailing roles and responsibilities, organization charts, training, and rewards to support project success.

Apply the RACI chart (RAM), a responsibility assignment matrix, to map tasks to roles (R, A, C, I) and clarify ownership, with exam tips and WBS prerequisites.

apply four estimation techniques to determine resource requirements for activities. document basis of estimates and resource breakdown structure, considering people, non-human resources, duration, and cost.

Identify resource requirements for each work package using bottom-up estimation, supported by the resource breakdown structure. Document the basis of estimates, including assumptions, methods, ranges, tolerance, and confidence levels.

Explore a practice question in resource management for the PMP exam, demonstrating why updating the resource calendar first, when a critical resource's availability changes, is essential for schedule impact.

Coordinate with functional managers to acquire internal and external resources, align with the project schedule and cost baseline, and assign physical resources and project team via negotiation and multi-criteria analysis.

Ensure physical resources are available and utilized per plan. Use work performance data to identify variances, initiate corrective actions, and apply change requests as needed.

Learn to apply make or buy decision making to decide whether to do work in-house or outsource, using make or buy analysis, WBS insights, and procurement management processes.

Understand the procurement process flow from defining the statement of work to awarding a contract, including cost estimates, bid documents, and vendor selection for PMP exam prep.

The procurement management plan guides outside sourcing, integrates with other management plans, and defines contract types, bid processes, and the statement of work and provider management.

Explore procurement documents, including the statement of work, RFQ, RFP, RFI, and invitation for bid, and how they guide vendor selection in plan procurement management.

Analyze cost reimbursable contracts, compare cost to price, and outline reimbursement of expenses plus profit, including three types: cost plus fixed fee, cost plus incentive fee, cost plus award fee.

Explore the cost plus incentive fee (CPIF) contract, a cost reimbursable approach that uses penalties and incentives to control vendor performance and share cost savings.

Explore cost plus award fee contracts where the award depends on subjective criteria like happiness and satisfaction, contrasting with objective cost plus incentive fee metrics and related exam tips.

Outline fixed price contracts overview and compare with cost reimbursable contracts, showing lump-sum payments, scope-defined work, and three types: firm fixed price, fixed price with incentive, and economic price adjustment.

Firm fixed price contracts set a statement of work and an agreed price, transferring risk to the vendor as the price does not change with scope, unlike cost reimbursable.

Understand fixed price with economic price adjustment contracts in construction projects, including inflation, currency exchange, and material cost impacts, and learn exam tips for applying this contract type.

Learn how time and materials contracts work, including when to use them for staff augmentation and equipment rentals, and examine exam tips on cost risk and undefined scope.

Emphasize value delivered contract types enable flexible outsourcing in agile projects by paying suppliers per feature based on product backlog value and weights, prioritizing high-value features.

Explore agile contracts money for nothing and change for free, tracking value with dollar-weighted features in the backlog and deciding to cancel or substitute work based on delivered value.

Learn how fixed-price increments price each feature by size (story points) in agile projects, balancing size with value, enabling item-level re-estimation and scope changes without reworking the whole contract.

Explore graduated time and material contracts, adjusting hourly rates by performance: on-time ($85), early completion ($100), and late completion ($70), using metrics and a definition of done.

Work with qualified or approved vendors to rely on background checks, proven performance, and streamlined contract and payment processes, using the vendor list and lessons learned to guide awards.

Evaluate a cost-plus-incentive-fee contract with schedule-based incentives to determine payment of $65,000 for legitimate costs and fee when work finishes on the due date.

Explore resource management and procurement management concepts, including internal and external resources, contract types, vendor selection, resource acquisition, estimating activity resources, RACI, and the resource breakdown structure, plus agile options.

Learn core quality management for projects, including quality planning, testing, verification, cost of quality, and continuous improvement within the PMP exam framework.

Explore the quality management plan as a core component of the project management plan, detailing quality standards, objectives, roles, processes, reviews, tools, and continuous improvement through plan-do-check-act.

Explore the differences between standards and regulations, including voluntary standards and mandatory laws, and capture them in the quality management plan to ensure compliance and avoid penalties.

Discover how objective quality metrics from plan quality management quantify project quality with examples like leak defects, first time right, defect density, scrap rate, and customer satisfaction.

Discover how cost of quality splits into prevention and appraisal (conformance) versus internal and external failure costs, and learn how proper training, tooling, and testing prevent costly defects.

Explore how quality audits verify process alignment with organizational policies, and how data analysis and quality process design uncover improvement opportunities to optimize quality management and reduce costs of quality.

Use the cause-and-effect (fishbone) diagram to identify and verify root causes of a problem by brainstorming potential causes, then filtering with evidence to find the actual causes.

Adopt a continuous improvement mindset through PDCA, Kaizen, TQM, and agile retrospectives, and leverage lessons learned repositories to drive incremental and breakthrough improvements in people, processes, and products.

Conduct retrospectives at sprint end to identify what went well and what went wrong, pursuing continuous improvement through root cause analysis and prioritized corrective actions in the next sprint.

Solve a quality management practice question on regulatory requirements, government-mandated safety standards for a new discrete electronic component, and distinguish them from standards and non-functional requirements.

Explore sustainability in project management for the PMP exam by examining environmental, social, and economic impacts, the sustainability pyramid levels—avoid, minimize, restore, compensate—and how value benefits stakeholders and future generations.

Discover how sustainability creates value for organizations, stakeholders, customers, and society by improving relationships, risk management, and efficiency. Deliver operational and financial benefits through reduced waste and energy use.

Explore how sustainability intersects every project performance domain, including finance, risk, scope, resource, and stakeholders, and shapes budgeting, planning, and decisions for long-term value in PMP exams.

Explore the governance performance domain, including initiating projects with a charter and integrating plan components into the project management plan. Learn about issue management, change management, and project closing.

Navigate an integration module scenario in the execution phase of a product development approach, where mandatory military-standard training affects schedule and cost, triggering a sponsor change request through change management.

Manage the issue log—tracking descriptions, ids, impact, category, owners, priorities, and status—and apply agile impediment log practices like timely updates and workarounds such as fast tracking and crashing.

Explore how risk, issue, and change management interrelate; identify when to apply risk responses, issue logs, and change requests to protect baselines.

Learn key problem vocabulary in agile project management by distinguishing impediments, obstacles, and blockers, with practical examples and the issue management process.

Master agile vision and issue management by using plan, inspect and adapt across sprint ceremonies, recording impediments in the log and guiding scrum master support for unobstructed progress.

Differentiate risks as future possibilities from issues as present problems. Manage risks proactively with risk registers and contingency reserves; address issues with issue logs and change management.

Compare predictive and agile change management through the integrated change control procedure. Learn roles like change initiator, change control board, and product owner, plus backlog refinement and progressive elaboration.

Learn how change requests modify baselines, project documents and deliverables through the configuration management plan and change management process, with guidance on rebaselining, regulatory updates, and corrective or preventive actions.

Review and approve change requests through a chartered change control board (CCB) with the PM, sponsor, client, subject matter expert, and procurement manager, using change management software to track lifecycle.

Apply a six-step change management process: qualify, analyze impact, identify options, obtain ccp review, update the project plan and baselines, and implement the change.

Learn the four change request types—corrective action, preventive action, defect repairs, and document or baseline updates—plus when to initiate them, and the governing change management procedures and roles.

Identify and differentiate administrative changes, contract modifications, and supplemental agreements, and understand termination triggers and change control processes in contract management.

Learn to manage contract-related disputes, including warranty issues, waivers, breaches, and cease-and-desist matters, through negotiation, ADR, and, if needed, litigation.

Solve a practice integration question and learn the change management sequence: assess the change, prepare impact statements, identify options, and update project documents and baselines after CCP approval.

Close project or phase ensures final product handover, provides training and user manuals, and documents a final report with lessons learned, archived for future projects.

Explains the two types of project closure—successful closure and premature termination—and how acceptance, the scope baseline, and the requirements traceability matrix, plus the definition of done, guide closure.

Close a project by completing plan-based closing activities, obtaining formal acceptance, resolving issues and claims, closing contracts, charging costs, releasing resources, archiving data, and delivering the final report.

Guide end users through transition and handover by providing training, documentation, and post-implementation support to ensure smooth adoption and realize project benefits.

See how AI supports project management by generating documentation, summarizing notes, identifying risks, and analyzing data. Aids planning and stakeholder communication while automating tasks to boost productivity.

Explore three AI adoption levels in project management: automation, assistance, and augmentation, showing when to automate, review, or use AI for decision support, with PMI guidance for exam readiness.

Explore how artificial intelligence augments governance, risk, stakeholder, and schedule domains in project management, enabling data-driven decisions, predictive analytics, and personalized stakeholder communication.

Complete the integration module and prepare for exam questions on integration management, spanning all five process groups, plus issue and change management. Prepare for upcoming risk management content.

Explains the seven risk management processes, from planning the risk plan and identifying risks to performing quantitative risk analysis, planning and implementing responses, and monitoring and auditing contingency reserves.

Explore risk as an uncertain event that affects project objectives like scope, schedule, cost, and quality, with threats negative and opportunities positive, and plan to avoid, mitigate, exploit, or enhance.

Understand risk attitude and risk appetite in project management. Compare risk averse, risk neutral, and risk seeking mindsets with examples from fixed deposits, mutual funds, and stocks.

Learn how to structure and implement a risk management plan within the project management plan, covering risk identification, assessment, response strategies, contingency reserve, and risk reporting.

Identify risks process starts project risk management by using expert judgment and brainstorming to populate the risk register with risk details, triggers, and owners.

Learn how to perform qualitative risk analysis by evaluating identified project risks with probability and impact scores, using the probability‑impact matrix to prioritize and categorize risks in the risk register.

The risk register records outputs of risk management, serving as the central planning document with risk IDs, likelihood, impact, priority, trigger conditions, score, and risk response plan.

Quantitative risk analysis numerically examines the combined effect of identified individual project risks on achieving the 12-month objective, guiding whether to perform Monte Carlo and decision tree analysis.

Monte Carlo analysis uses statistical modeling and simulations to assess project risk and uncertainty. Feed three-point estimates into software to produce a probability distribution function for time and cost.

Apply Monte Carlo analysis to infer a probability distribution for project cost. Compare optimistic, most likely, and pessimistic estimates to establish a realistic budget.

Apply decision tree analysis to compare launching a new product versus upgrading an existing one, using expected monetary value, probabilities, and revenues to select the optimal choice.

Identify risks, plan risk responses, and implement actions to address threats and opportunities. Update the risk register with responses, assign risk owners, and allocate schedule and cost reserves.

Plan risk responses for individual risks and overall exposure, assign risk owners, and update schedules and budgets using the risk management plan and risk register.

Learn risk response strategies for threats and opportunities, including escalate, accept, avoid, mitigate, exploit, enhance, transfer, and share, with exam-style drag-and-drop practice.

Execute risk responses per the risk management plan, update the risk register and risk report, adjust baselines, and track progress with PMIS tools using expert judgment.

Learn how agile risk management uses a risk adjusted product backlog to prioritize features and risk responses by dollar value, balancing revenue and loss avoidance.

Continuously monitor risk, identify new risks during execution, reevaluate probability and impact, update the risk register, audit risk management, and adjust responses to prevent issues.

Apply monitor risks by using the risk management plan, risk responses, and risk reports to assess risk exposure, review work performance data, and update the risk register and related plans.

Close the risk management module with a thorough review of concepts that prevent project risk and avoid failures, and prepare for exam questions on risk management.

Develop and manage project communications and stakeholder engagement to align needs and expectations, using the stakeholder engagement plan, stakeholder register, and engagement assessment matrix for co-located and distributed teams.

Identify project stakeholders as individuals or groups who influence, are impacted by, or have an interest in the project, and map their needs for effective engagement and communication management.

Identify and continuously update project stakeholders, assess their interests and influence, and tailor communication plans to engage them through meetings, workshops, surveys, and reports.

Identify stakeholders and populate the stakeholder register from key documents, capturing needs and influence; use the stakeholder engagement and communication plans and mapping tools to manage expectations.

Learn to map and group stakeholders by influence, crafting targeted engagement strategies for four to five categories to optimize communication, resources, and project success.

Power-interest grid helps categorize stakeholders by power and interest to tailor engagement strategies. It uses a two-dimensional matrix to assign stakeholders to four quadrants and guide targeted communication and involvement.

Discover the salience model, a stakeholder grouping technique using a Venn diagram of power, legitimacy, and urgency to classify stakeholders into seven categories.

Explore direction of influence to categorize stakeholders into upward, downward, outward, and sideward by reporting structure and authority, and compare this technique with salience model, power‑interest grid, and stakeholder cube.

Identify how failing to categorize stakeholders by relative importance undermines the stakeholder engagement plan. Prioritize communications by stakeholder importance and conduct a retrospective to uncover root causes.

Use the stakeholder engagement assessment matrix to map stakeholder attitudes, plan targeted engagement strategies, and monitor shifts from resistance to support for project success.

Learn how to balance communication planning and stakeholder engagement through surveys and feedback, building trust and rapport while ensuring timely, accurate information flow.

Learn to create a stakeholder engagement plan that guides engagement with stakeholders. Apply salience, power–interest analysis, and engagement metrics, and align with the risk and communication plans during execution.

Create and update a stakeholder engagement plan that guides stakeholder identification, prioritization, engagement strategies, and communications to maintain support and align with the project management plan.

Discover how the communication management plan guides project communications, detailing who, what, when, and how information is shared with stakeholders using emails, reports, and meetings.

Identify stakeholder information needs through communication requirements analysis, gathering preferences on what, when, how, and frequency, then develop and document an aligned communication management plan.

Select and apply the right communication methods and technologies to enhance stakeholder engagement and information flow, using face-to-face, video conferencing, email, reports, social media, chats, and dashboards.

Explore push, pull, and interactive communication methods, with examples like emails, memos, meetings, and instant messaging, and learn how each method initiates messages and feedback.

Develop a robust communication management plan by assessing challenges and selecting methods, tools, and technology. Ensure timely, secure, and accessible stakeholder communication, considering confidentiality, policies, and accessibility.

Learn how the cross-cultural communication model uses sender, encoding, medium, and receiver, with acknowledgement and feedback, while emotions, biases, and noise shape message understanding in multicultural teams.

Execute the planned stakeholder engagement strategies to support stakeholders and manage expectations. Use the stakeholder engagement plan, communication management plan, and stakeholder register to handle change requests and risk updates.

Execute the manage communications process by implementing the communications management plan with inputs from the stakeholder engagement plan and stakeholder register, circulating project communications and reports to stakeholders on schedule.

Monitor the communication management process to convert work performance data into work performance information, ensuring stakeholders receive timely, appropriately detailed EVM reports, and update plans through change requests when needed.

Update the project schedule after updating the communication management plan to assign a weekly quality status report and share it with stakeholders.

Learn how a team charter defines mission, objectives, shared values, ground rules, and communication guidelines to help a project team operate as a well-organized unit.

Explore how the team charter governs team-level communication, detailing frequency, methods, and ground rules, and how retrospectives drive continuous improvement.

Contrast co-located and virtual teams to show how face-to-face interaction and a shared workspace boost communication and bonding, while virtual teams enable global talent and cost savings with tech reliance.

Investigate virtual team communication challenges—time zones, reliance on technology, and cultural differences—and apply best practices like video calls, clear guidelines, shared calendars, and tools such as Jira and Slack.

Promote osmotic communication by seating co-located teams within ten meters, enabling overheard conversations in a shared commons while offering caves for private focused work.