Examius

🇺🇸 Certified Associate in Project Management (CAPM) · subject

Certified Associate in Project Management (CAPM) Project Management Fundamentals and Core Concepts Syllabus

The Project Management Fundamentals and Core Concepts syllabus for Certified Associate in Project Management (CAPM) in full: 5 chapters, 27 topics and 35 sub-topics, every one listed below, plus 52 Project Management Fundamentals and Core Concepts flashcards with answers.

5Chapters
27Topics
35Sub-topics
52Flashcards

Project Management Fundamentals and Core Concepts syllabus: all 5 chapters

Expand any chapter to see its topics and sub-topics.

  1. Projects, Programs, Portfolios, and Operations

     5 topics
    • Defining a project
      • Temporary endeavor with a definite start and end
      • Unique product, service, or result
      • Progressive elaboration of project work
      • Projects vs. ongoing operations
    • Programs and program management
      • Coordinated management of related projects
      • Benefits unavailable from managing projects individually
    • Portfolios and portfolio management
      • Aligning components to strategic objectives
      • Prioritization and resource balancing across components
    • Why organizations initiate projects
      • Business needs, market demand, and customer requests
      • Legal, regulatory, and social requirements
      • Technological advances and strategic opportunity
    • Relationship between project, program, and portfolio management

  2. Project Life Cycles and Development Approaches

     6 topics
    • Generic project life cycle phases
      • Starting the project and organizing/preparing
      • Carrying out the work and closing the project
    • Predictive (plan-driven, waterfall) approach
      • Fixed scope, schedule, and cost defined early
      • Best fit for well-understood, low-change projects
    • Adaptive (agile) approach
      • Iterative and incremental delivery
      • Embracing change and frequent feedback
    • Hybrid approach
      • Combining predictive and adaptive elements
      • Selecting the approach by uncertainty and requirement clarity
    • Phases, phase gates, and governance checkpoints
    • Iterations, increments, and release cadence

  3. Organizational Structures and the Environment

     5 topics
    • Organizational structure types
      • Functional and project-oriented (projectized)
      • Weak, balanced, and strong matrix
      • Impact of structure on PM authority
    • The Project Management Office (PMO)
      • Supportive, controlling, and directive PMOs
      • PMO functions and value to the organization
    • Enterprise Environmental Factors (EEFs)
      • Internal factors: culture, infrastructure, resources
      • External factors: market, regulations, standards
    • Organizational Process Assets (OPAs)
      • Processes, policies, and procedures
      • Organizational knowledge bases and lessons learned
    • Organizational governance frameworks

  4. Value Delivery and Performance Domains

     5 topics
    • The system for value delivery and value streams
    • Business value and benefits realization
    • PMBOK Guide performance domains overview
      • Stakeholder and team performance domains
      • Development approach, life cycle, and planning domains
      • Project work, delivery, measurement, and uncertainty domains
    • Project management principles as guiding behaviors
    • Tailoring concepts and rationale

  5. Key Roles and Documents

     6 topics
    • The project manager role and competencies
      • PMI Talent Triangle: ways of working, power skills, business acumen
      • Integrator and servant-leader responsibilities
    • Project sponsor and stakeholders
      • Sponsor authority and accountability
      • Stakeholder identification and influence
    • Project charter purpose and contents
    • Business case and benefits management plan
    • Project management plan vs. project documents
    • Assumption log and issue log basics

