Associate Project Management (CAPM) Certification | 5-Days

Domain 1 – Project Management Fundamentals and Core Concepts:

Task 5: 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.

Domain 2 – Predictive, Plan-Based Methodologies:

Task 1: Explain when it is appropriate to use a predictive, plan-based approach.

• Identify the suitability of a predictive, plan-based approach for the organizational structure (e.g., colocation, matrix structure, hierarchical, etc.).
• Determine the activities within each process.
• Give examples of typical activities within each process.
• Distinguish the differences between various project components.

Task 2: emonstrate an understanding of a project management plan schedule.

• Apply critical path methods.
• Calculate schedule variance.
• Explain work breakdown structures (WBS).
• Explain work packages.
• Apply a quality management plan and  integration management plan

Task 3: Determine how to document project controls of predictive, plan based projects.

• Identify artifacts that are used in predictive, plan-based projects.
• Calculate cost and schedule variances.

Domain 3 – Agile Frameworks/Methodologies

Task 1: Explain when it is appropriate to use an adaptive approach.

• Compare the pros and cons of adaptive and predictive, plan-based projects.
• Identify the suitability of adaptive approaches for the organizational structure (e.g., virtual, colocation, matrix structure, hierarchical, etc.).
• Identify organizational process assets and environmental factors that facilitate the use of adaptive approaches.

Task 2: Determine how to plan project iterations.

• Distinguish the logical units of iterations.
• Interpret the pros and cons of the iteration.
• Translate this WBS to an adaptive iteration.
• Determine inputs for scope.
• Explain the importance of adaptive project tracking versus predictive, plan-based tracking.

Task 3: Determine how to document project controls for an adaptive project.

• Identify artifacts that are used in adaptive projects.

Task 4; Explain the components of an adaptive plan.

• Distinguish between the components of different adaptive methodologies (e.g., Scrum, Extreme Programming (XP), Scaled Adaptive Framework (SAFe®), Kanban, etc.)

Domain 3 – Agile Frameworks/Methodologies

Task 5: Determine how to prepare and execute task management steps.

• Interpret success criteria of an adaptive project management task.
• Prioritize tasks in adaptive project management.

Domain 4 – Business Analysis Frameworks

Task 1: Demonstrate an understanding of business analysis (BA) roles and responsibilities.

• Distinguish between stakeholder roles (e.g., process owner, process manager, product manager, product owner, etc.).
• Outline the need for roles and responsibilities (Why do you need to identify stakeholders in the first place?).
• Differentiate between internal and external roles

Task 2: Determine how to conduct stakeholder communication.

• Recommend the most appropriate communication channel/tool (e.g., reporting, presentation, etc.).
• Demonstrate why communication is important for a business analyst between various teams (features, requirements, etc.).

Task 3: Determine how to gather requirements.

• Match tools to scenarios (e.g., user stories, use cases, etc.).
• Identify the requirements gathering approach for a situation (e.g., conduct stakeholder interviews, surveys, workshops, lessons learned, etc.).
• Explain a requirements traceability matrix/product backlog.

Domain 4 – Business Analysis Frameworks

Task 4:  Demonstrate an understanding of product roadmaps.

• Explain the application of a product roadmap.
• Determine which components go to which releases.

Task 5: Determine how project methodologies influence business analysis processes.

• Determine the role of a business analyst in adaptive and/or predictive, plan-based approaches

Task 6: Validate requirements through product delivery.

• Define acceptance criteria (the action of defining changes based on the situation).
• Determine if a project/product is ready for delivery based on a requirements traceability matrix/product backlog.