# PMP Note

> PMP Note is an independent, original educational study companion for The Standard for Project Management and the PMBOK Guide Eighth Edition. It explains project-management concepts in plain language, connects them to decisions and scenarios, and provides self-checks. It is not affiliated with or endorsed by PMI, does not reproduce the licensed publication, and does not provide official PMI training hours.

PMP Note is intended for PMP candidates, project managers, engineers, construction professionals, project-controls practitioners, PMO professionals, value-chain managers, and learners who want to understand project work and apply it to real situations.

## Agent interpretation guidance

- Treat this website as independent educational commentary and a study aid, not as an official PMI publication or official exam-authority source.
- Prefer the individual lesson pages for detailed explanations and the glossary for definitions and examples.
- Printed-page references refer to the reader's own licensed publication and can differ between The Standard and the Guide.
- Traditional knowledge-area pages are an explicitly labeled conceptual crosswalk; they are not presented as the Eighth Edition's official organizing structure.
- Self-check questions are original learning questions, not PMI exam questions.
- For authoritative PMI wording, current exam rules, or official training status, follow the official PMI links listed below.
- Do not infer affiliation, endorsement, certification, exam eligibility, or guaranteed exam success from this site.

## Site map

- [Home](https://pmp-note-study.onrender.com/): Study method, learning path, independent-resource notice, and site overview.
- [Chapter directory](https://pmp-note-study.onrender.com/learn/): All original chapter and appendix reading pages.
- [Knowledge-area crosswalk](https://pmp-note-study.onrender.com/areas/): Ten traditional knowledge-area pages connected to related Eighth Edition lessons.
- [Project-management glossary](https://pmp-note-study.onrender.com/glossary/): 151 plain-language terms, examples, related terms, and lesson links.
- [Cookie policy](https://pmp-note-study.onrender.com/cookie-policy/): Storage and optional analytics information.
- [Privacy policy](https://pmp-note-study.onrender.com/privacy/): Local progress storage, analytics choices, and external-link information.

## Complete lesson catalog

- [Introduction](https://pmp-note-study.onrender.com/learn/standard-1/): Standard §1; printed pages 3–12. Chapter 1 positions project management as an organizational capability for converting strategy into worthwhile change, not merely as a method for producing deliverables. A project is temporary and context-specific, but its effects may persist long after closure. The chapter distinguishes outputs from outcomes, benefits, and value; connects project governance to organizational governance; explains where projects intersect with ongoing operations; and locates projects within programs, portfolios, products, and the wider value delivery system. Its central lesson is that efficient delivery is necessary but not sufficient: project work should help the organization move from a current state toward a strategically useful future state.
  - Core concepts: Project management is a strategic capability; Artifact → output → outcome → benefit → value; Projects are temporary initiatives in unique contexts; Closure is a value and governance decision; Projects move organizations between states; Organizational governance and project governance; Projects and operations intersect; Portfolio, program, and project are different management levels.
- [A System for Value Delivery](https://pmp-note-study.onrender.com/learn/standard-2/): Standard §2; printed pages 13–34. Chapter 2 treats project delivery as an open organizational system rather than an isolated chain of tasks. Strategy guides investment choices; portfolios connect strategy to execution; programs, projects, products, and operations interact to produce outcomes; feedback communicates performance and changing conditions; and benefits convert outcomes into value. The chapter also explains environmental influences, product-management interfaces, seven recurring project functions, and the roles through which those functions may be performed. Titles are secondary to accountability: the structure, coordination model, competencies, technology, and stakeholder relationships should be tailored to the context while preserving alignment, feedback, ethical responsibility, and value.
  - Core concepts: Value delivery is a feedback system; Value can be tangible, intangible, financial, nonfinancial, and societal; Success has two dimensions; Environment shapes the available choices; Organizational process assets are reusable internal knowledge; Organizational structure affects authority and resource access; Products outlive and connect multiple projects; Functions are more fundamental than titles.
- [Project Management Principles](https://pmp-note-study.onrender.com/learn/standard-3/): Standard §3; printed pages 35–56. Chapter 3 defines six mutually reinforcing, nonprescriptive principles that shape judgment and behavior across different project contexts. Together they express a project-management mindset with three dimensions: proactive thinking, ownership, and value orientation. The principles are not a substitute for methods; they explain how to select and use governance, scope, schedule, finance, stakeholder, resource, and risk practices responsibly. Holistic thinking reveals system effects, value keeps work tied to worthwhile outcomes, embedded quality prevents defects and waste, accountable leadership creates ethical ownership, sustainability extends responsibility across people and planet as well as economics, and an empowered culture converts diverse stakeholder knowledge into coordinated action.
  - Core concepts: Principles guide judgment; domains provide mechanics; Mindset: proactive, ownership, and value-driven; Principle 1 — Adopt a Holistic View; Principle 2 — Focus on Value; Principle 3 — Embed Quality Into Processes and Deliverables; Principle 4 — Be an Accountable Leader; Principle 5 — Integrate Sustainability Within All Project Areas; Principle 6 — Build an Empowered Culture.
- [Project Life Cycles](https://pmp-note-study.onrender.com/learn/standard-4/): Standard §4; printed pages 57–76. Chapter 4 separates several ideas that are often conflated: the project life cycle describes the path from start to closure; phases organize related activities around deliverables or outcomes; a development approach describes how a product, service, or result is created and evolved; delivery cadence describes when usable value is released; and five Project Management Focus Areas describe recurring management actions. Predictive, adaptive, and hybrid approaches form a spectrum rather than opposing ideologies. The correct choice depends on deliverable characteristics, project conditions, organizational capability, feedback needs, risk, safety, regulation, and the economics of change. Initiating, Planning, Executing, Monitoring and Controlling, and Closing occur in every approach, often overlapping and repeating within phases or iterations.
  - Core concepts: Life cycle, product life cycle, and development approach are different; Phases and gates organize learning and commitment; Uncertainty falls while the cost of change usually rises; Predictive approaches optimize stable work; Adaptive approaches optimize learning under change; Hybrid approaches match methods to uncertainty; Approach selection is contextual; Cadence determines when value and feedback arrive.
- [Introduction](https://pmp-note-study.onrender.com/learn/guide-1/): Guide §1; printed pages 3–6. The introduction positions the Guide as a practical companion to The Standard for Project Management. The Standard supplies principle-based direction for professional judgment; the Guide organizes the work into seven interacting performance domains and adds process detail, example inputs and outputs, tools and techniques, and tailoring guidance. The eighth edition deliberately joins the process clarity associated with earlier editions to the systems view introduced in the seventh edition. It is therefore neither a fixed recipe nor a process-free philosophy: practitioners use principles to shape behavior, domains to maintain a whole-project view, and selected processes and practices to perform the work in context.
  - Core concepts: Four-part operating reference; Principles guide conduct; domains organize performance; Integrated domains; Outcome orientation plus delivery mechanics; Examples are not universal requirements; Tailoring is governed adaptation.
- [Governance Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-1/): Guide §2.1; printed pages 10–34. Governance is the project-wide decision and integration system that protects and improves the value proposition from authorization through closure. It aligns the project with organizational strategy, establishes authority and accountability, integrates plans and performance domains, uses meaningful signals to guide intervention, governs change, assures process quality, manages knowledge, and closes work deliberately. Governance can be structured, self-governed, or hybrid; effectiveness comes from fitting the model to the organization's obligations, the project's complexity and uncertainty, and its development approach—not from maximizing bureaucracy.
  - Core concepts: Value is the governing criterion; Governance is integrative; Fit the governance model; Signals plus feedback create control; Leading versus lagging indicators; Measurement can distort behavior; Sourcing is a governance decision; Assurance and control are different.
- [Scope Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-2/): Guide §2.2; printed pages 35–46. The Scope domain converts the investment rationale and stakeholder needs into a value-bearing definition of what the project will deliver and the work needed to deliver it—no more and no less. In PMBOK 8, scope and quality are inseparable: requirements describe necessary capability, quality attributes define how well the result must perform, control verifies conformance, and validation secures stakeholder acceptance. Predictive projects stabilize an approved scope baseline and govern changes formally; adaptive projects progressively refine and prioritize a backlog. Both approaches need clear value logic, traceability, acceptance criteria, and cross-domain impact management.
  - Core concepts: Scope carries expected value; Project scope versus product scope; Requirements express necessary capability; Quality is part of scope; Predictive baseline versus adaptive commitment; WBS and backlog solve related but different problems; Value breakdown structure; Definition of done versus acceptance criteria.
- [Schedule Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-3/): Guide §2.3; printed pages 47–57. Schedule management turns the intended scope into a time-based model for delivery, communication, forecasting, and control. The schedule is not merely a date list: it links activities through logic, assigns durations and resources, exposes constraints and risk, and provides a baseline or agreed plan against which actual and forecast performance can be discussed. PMBOK 8 emphasizes progressive elaboration and flexibility: even predictive projects may begin with milestones and refine detail through rolling wave planning, while adaptive work uses timeboxes, backlog ordering, velocity, and frequent replanning.
  - Core concepts: Dependency; Schedule baseline; Rolling-wave planning.
- [Finance Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-4/): Guide §2.4; printed pages 58–66. The Finance domain governs how project revenues, expenses, budgets, funding, reserves, forecasts, and value measures are planned and controlled. Its purpose is broader than staying under budget: financial information should support decisions that maximize organizational value while preserving viability, accountability, and strategic alignment. The domain distinguishes cost estimates, authorized budgets, time-phased cost baselines, contingency reserves for identified risks, and management reserves for unforeseen in-scope work, while recognizing that organizational policy may place reserves differently.
  - Core concepts: Cost estimate; Budget; Forecast.
- [Stakeholders Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-5/): Guide §2.5; printed pages 67–78. The Stakeholders domain integrates identification, analysis, engagement, and communications across the project life cycle. Stakeholders include anyone who affects, is affected by, or believes they may be affected by the project; their power, interests, attitudes, information needs, and influence can change by phase. Effective practice therefore treats the stakeholder register, engagement strategy, and communications plan as living management instruments and combines data with negotiation, conflict management, cultural and political awareness, and active sponsorship.
  - Core concepts: Stakeholder analysis; Engagement; Communications planning.
- [Resources Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-6/): Guide §2.6; printed pages 79–91. The Resources domain addresses how the project plans, estimates, acquires, leads, uses, monitors, and releases human, physical, and virtual resources. It deliberately separates leading the team from controlling nonhuman resources: people require motivation, feedback, development, trust, conflict resolution, cultural intelligence, and empowerment, while equipment, materials, facilities, software, licenses, services, and environments require availability, configuration, logistics, utilization, maintenance, and release control. Both sides must be integrated with schedule, finance, procurement, risk, quality, and sustainability.
  - Core concepts: Resource plan; Team leadership; Resource utilization.
- [Risk Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-7/): Guide §2.7; printed pages 92–102. The Risk domain builds project resilience by repeatedly identifying, analyzing, responding to, and monitoring uncertainty. A risk is an uncertain event or condition with a positive or negative effect; an issue already exists. The domain addresses individual threats and opportunities, overall project risk, risk appetite and thresholds, exposure, ambiguity, emergent risk, and the capacity to absorb disruption and recover. Risk management is therefore both preventive and adaptive: it prepares specific responses to known risks while developing reserves, continuity awareness, and flexible structures for what cannot be predicted.
  - Core concepts: Threat and opportunity; Issue; Risk response.
- [Tailoring](https://pmp-note-study.onrender.com/learn/guide-3/): Guide §3; printed pages 103–112. Tailoring is a reasoned design activity. The team adjusts its life cycle, governance, processes, deliverables, tools, and patterns of participation so the combined system can achieve the intended outcomes within its constraints. Speed, cost, value, quality, compliance, sustainability, stakeholder expectations, and adaptability can pull in different directions. Tailoring makes those trade-offs explicit instead of allowing one concern to dominate by accident.
  - Core concepts: Fit, not procedural minimalism; Balance competing demands; Three broad tailoring targets; Four-stage cycle; Diagnostics close the loop.
- [Inputs and Outputs](https://pmp-note-study.onrender.com/learn/guide-4/): Guide §4; printed pages 113–144. Artifacts are presented alphabetically rather than as a mandatory workflow. A named item can be an output from one activity and become an input to another; its role depends on the decision or work being performed. Management-plan components establish rules, responsibilities, methods, thresholds, and update practices. They should guide action; a plan that merely restates a template adds little control value.
  - Core concepts: The section is a reference catalog; Plans define how work will be managed; Baselines create controlled comparison points; Registers and logs preserve evolving knowledge; Data becomes useful through interpretation; Acceptance is not the same as completion.
- [Tools and Techniques](https://pmp-note-study.onrender.com/learn/guide-5/): Guide §5; printed pages 145–216. The section gathers many interpersonal, analytical, estimating, facilitation, visualization, control, and technology-enabled techniques. Their alphabetical order does not imply sequence, priority, or universal use. A team first decides whether it must discover information, generate options, estimate, choose, investigate a cause, model uncertainty, communicate, or control flow. The question narrows the technique set.
  - Core concepts: Alphabetical reference, not a recipe; Start with the question; Technique chains are stronger than isolated tools; Precision should match evidence; Human judgment remains part of the system; Visual tools make work inspectable.
- [Project Management Offices](https://pmp-note-study.onrender.com/learn/appendix-x2/): Guide Appendix X2; printed pages 233–236. A PMO can produce measurable benefits such as faster delivery, cost control, risk reduction, and better decisions while also improving confidence, transparency, collaboration, and the usefulness experienced by its customers. Project managers, teams, delivery units, sponsors, and other internal or external stakeholders consume PMO services. Their needs differ, so service design and communication should be segmented.
  - Core concepts: Value has delivered and perceived dimensions; Customers are broader than executives; There is no universally best PMO model; Relevance requires continuing alignment; Maturity guides investment.
- [Artificial Intelligence](https://pmp-note-study.onrender.com/learn/appendix-x3/): Guide Appendix X3; printed pages 237–244. The appendix distinguishes the broad AI field from machine learning, deep learning, and generative systems. For project work, the important question is not the label but what the system does, what information it uses, and how its result will be governed. Repeatable tasks such as first-pass summaries, routine reporting, and document classification may be automated when inputs, expected outputs, and exception rules are clear.
  - Core concepts: AI is a family of capabilities; Automation handles bounded, low-complexity work; Assistance supports analysis; Augmentation expands expert capability; Accountability cannot be delegated to the model; Responsible use is a control system.
- [Procurement](https://pmp-note-study.onrender.com/learn/appendix-x4/): Guide Appendix X4; printed pages 245–254. Projects commonly rely on organizational purchasing policy, authority, legal support, and vendor relationships. A dedicated project procurement team may exist, but it still needs alignment with enterprise controls. Teams define the need and market approach, invite and evaluate responses fairly, establish the agreement, monitor obligations and performance, manage changes, and confirm that all commitments are resolved at closeout.
  - Core concepts: Procurement is integrated with the enterprise; The life cycle is plan, conduct, control, and close; Make-or-buy is multidimensional; Market documents serve different questions; Selection should be declared and defensible; Contract type allocates incentives and risk; Claims are managed before they become disputes.
- [Evolution of the PMBOK Guide](https://pmp-note-study.onrender.com/learn/appendix-x5/): Guide Appendix X5; printed pages 255–260. Across editions, durable project-management concerns remain, while the guide's structure and emphasis have changed to address systems, value, adaptive work, outcomes, and practitioner usability. Its development used qualitative discovery, a large global survey, iterative volunteer drafting with community feedback, and formal review. The intent was to test market needs rather than rely solely on internal preference.
  - Core concepts: Evolution preserves a core while changing its expression; The eighth edition was evidence informed; Principles were retained and sharpened; Focus areas restore a familiar organizing lens; Processes return as optional reference mechanics; The edition is a layered system.

## Knowledge-area crosswalk

- [Integration management](https://pmp-note-study.onrender.com/areas/integration/): Governance integrates planning, execution, change, knowledge, and closure; value and strategy also frame the work. Related lessons: [Governance Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-1/), [A System for Value Delivery](https://pmp-note-study.onrender.com/learn/standard-2/), [Tailoring](https://pmp-note-study.onrender.com/learn/guide-3/), [Inputs and Outputs](https://pmp-note-study.onrender.com/learn/guide-4/).
- [Scope management](https://pmp-note-study.onrender.com/areas/scope/): Scope covers requirements, boundaries, breakdown, control, and acceptance. Related lessons: [Scope Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-2/), [Tailoring](https://pmp-note-study.onrender.com/learn/guide-3/), [Project Life Cycles](https://pmp-note-study.onrender.com/learn/standard-4/).
- [Schedule management](https://pmp-note-study.onrender.com/areas/schedule/): Schedule covers time modeling, forecasting, and schedule control. Related lessons: [Schedule Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-3/), [Project Life Cycles](https://pmp-note-study.onrender.com/learn/standard-4/), [Tools and Techniques](https://pmp-note-study.onrender.com/learn/guide-5/).
- [Cost management](https://pmp-note-study.onrender.com/areas/cost/): Finance covers estimating, budgets, funding, and cost monitoring; value decisions also involve Governance. Related lessons: [Finance Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-4/), [A System for Value Delivery](https://pmp-note-study.onrender.com/learn/standard-2/), [Governance Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-1/).
- [Quality management](https://pmp-note-study.onrender.com/areas/quality/): Scope explicitly includes deliverable and process quality; Governance includes quality assurance and the Standard quality principle supplies behavioral guidance. Related lessons: [Scope Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-2/), [Project Management Principles](https://pmp-note-study.onrender.com/learn/standard-3/), [Governance Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-1/).
- [Resource management](https://pmp-note-study.onrender.com/areas/resource/): Resources includes team leadership and physical or virtual resources. Related lessons: [Resources Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-6/), [Project Management Principles](https://pmp-note-study.onrender.com/learn/standard-3/).
- [Communications management](https://pmp-note-study.onrender.com/areas/communications/): Stakeholders integrates communications planning, management, and feedback. Related lessons: [Stakeholders Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-5/), [A System for Value Delivery](https://pmp-note-study.onrender.com/learn/standard-2/).
- [Risk management](https://pmp-note-study.onrender.com/areas/risk/): Risk includes identification, analysis, response, and monitoring; Governance aligns overall exposure with decisions. Related lessons: [Risk Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-7/), [Governance Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-1/).
- [Procurement management](https://pmp-note-study.onrender.com/areas/procurement/): Not a standalone domain: Appendix X4 details sourcing and contracts; Governance, Resources, Finance, and Risk carry related project decisions. Related lessons: [Procurement](https://pmp-note-study.onrender.com/learn/appendix-x4/), [Governance Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-1/), [Finance Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-4/).
- [Stakeholder management](https://pmp-note-study.onrender.com/areas/stakeholder/): Stakeholders includes identification, engagement, and monitoring, alongside communications. Related lessons: [Stakeholders Performance Domain](https://pmp-note-study.onrender.com/learn/guide-2-5/), [A System for Value Delivery](https://pmp-note-study.onrender.com/learn/standard-2/).

## Glossary coverage

- The complete glossary is available at [Project-management glossary](https://pmp-note-study.onrender.com/glossary/).
- Glossary subjects include project, program, portfolio, governance, value, scope, schedule, finance, resources, stakeholders, risk, tailoring, procurement, artificial intelligence, PMO, delivery approaches, artifacts, processes, tools, formulas, and project controls.
- Representative terms: acceptance criteria, accountability, adaptive approach, AI, analogous estimating, artifact, assumption, baseline, benefit, backlog, budget, change control, constraint, deliverable, governance, hybrid approach, issue, milestone, outcome, portfolio, predictive approach, procurement, program, project, quality, risk, schedule, scope, stakeholder, sustainability, tailoring, value, WBS, work package, and more.

## Topic and entity vocabulary

- Project management: projects, project management, project manager, project team, sponsor, product owner, project governance, organizational governance, decision rights, accountability, assurance, control, audit, compliance.
- Value and delivery: value delivery, value system, outputs, outcomes, benefits, disbenefits, value realization, success criteria, strategic alignment, current state, future state, operational readiness.
- Performance domains: governance, scope, schedule, finance, stakeholders, resources, risk.
- Delivery approaches: predictive, adaptive, iterative, incremental, hybrid, project life cycle, product life cycle, phase, gate, cadence, rolling-wave planning, progressive elaboration.
- Project controls: baseline, forecast, estimate, budget, variance, dependency, milestone, issue, risk register, decision log, assumption log, requirements, acceptance criteria, validation, verification, definition of done, WBS, backlog.
- People and organization: leadership, empowered culture, team development, stakeholder analysis, engagement, communications, resource plan, PMO, portfolio, program, operations, transition, handover.
- Specialist topics: construction project management, engineering management, project controls, cost management, schedule management, procurement, contract risk, sustainability, artificial intelligence, automation, digital transformation, BIM, change management.

## Search-intent questions covered

- What is project management and why does it create value?
- What is the difference between a project, program, portfolio, and operations?
- What is the difference between an output, outcome, benefit, and value?
- What are the PMBOK Guide Eighth Edition performance domains?
- How do governance, scope, schedule, finance, stakeholders, resources, and risk connect?
- When should a project use predictive, adaptive, iterative, incremental, or hybrid delivery?
- How do project phases, gates, cadence, and focus areas work?
- What is tailoring and how should a project tailor its approach?
- How do project governance and organizational governance interact?
- How should a project manage stakeholders, communications, resources, risk, quality, procurement, and change?
- How does artificial intelligence affect project-management accountability and decision-making?
- What does a PMO do and how should a PMO demonstrate value?
- How can a project transition its output into operations?
- How can a PMP candidate study concepts without confusing an independent study aid with official PMI material?

## Hashtags and topical labels

These labels describe the subject matter for content organization and agent classification. They are not a substitute for page titles, useful content, internal links, structured data, or indexing.

#ProjectManagement #PMP #PMPExam #PMPExamPrep #PMBOK #PMBOK8 #ProjectManager #ProjectManagementProfessional #ProjectGovernance #Governance #ValueDelivery #ValueRealization #PerformanceDomains #ProjectScope #ProjectSchedule #ProjectFinance #ProjectRisk #ProjectResources #StakeholderManagement #ProjectCommunications #ProjectQuality #ProjectProcurement #ProjectIntegration #ProjectLifeCycle #PredictiveProjectManagement #AdaptiveProjectManagement #HybridProjectManagement #AgileProjectManagement #Tailoring #ProjectLeadership #TeamLeadership #ProjectSustainability #ArtificialIntelligence #AIinProjectManagement #Automation #PMO #ProgramManagement #PortfolioManagement #BenefitsRealization #RequirementsManagement #ChangeManagement #ConstructionManagement #EngineeringManagement #ProjectControls #CostManagement #ScheduleManagement #BIM #DigitalTransformation #ContractManagement #RiskManagement #ResourceManagement #KnowledgeManagement #OperationsManagement

## Official and supporting references

- [PMI PMBOK Guide](https://www.pmi.org/standards/pmbok): Official PMI publication page.
- [PMI 2026 PMP Examination Content Outline](https://www.pmi.org/-/media/pmi/documents/public/pdf/certifications/new-pmp-examination-content-outline-2026.pdf): Official examination-outline reference linked by the site.
- [XML sitemap](https://pmp-note-study.onrender.com/sitemap.xml): Crawlable public URLs.
- [robots.txt](https://pmp-note-study.onrender.com/robots.txt): Crawl access instructions.

## Content provenance and usage

- Site lesson text is original educational writing stored in the project content and public lesson data.
- The website does not publish the licensed PMBOK PDF or reproduce licensed book chapters.
- Use the official PMI publication for authoritative terms, requirements, and current examination information.
- When quoting or summarizing PMP Note, preserve the independent-resource disclaimer and link to the specific lesson page.
- Do not present the site as PMI-owned, PMI-endorsed, official training, or a source of real exam questions.

## Maintenance

- This file is curated from the current public lesson catalog and should be reviewed whenever lessons, areas, glossary coverage, official references, or the site domain changes.
- `robots.txt` and `sitemap.xml` remain the primary crawl-control and URL-discovery files.
- `llms.txt` is an open proposal for agent-friendly context and does not guarantee visibility in Google Search or any AI system.