Scribd
Upload
8 views

CAPM

Uploaded by

Zekariyas Mussie
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
8 views

CAPM

Uploaded by

Zekariyas Mussie
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Project Management Fundamentals and Core Concepts – 36%

1.1 Demonstrate an understanding of the various project life cycles and processes.
• Distinguish between a project, program, and a portfolio.
• Distinguish between a project and operations.
• Distinguish between predictive and adaptive approaches.
• Distinguish between issues, risks, assumptions, and constraints.
• Review/critique project scope.
• Apply the project management code of ethics to scenarios (refer to PMI Code of
Ethics and Professional Conduct).
• Explain how a project can be a vehicle for change.

1.2 Demonstrate an understanding of project management planning.


• Describe the purpose and importance of cost, quality, risk, schedule, etc.
• Distinguish between the different deliverables of a project management plan versus
product management plan. project/product
• Distinguish differences between a milestone and a task duration.
• Determine the number and type of resources in a project.
• Use a risk register in each situation.
• Use a stakeholder register in each situation.
• Explain project closure and transitions.

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

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

1.5 Demonstrate an understanding of common problem-solving tools and techniques.


• Evaluate the effectiveness of a meeting.
• Explain the purpose of focus groups, stand-up meetings, brainstorming, etc.
Predictive, Plan-based Methodologies - 17%

2.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., virtual, 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.

2.2 Demonstrate an understanding of a project management plan schedule.


• Apply critical path methods.
• Calculate schedule variance. - address in 2.3
• Explain work breakdown structures (WBS).
• Explain work packages.
• Apply a quality management plan.
• Apply an integration management plan.

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

Agile Frameworks/Methodologies - 20%

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

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

3.3 Determine how to document project controls for an adaptive project.


• Identify artifacts that are used in adaptive projects. - Burndown charts, product
backlog, DoD, DoR, Kanban board, velocity chart.
3.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.).

3.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 - use scenario with simple criteria
and give a list.

Business Analysis Frameworks - 27%

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

4.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.).

4.3 Determine how to gather requirements.


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

4.4 Demonstrate an understanding of product roadmaps.


• Explain the application of a product roadmap.
• Determine which components goes to which release.

4.5 Determine how project methodologies influence business analysis processes.


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

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

You might also like