PMP® Illustrated

Section overview introduces project management processes across scope, schedule, cost, quality, resources, risk, procurement, stakeholders, and integration, highlighting planning as the integrating activity for execution, monitoring, and closing.

Execute projects with urgency to deliver business value while maintaining precision and quality, using incremental, often-delivered agile milestones that let customers start using value early.

Explore how incremental delivery in agile projects creates value throughout the work, delivers early feedback and ROI, using sprints, iterations, time boxes, and a product roadmap.

Discover how to value a project through financial gains, market share, environmental and social benefits, and growth, using roadmaps and progressive elaboration to time releases and boost return on investment.

Find the minimum viable product and minimum marketable feature to deliver a small, valuable increment, using value stream mapping, burn down and cumulative flow diagrams, and retrospectives.

Improve project outcomes by mastering bidirectional communication with stakeholders, using performance reports, feedback, demos, and calendars to plan, monitor, and align issues, risks, and vision.

Analyze stakeholders' communication needs by building a stakeholder register or 'who's who' document to capture contact info, interests, and influence, and define communication methods.

Develop a communications management plan to define who needs what information, when, and in which channel. Include escalation, glossaries, and a clear communication model to prevent miscommunication and stay compliant.

Communicate project information frequently using push methods like emails and reports, and pull methods via information radiators and dashboards, and demonstrate completed work in sprint reviews for transparency and value.

Confirm understanding and ensure feedback is received through verbal or nonverbal cues; use stakeholder register and communications plan to update project communications in a predictive environment.

Assess and manage risk using qualitative and quantitative analysis to estimate probability and impact. Document risks in a risk register, classify them, and plan responses to threats and opportunities.

Explore risk management options in traditional and agile contexts. Use proof of concept spikes and a customer demo to test high probability, high impact risks and keep projects on track.

Iteratively assess and prioritize risks throughout the project and in each agile iteration, using a risk-adjusted backlog, risk register, and ongoing risk responses.

Identify stakeholders early, assess their requirements and influence, plan and execute engagement and communication, and monitor ongoing stakeholder engagement to maintain alignment with expectations.

Analyze stakeholders by mapping power, influence, and interest on a power–interest grid and using a salience model to prioritize engagement, information, and support.

Categorize stakeholders with a robust stakeholder register, detailing contact information, roles, requirements, expectations, influence, and attitude to guide communications management, and map affinity groups and personas of ideal users.

Identify and plot stakeholder engagement with a stakeholder engagement assessment matrix, mapping current to desired levels—from unaware to leading—across categories, including sponsors and champions.

Develop, execute, and validate a strategy for stakeholder engagement by aligning goals, maintaining transparent communication, and involving stakeholders in forecasting, demos, and risk planning to deliver business value.

Plan and manage budget resources by estimating costs and creating a project budget that covers money, people, and physical resources. Monitor budget and resource needs, including contingency reserves.

Estimate budgetary needs by planning for materials, labor, and equipment, including indirect costs and contingencies. Apply analogous, parametric, and bottom-up methods with WBS to converge on cost estimates; assess risk.

Anticipate budget challenges by understanding budget components, including activity estimates, cost baseline, and management reserve, while monitoring time, cost, and change requests to avoid gold plating and step funding.

Monitor budget variations by building a cost baseline, tracking weekly cumulative costs against the baseline, and using an S-curve to compare actuals to plan for root-cause analysis.

Plan and manage resources by agreeing the definition of done, the project scope, and a detailed WBS dictionary; establish quality criteria and use prototypes to align expectations and manage change.

Plan and manage the project schedule with traditional upfront estimation and agile iteration planning, guided by a schedule management plan, product backlog, and release plan.

Estimate project tasks using milestones, dependencies, and story points in both predictive and agile methods, guided by the scope management plan, assumptions, constraints, enterprise environmental factors, and organizational process assets.

Leverage benchmarks and historical data to measure key performance indicators and predict project duration and cost, using user story points and velocity across iterations to forecast remaining work.

