PMI Certified Associate in Project Management (CAPM) Exam Questions

PMI Certified Associate in Project Management Exam Objectives

1. 1

   1.0 Project Management Fundamentals and Core Concepts (36%)

   • Task 1.1: duration. Determine the number and type of resources in a project. Use a risk register in a given situation. Use a stakeholder register in a given situation. Explain project closure and transitions. Demonstrate an understanding of project roles and responsibilities. Compare and contrast the roles and responsibilities of project managers and project sponsors. Compare and contrast the roles and responsibilities of the project team and the project sponsor. Explain the importance of the role the project manager plays (e.g., initiator, negotiator, listener, coach, working member, and facilitator). Explain the differences between leadership and management. Explain emotional intelligence (EQ) and its impact on project management. Determine how to follow and execute planned strategies or frameworks (e.g., communication, risks, etc.). Give examples of how it is appropriate to respond to a planned strategy or framework (e.g., communication, risk, etc.). Explain project initiation and benefit planning. Demonstrate an understanding of common problem-solving tools and techniques. Evaluate the effectiveness of a meeting. Explain the purpose of focus groups, standup meetings, brainstorming, etc
2. 2

   2.0 Predictive, Plan-Based Methodologies (17%)

   • 2.1Explain when it is appropriate to use a predictive, plan-based approach.
   • 2.2Identify the suitability of a predictive, plan-based approach for the organizational structure (e.g., virtual, colocation, matrix structure, hierarchical, etc.).
   • 2.3Determine the activities within each process.
   • 2.4Give examples of typical activities within each process.
   • 2.5Distinguish the differences between various project components.
   • 2.6Demonstrate an understanding of a project management plan schedule.
   • 2.7Apply critical path methods.
   • 2.8Calculate schedule variance.
   • 2.9Explain work breakdown structures (WBS).
   • 2.10Explain work packages.
   • 2.11Apply a quality management plan.
   • 2.12Apply an integration management plan.
   • 2.13Determine how to document project controls of predictive, planbased projects.
   • 2.14Identify artifacts that are used in predictive, plan-based projects.
   • 2.15Calculate cost and schedule variances.
3. 3

   3.0 Agile Frameworks/Methodologies (20%)

   • Task 3.1: management steps. Interpret success criteria of an adaptive project management
   • Task 3.2: . Prioritize tasks in adaptive project management.
4. 4

   4.0 Business Analysis Frameworks (27%)

   • 4.1Demonstrate an understanding of business analysis (BA) roles and
   • 4.2responsibilities.
   • 4.3Distinguish between stakeholder roles (e.g., process owner, process manager, product manager, product owner, etc.).
   • 4.4Outline the need for roles and responsibilities (Why do you need to identify stakeholders in the first place?).
   • 4.5Differentiate between internal and external roles.
   • 4.6Determine how to conduct stakeholder communication.
   • 4.7Recommend the most appropriate communication channel/tool (e.g., reporting, presentation, etc.).
   • 4.8Demonstrate why communication is important for a business analyst between various teams (features, requirements, etc.).
   • 4.9Determine how to gather requirements.
   • 4.10Match tools to scenarios (e.g., user stories, use cases, etc.).
   • 4.11Identify the requirements gathering approach for a situation (e.g., conduct stakeholder interviews, surveys, workshops, lessons learned, etc.).
   • 4.12Explain a requirements traceability matrix/product backlog.
   • 4.13Demonstrate an understanding of product roadmaps
   • 4.14Explain the application of a product roadmap.
   • 4.15Determine which components go to which releases.
   • 4.16Determine how project methodologies influence business analysis processes.
   • 4.17Determine the role of a business analyst in adaptive and/or predictive, plan-based approaches.
   • 4.18Validate requirements through product delivery.
   • 4.19Define acceptance criteria (the action of defining changes based on the situation).
   • 4.20Determine if a project/product is ready for delivery based on a requirements traceability matrix/product backlog.