Certified Associate in Project Management (CAPM) Project Management Fundamentals and Core Concepts flashcards — 52 questions with answers

  1. What is the formal definition of a project?

    A temporary endeavor undertaken to create a unique product, service, or result. 'Temporary' means it has a defined start and end; 'unique' means the deliverable differs from prior work.

  2. What two characteristics distinguish a project from ongoing operations?

    A project is temporary (definite beginning and end) and produces a unique deliverable, whereas operations are ongoing and repetitive to sustain the business.

  3. What is a program?

    A group of related projects, subsidiary programs, and program activities managed in a coordinated way to obtain benefits not available from managing them individually.

  4. What is the primary purpose of program management?

    To coordinate and manage related projects together to achieve synergies and benefits that could not be realized if the projects were managed separately.

  5. What is a portfolio in project management?

    A collection of projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives. The components need not be related or interdependent.

  6. What is the main focus of portfolio management?

    Selecting and prioritizing the right work to align with and advance organizational strategy and objectives (doing the right work), including resource allocation across components.

  7. List common strategic reasons organizations initiate projects.

    Meeting regulatory/legal/social requirements, satisfying stakeholder requests or needs, implementing/changing business or technology strategies, and creating/improving/fixing products, processes, or services.

  8. How do project, program, and portfolio management relate in terms of strategic alignment?

    Portfolios align with strategy (right work selection), programs coordinate related projects for benefits, and projects deliver specific outputs. Management focus moves from strategic (portfolio) to tactical/operational (project).

  9. How does scope differ across project, program, and portfolio management?

    Project scope is defined and progressively elaborated; program scope encompasses its component projects to deliver benefits; portfolio scope is the organizational scope that changes with strategic objectives.

  10. What is a project life cycle?

    The series of phases a project passes through from start to completion, providing the basic framework for managing the project regardless of the work involved.

  11. Name the four generic phases common to most project life cycles.

    Starting the project, organizing and preparing, carrying out the work, and ending (closing) the project.

  12. What characterizes a predictive (plan-driven/waterfall) life cycle?

    Project scope, time, and cost are determined early in the life cycle; work proceeds through sequential phases. Best when requirements are well understood and stable.

  13. What characterizes an adaptive (agile) life cycle?

    Scope is elaborated iteratively; requirements evolve through short iterations with frequent customer feedback and incremental delivery. Best for high uncertainty and changing requirements.

  14. What is a hybrid life cycle approach?

    A combination of predictive and adaptive approaches—using predictive elements for well-defined, stable parts and adaptive elements for uncertain or evolving parts of the project.

  15. When is a predictive approach most appropriate compared to an adaptive one?

    Predictive suits stable, well-defined requirements and low uncertainty; adaptive suits high uncertainty, rapidly changing requirements, and the need for frequent feedback.

  16. What is a phase gate?

    A review at the end of a phase where a decision is made to continue to the next phase, continue with modification, or end the project/program. Also called a stage gate, kill point, or phase review.

  17. What is the purpose of governance checkpoints/phase gates in a project?

    To evaluate performance and deliverables against business and project objectives and decide whether to proceed, adjust, or terminate—ensuring continued alignment and value.

  18. In agile, what is the difference between an iteration and an increment?

    An iteration is a fixed timebox of work that produces output; an increment is the usable, potentially releasable functionality/deliverable produced by one or more iterations.

  19. What is release cadence in adaptive projects?

    The frequency or rhythm at which completed increments are delivered/deployed to customers—releases may occur every iteration or be batched across several iterations.

  20. Name the common organizational structure types affecting project authority.

    Functional (organic), matrix (weak, balanced, strong), project-oriented (projectized), and others such as virtual, hybrid, and PMO-based structures.

