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

Project Management Fundamentals and Core Concepts syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Project Management Fundamentals and Core Concepts in Certified Associate in Project Management (CAPM), not a summary of it.

1. 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. 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. 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. 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. 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

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

19 of 52 cards from the Project Management Fundamentals and Core Concepts deck — real questions with worked 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.

See more Project Management Fundamentals and Core Concepts flashcards →

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

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