Learn to prepare schedules with Gantt charts and network diagrams, identify milestones and the critical path, and manage dependencies, float, and agile releases across iterations.

Assess and prioritize impact on project scope and backlog using earned value management and agile tools like burn down charts and cumulative flow diagrams to track remaining, in-progress, and completed.

Modify schedules using rolling wave planning and agile change, prioritizing the product backlog through sprint reviews, the change control board, short planning cycles, and near-term detail with iterative retrospectives.

Coordinate with other projects, operations, and releases to ensure transparent forecasting. Update program and portfolio managers with forecasts, estimates, and backlog management for effective planning.

Learn to plan, manage, and control quality for project deliverables by identifying requirements and standards, ensuring conformance and that outputs are fit to use, and monitoring results.

Determine quality requirements for product deliverables by aligning with standards, regulations, and industry practices. Use a quality management plan to balance prevention, appraisal, and failure costs, and enforce corrective actions.

Identify quality gaps and propose improvement options using quality metrics, control charts, audits, RCA, and Ishikawa diagrams to drive testing, validation, and continuous improvement (pdca, kaizen, six sigma).

Survey and measure deliverable quality with quality metrics and cost of quality throughout agile cycles—from product backlog to increment—via sprint reviews and retrospectives, guided by plan-do-check-act.

Plan and manage scope by aligning with customer expectations, defining the project’s entire breadth, and identifying what to create or purchase to deliver what the customer anticipates.

Learn to determine and prioritize requirements, collect them with diverse elicitation techniques, and track them with a requirements traceability matrix in agile and predictive contexts.

Decompose project scope into a work breakdown structure with work packages, estimates, and acceptance criteria for a plan-driven approach, while agile favors a prioritized product backlog and user stories.

Monitor and validate scope through acceptance criteria and definition of ready and done, using given when then scenarios. At iteration end, demos and retrospectives flush out misunderstandings and align deliverables.

Consolidate planning into the project management plan by integrating scope, schedule, cost, quality, resources, risks, and stakeholders, and establish the scope, schedule, and cost baselines with the performance measurement baseline.

Assess consolidated project plans using a project management information system, like Primavera, Jira, or base camp, to identify capacity limits, dependency violations, and late downstream activities.

Analyze collected data by examining the configuration management plan, tracking project artifacts like blueprints, and monitoring scope changes; update configuration items and engage the Change Control Board as needed.

Collect and analyze data to inform decisions by evaluating how changes affect cost, completion, risk, and value through the change control board, change manager plan, and change control process.

Determine critical information requirements to ensure compliance with government rules and quality standards, and monitor deliverables using the ppm plan, baselines, product backlog, and change and configuration management plans.

Identify how change is inevitable in projects, contrast predictive planning with adaptive approaches, and embrace agile, change-driven strategies to manage scope, time, and cost.

Anticipate and embrace change as a core project reality, recognizing triggers such as missing requirements, specification changes, new regulations, customer changes, incorrect estimates, and market competition, and plan adjustments accordingly.

Compare predictive, agile, and hybrid change strategies in project management. Learn to control changes, protect baselines, manage the backlog, and educate stakeholders for smooth scope evolution.

Execute the change management strategy according to the methodology. Apply predictive and agile approaches with approval levels, change control boards, and tracking tools.

Identify the change and assess its impact on scope, schedule, budget, and risk. Implement integrated change control, update plans and baselines, inform stakeholders, and prioritize changes using must, should, could.

Learn to plan and manage procurement, understand contract types, oversee suppliers, and recognize the project manager as a key stakeholder to protect the project from procurement issues.

Define resource requirements and needs, perform a make-or-buy analysis, and implement a procurement management plan to govern bids, contracts, and vendor management for timely, cost, and quality outcomes.

Communicate resource requirements clearly, including lead times for contracts and purchase orders, define objectives and done criteria, and assess vendors via life-cycle costing to avoid miscommunication.