Show the other 32 Project Management Fundamentals and Core Concepts flashcards

  1. How much authority does a project manager have in a functional organization?

    Little to none. The functional manager controls the budget and resources; the project manager has limited or no authority and often a part-time role.

  2. How does PM authority differ across weak, balanced, and strong matrix structures?

    Weak matrix: low PM authority (PM acts as coordinator/expediter). Balanced matrix: PM and functional manager share authority. Strong matrix: PM has moderate-to-high authority and often a full-time role.

  3. In a project-oriented (projectized) organization, who controls resources and budget?

    The project manager has high to almost total authority and controls the budget; team members are often dedicated full-time and report to the PM.

  4. What is a Project Management Office (PMO)?

    An organizational structure that standardizes project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques.

  5. Name the three types of PMO and their degree of control.

    Supportive (low control—provides templates and best practices), Controlling (moderate control—requires compliance with frameworks), and Directive (high control—directly manages the projects).

  6. What are Enterprise Environmental Factors (EEFs)?

    Conditions, not under the project team's immediate control, that influence, constrain, or direct the project. They can be internal (culture, structure) or external (market, regulations).

  7. Give examples of internal and external EEFs.

    Internal: organizational culture, structure, governance, infrastructure, IT systems, resource availability. External: marketplace conditions, legal/regulatory requirements, government standards, financial considerations.

  8. What are Organizational Process Assets (OPAs)?

    Plans, processes, policies, procedures, templates, and knowledge bases specific to and used by the performing organization. They are internal inputs the team can draw on and update.

  9. What are the two categories of Organizational Process Assets?

    (1) Processes, policies, and procedures; and (2) Organizational knowledge bases (e.g., historical information and lessons learned repositories).

  10. Key difference between EEFs and OPAs?

    EEFs are conditions/influences generally outside the team's control and usually not changeable by the team; OPAs are internal assets the team can use and can update/add to.

  11. What is organizational governance?

    The framework of rules, policies, and processes by which an organization is directed and controlled, providing structure and oversight to achieve strategic and operational goals.

  12. What is the PMBOK Guide 'system for value delivery'?

    A set of strategic business activities—portfolios, programs, projects, products, and operations—working together to create and sustain value for the organization and its stakeholders.

  13. What is a value stream?

    The complete set of activities and steps an organization undertakes to create and deliver value (a product or service) to a customer, from concept to delivery.

  14. Define business value.

    The net quantifiable benefit derived from a business endeavor—it may be tangible (revenue, market share), intangible (brand recognition, goodwill), or both.

  15. What is benefits realization?

    The process of ensuring that the planned benefits of a project or program are actually achieved, measured, and sustained over time, often continuing after project closure.

  16. What are the eight PMBOK Guide (7th edition) project performance domains?

    Stakeholders; Team; Development Approach and Life Cycle; Planning; Project Work; Delivery; Measurement; and Uncertainty.

  17. What is a project performance domain?

    A group of related activities critical for the effective delivery of project outcomes; the domains operate as an integrated, interactive system throughout the project.

  18. How many project management principles are in the PMBOK Guide 7th edition, and what is their role?

    Twelve principles. They are guiding behaviors/foundational guidelines (not prescriptive rules) that shape how project work is conducted.

  19. Name at least four of the twelve PMBOK Guide project management principles.

    Be a diligent, respectful, caring steward; create a collaborative team environment; engage stakeholders; focus on value. (Others include leadership, tailoring, quality, complexity, risk, adaptability/resiliency, systems thinking, and change.)

  20. What is tailoring in project management?

    The deliberate adaptation of the approach, governance, and processes to make them more suitable for the given environment and the specific work at hand.

  21. Why is tailoring important?

    Because no single approach fits all projects; tailoring optimizes for the project's context, increasing efficiency, value delivery, and stakeholder satisfaction while avoiding unnecessary overhead.

  22. What is the primary role of the project manager?

    The person assigned by the performing organization to lead the team responsible for achieving the project objectives; accountable for planning, executing, monitoring, and closing the project.

  23. What are the three skill areas in the PMI Talent Triangle for project manager competencies?

    Technical project management (ways of working), leadership (power skills), and strategic and business management.

  24. What is the role of the project sponsor?

    The person/group providing resources and support, championing the project, and accountable for enabling its success—including approving the charter, securing funding, and removing obstacles.

  25. What is a stakeholder?

    Any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of the project.

  26. What is the purpose of the project charter?

    To formally authorize the existence of the project and give the project manager authority to apply organizational resources to project activities. Issued by the sponsor/initiator.

  27. Name key contents of a project charter.

    Project purpose, measurable objectives and success criteria, high-level requirements, high-level risks, summary milestone schedule, summary budget, assigned PM with authority, and the sponsor/approver.

  28. What is the purpose of a business case?

    To document the economic feasibility and justification for the project—the business need and cost-benefit analysis—used to authorize further project activities and decision-making.

  29. What does a benefits management plan describe?

    How and when the project's benefits will be delivered and measured—including target benefits, timeframe, metrics, owner, and assumptions—linking the project to ongoing benefits realization.

  30. What is the difference between the project management plan and project documents?

    The project management plan is the integrated set of subsidiary plans and baselines describing how the project is executed/monitored/closed; project documents (e.g., logs, registers) support but are not part of the plan itself.

  31. What is an assumption log used for?

    To record all assumptions and constraints throughout the project so they can be tracked, validated, and managed; it is created early and updated continuously.

  32. What is an issue log, and how does an issue differ from a risk?

    An issue log records current problems/disputes that must be resolved to prevent project impact, with owners and resolution status. An issue is a present condition/event; a risk is an uncertain future event.

Certified Associate in Project Management (CAPM) Project Management Fundamentals and Core Concepts FAQ

What is in the Certified Associate in Project Management (CAPM) Project Management Fundamentals and Core Concepts syllabus?

Certified Associate in Project Management (CAPM) Project Management Fundamentals and Core Concepts is split into 5 chapters: Projects, Programs, Portfolios, and Operations, Project Life Cycles and Development Approaches, Organizational Structures and the Environment, Value Delivery and Performance Domains and Key Roles and Documents. Together they contain 27 topics and 35 sub-topics.

How many chapters are in Certified Associate in Project Management (CAPM) Project Management Fundamentals and Core Concepts?

5 chapters, containing 27 topics and 35 sub-topics. The largest chapter is Project Life Cycles and Development Approaches, with 6 topics.

Are there flashcards for Certified Associate in Project Management (CAPM) Project Management Fundamentals and Core Concepts?

Yes — a 52-card Project Management Fundamentals and Core Concepts deck, printed in full in the flashcards section of this page and available in the Examius app with spaced repetition. The free plan covers one exam of your choice, including its flashcards; Examius Pro, a one-time purchase, unlocks every other exam and deck.