Manage suppliers and contracts by coordinating delivery and site access, and explain contract types—fixed price, cost reimbursable, and time and materials—with statements of work and RFQ, RFP, and RFI.

Plan and manage the procurement strategy by controlling the procurement process, maintaining buyer-seller relationships, closing contracts, paying vendors under agreed terms, with agile incremental delivery contracts.

Develop a delivery solution by implementing a contract change control system that collects, tracks, adjudicates changes, handles disputes, and defines approval levels for procurements and closeout.

Manage project artifacts through document management and versioning for all plans and deliverables. Living documents evolve with changes, requiring audit trails, configuration management, and version control.

Determine requirements for managing artifacts aligned with organizational needs, applying version control and change management to agile items like backlog, product increment, roadmap, vision statement, sprint backlog, and release plan.

Validate that project information is up to date and accessible by applying configuration management, storing artifacts in a repository, and recording changes and versioning to designs, plans, and blueprints.

Assess the effectiveness of managing project artifacts by implementing storage and distribution systems that match project complexity, using cloud-based or commercial version control with check-in/check-out, access controls, and email notifications.

Determine the appropriate project methodology by comparing predictive, iterative, incremental, and hybrid approaches, including waterfall plan-driven and agile methods, guided by uncertainty, complexity, stakeholder needs, and timelines.

Assess project needs, complexity, and magnitude to choose the right approach across industrial, knowledge, and agricultural work contexts, and to manage uncertainty with agile principles.

Apply a spider chart agile suitability filter to decide project execution strategy by mapping team size, experience, customer access, culture, trust, and change likelihood to agile, hybrid, or plan-driven approaches.

Assess the type of work and select the best project methodology—predictive, agile, or hybrid—to maximize business value. Use examples like building a house or software to illustrate the decision process.

Leverage iterative incremental practices and agile cadence across the project lifecycle, from planning and daily standups to sprint reviews, retrospectives, and continuous recognition.

Define a project governance structure to guide decision making with go/no-go criteria (time or cost), outline escalation paths, and set expectations for project team and manager aligned with ground rules.

Determine appropriate project governance with issue resolution, escalation, and communication processes; align with organizational strategy, define acceptance criteria, roles and responsibilities, decision making, and change processes, emphasizing transparency.

Defines escalation paths and thresholds via base gates and phase gates, with phase-end reviews ensuring quality. Applies governance across the lifecycle, including risk assessment and stakeholder escalation when issues arise.

Identify how a risk becomes an issue when it actually occurs, with threats as negative risks requiring immediate action, and distinguish those from opportunities.

Identify when a risk becomes an issue, categorize it under quality, schedule, communications, or cost, and log it in the issue log with owner, priority, target date, and final outcome.

Identify the issue, log its data and owner, and assign a resolution date; collaborate with the team to devise a solution, then escalate if unresolved.

Collaborate with stakeholders to resolve issues by monitoring progress, proposing and implementing responses, and evaluating impact and effectiveness, while using the impediments board, daily stand-ups, and retrospectives for continuous improvement.

Explain how to ensure knowledge transfer for project continuity by sharing explicit and tacit knowledge openly, enabling operational transfer and ongoing support after the project.

Clarify project responsibilities within the team and map knowledge transfer steps—identify, capture, share, apply, assess—across individual, project, and organizational levels.

Outline working environment expectations through end-of-phase lessons learned retrospectives, document findings in a central lessons learned register, and share knowledge via face-to-face, video conferencing, wikis, and intranet tools.

Confirm the approach for knowledge transfers in remote teams by prioritizing written documentation, public sharing, and open editing, and back it with retrospectives and lessons learned repositories.

Plan and manage project phase closures or transitions by ensuring the work breakdown structure, activities list, and work packages fully satisfy the charter and original scope.

Determine criteria to successfully close the project or phase and finish closure activities, including phase reviews, phase gate estimates for the next phase (time and money), and archiving data.

Validate readiness for transition by confirming acceptance criteria and the definition of done, ensuring unit tests pass, code review complete, and the customer rep or sponsor signs off.

Conclude activities by confirming deliverables, updating documents, resolving issues, closing contracts and procurements, ensuring payments align with terms, closing project accounts, archiving information for the central lessons repository.

Master core project management processes—from scope and schedule to cost, quality, resources, procurement, and communications—through Project Integration Management, linking stakeholder engagement and change management across the project.

Examine how the business environment shapes project operations, covering framework, structure, procurement, requirements gathering, and interactions with departments and PMOs, with emphasis on government agency compliance.

Plan and manage project compliance by identifying regulatory laws, organizational requirements, safety, ethics, and social responsibility. Prepare for exam questions on being in compliance and following laws and regulations.

Confirm project compliance requirements by understanding what counts as compliance and treating it as must-have constraints, and integrate compliance into the backlog and WBS for traceability and risk management.

Classify compliance categories by what they control. Identify universal categories such as workplace health and safety, quality, environmental risk process, risk and security and privacy, anti-corruption, and social responsibility.

Identify potential threats to compliance by assessing product defects, testing errors, and regulatory changes, address unknown unknowns and awareness gaps, and use risk tools to plan avoidance or mitigation.

Apply methods to support compliance by using execution and work performance reports, risk reports, and agile information radiators, with frequent phase gates and sprint reviews to reduce rework.

Analyze the consequences of noncompliance by tracking and managing risk and the risk register within agile and hybrid frameworks, aligning governance, ready/done definitions, and continuous improvement.

determine the approach and actions to address compliance needs through the quality management plan; educate stakeholders, identify non-compliance, establish tolerances, and apply corrective actions, with awareness of cost of change.

Assess project compliance by applying plan-based tolerances, QA tools, audits, and performance reports to confirm compliance or identify shortcomings, then update the plan and repeat the cycle.

Evaluate and deliver project benefits and value while managing pure risk through avoidance or mitigation, and apply the triple bottom line of people, profit, and planet.

Analyze how to identify and quantify business value, compare benefits versus costs, and prioritize agile product backlog to maximize project value from the start.

Document ownership for ongoing benefit realization by aligning portfolio decisions with strategy and measuring value through the benefits management plan.

Verify a measurement system to track benefits, including roi, present value, future value, net present value (npv), and internal rate of return (irr), and highlight agile delivery of incremental value.

evaluate delivery options to demonstrate value through frequent agile demos and sprints, and use Net Promoter Score to gauge loyalty while testing A and B variants.

Assess outcomes by calculating expected monetary value as monetary value times probability, then compare decision paths using a decision tree and Monte Carlo simulations to inform return on investment decisions.

Evaluate external business environment changes that affect project scope within a 3-year window. Use Mordor and Pestle as quick brainstorming tools to gather requirements, without replacing subject matter experts.

Assess and prioritize impacts on project scope or backlog via the change control board or product owner, then update baselines and the configuration management system as changes are approved.

Recommend options for scope or backlog changes through integrated change control, assess impacts on scope, time, cost, quality, and risk, and update the backlog with the product owner.

Continually monitor changes with the governance board, sponsor, and PMO to clarify charter and guide resources; empower the product owner and involve the team in user stories and backlog updates.

Learn to support organizational change by aligning motivation and reward systems with regulations, policies, and the operating environment, while reinforcing a shared vision, information sharing norms, and guidance for stakeholders.

Assess culture by examining structural options: functional, matrix (weak to strong), and project teams with full-time managers guiding budgets; PMOs range from supportive to directive, shaping governance and value delivery.

Evaluate the impact of organizational change by leveraging organizational process assets, applying change management plans, and aligning with agile prioritization of changes.

Evaluate the project's organizational impact through a structured rollout, training, and change management plan, detailing prerequisites, change control, and artifacts to align with scope and deliver benefits.

Master the business environment by understanding compliance, value, and the four activities—moving, adding, changing, and deleting—and manage change via integrated change control, the change control board, and stakeholder communication.