CAPM Study Notes

PMBOK 6th Edition: Process and Predictive Approach

1. Process Groups Overview
The PMBOK 6th Edition organizes processes into 5 Process Groups:
1. Initiating
o Develop Project Charter.
o Identify Stakeholders.
2. Planning
o Develop Project Management Plan.
o Plan Scope, Schedule, and Cost Management.
o Plan Risk Responses.
3. Executing
o Manage Project Work and Team.
o Implement Risk Responses.
o Conduct Procurements.
 4. Monitoring and Controlling
o Monitor and Control Project Work.
o Perform Integrated Change Control.
o Validate Scope and Control Quality.
5. Closing
o Close Project or Phase.

2. Knowledge Areas and Key Processes

There are 10 Knowledge Areas, each corresponding to processes in the process groups:
1. Integration Management
o Key process: Develop Project Charter, Monitor and Control Project Work.
2. Scope Management
o Key process: Collect Requirements, Define Scope, Create WBS.
3. Schedule Management
o Key process: Define Activities, Sequence Activities, Develop Schedule.
4. Cost Management
o Key process: Estimate Costs, Determine Budget.
5. Quality Management
o Key process: Plan Quality Management, Manage Quality, Control Quality.
6. Resource Management
o Key process: Estimate Activity Resources, Develop and Manage Team.
7. Communications Management
o Key process: Plan, Manage, and Monitor Communications.
8. Risk Management
o Key process: Plan Risk Management, Identify Risks, Perform Risk Responses.
9. Procurement Management
o Key process: Plan Procurement Management, Conduct Procurements.
10. Stakeholder Management
 Key process: Identify Stakeholders, Manage Stakeholder Engagement.

3. Critical Tools and Techniques

1. Earned Value Management (EVM):
o Formulas to calculate performance:
 SPI = EV / PV (Schedule Performance Index).
 CPI = EV / AC (Cost Performance Index).
2. Critical Path Method (CPM):
o Helps identify the longest path in the project schedule to determine project
duration.
3. Risk Management Techniques:
o Probability and Impact Matrix.
o SWOT Analysis (Strengths, Weaknesses, Opportunities, Threats).

PMBOK 7th Edition: Principles and Value-Driven

Approach
1. 12 Project Management Principles (7th Edition)
1. Stewardship: Be a responsible manager.
2. Team Collaboration: Promote team accountability and cooperation.
3. Stakeholder Engagement: Proactively engage stakeholders.
4. Value Focus: Deliver measurable outcomes.
5. Systems Thinking: See the project as part of a larger ecosystem.
6. Leadership: Be a servant leader.
7. Tailoring: Adapt project practices to context.
8. Quality Focus: Maintain consistent quality.
9. Complexity Management: Address project complexities effectively.
10. Risk Optimization: Manage risks to benefit the project.
11. Adaptability and Resilience: Be flexible to change.
12. Change Management: Facilitate and enable change.

2. 8 Performance Domains
1. Stakeholder Performance:
o Identify, analyze, and engage stakeholders.
2. Team Performance:
o Build and lead a high-performing team.
3. Development Approach and Life Cycle:
o Choose predictive, adaptive, or hybrid life cycles.
4. Planning Performance:
o Establish project objectives and baselines.
5. Project Work Performance:
o Ensure smooth execution and monitor progress.
6. Delivery Performance:
o Deliver value and ensure customer satisfaction.
7. Measurement Performance:
o Track project metrics and KPIs.
8. Uncertainty Performance:
o Address and manage uncertainties effectively.

3. Key Concepts
1. Value Delivery:
o Align project objectives with organizational goals.
2. Tailoring:
o Customize project management practices to fit the project environment.
3. Agile, Hybrid, and Predictive Approaches:
o Understand when to apply each methodology.

Agile Practice Guide Highlights

1. Key Agile Principles
1. Customer satisfaction through continuous delivery.
2. Embrace changing requirements.
3. Deliver working solutions frequently.
 4. Collaboration between business and technical teams.
5. Build projects around motivated individuals.
6. Simplicity is essential.
2. Agile Tools and Frameworks
1. Scrum:
o Key roles: Product Owner, Scrum Master, Development Team.
o Events: Sprint Planning, Daily Scrum, Sprint Review, Retrospective.
2. Kanban:
o Visualize work and limit work-in-progress (WIP).
3. Hybrid Approach:
o Combine predictive and agile techniques to suit project needs.

Exam Tips and Practice Areas

1. Key Topics to Master:
o Process Groups and Knowledge Areas (PMBOK 6th).
o Agile Principles and Frameworks (Agile Practice Guide).
o 12 Principles and 8 Performance Domains (PMBOK 7th).
2. Practice Tests:
o Take mock exams to simulate the CAPM test.
o Review situational and knowledge-based questions.
3. Exam Strategy:
o Read each question carefully.
o Manage time effectively (1 minute per question).

A System for Value Delivery - PMBOK 7th E, page 34

The information in this section provides a context for value delivery, governance, project

functions, the project environment, and product management.

▶ Section 2.1 Creating Value. This section describes how projects operate within a system

to produce value for organizations and their stakeholders.

▶ Section 2.2 Organizational Governance Systems. This section describes how governance

supports a system for value delivery.

▶ Section 2.3 Functions Associated with Projects. This section identifies the functions

that support projects.

▶ Section 2.4 The Project Environment. This section identifies internal and external

factors that influence projects and the delivery of value.

▶ Section 2.5 Product Management Considerations. This section identifies the ways

portfolios, programs, projects, and products relate

Creating a new product, service, or result that meets the needs of customers or end users;

▶ Creating positive social or environmental contributions;

▶ Improving efficiency, productivity, effectiveness, or responsiveness;

▶ Enabling the changes needed to facilitate organizational transition to its desired future

state; and

▶ Sustaining benefits enabled by previous programs, projects, or business operations.

2.1.1 VALUE DELIVERY COMPONENTS

There are various components, such as portfolios, programs, projects, products, and
operations, that can be used individually and collectively to create value. Working together, these
components comprise a system for delivering value that is aligned with the organization’s strategy.

Figure 2-1 shows an example of a system to deliver value that has two portfolios comprised of
programs and projects. It also shows a stand-alone program with projects and stand-alone projects
not associated with portfolios or programs. Any of the projects or programs could include products.
Operations can directly support and influence portfolios, programs, and projects, as well as other
business functions, such as payroll, supply chain management, and so forth. Portfolios, programs,
and projects influence each other as well as operations.

2.2 ORGANIZATIONAL GOVERNANCE SYSTEMS The governance system works alongside the value
delivery system to enable smooth workflows, manage issues, and support decision making. Governance
systems provide a framework with functions and processes that guide activities. A governance
framework can include elements of oversight, control, value assessment, integration among
components, and decision-making capabilities. Governance systems provide an integrated structure for
evaluating changes, issues, and risks associated with the environment and any component in the value
delivery system. This includes portfolio objectives, program benefits, and deliverables produced by
projects. Projects can operate within a program or portfolio or as a stand-alone activity. In some
organizations, a project management office might support programs and projects within a portfolio.
Project governance includes defining the authority to approve changes and make other business
decisions related to the project. Project governance is aligned with program and/or organizational
governance.
2.3 FUNCTIONS ASSOCIATED WITH PROJECTS People drive project delivery. They do so by fulfilling
functions necessary for the project to run effectively and efficiently. Functions related to the project can
be fulfilled by one person, by a group of people, or combined into defined roles. Coordinating a
collective work effort is extremely important to the success of any project. There are different types of
coordination suitable for different contexts. Some projects benefit from decentralized coordination in
which project team members self-organize and self-manage. Other projects benefit from centralized
coordination with the leadership and guidance of a designated project manager or similar role. Some
projects with centralized coordination can also benefit from including self-organized project teams for
portions of the work. Regardless of how coordination takes place, supportive leadership models and
meaningful, continuous engagements between project teams and other stakeholders underpin
successful outco
 Project Management Principles SECTION 3 – Page ,49 / 7th edition
Principles for a profession serve as foundational guidelines for strategy, decision making, and problem
solving. Professional standards and methodologies are often based on principles. In some professions,
principles serve as laws or rules, and are therefore prescriptive in nature. The principles of project
management are not prescriptive in nature. They are intended to guide the behavior of people involved
in projects. They are broadly based so there are many ways individuals and organizations can maintain
alignment with the principles. Principles can, but do not necessarily, reflect morals. A code of ethics is
related to morals. A code of ethics for a profession can be adopted by an individual or profession to
establish expectations for moral conduct. The PMI Code of Ethics and Professional Conduct [2] is based

on four values that were identified as most important to the project management community: ▶
Responsibility, ▶ Respect, ▶ Fairness, and ▶ Honesty. The 12 principles of project management are
aligned with the values identified in the PMI Code of Ethics and Professional Conduct. They do not
follow the same format, and they are not duplicative, rather the principles and the Code of Ethics are
complementary. The principles of project management were identified and developed by engaging a
global community of project practitioners. The practitioners represent different industries, cultural
backgrounds, and organizations in different roles and with experience in various types of projects.
Multiple rounds of feedback resulted in 12 principles that provide guidance for effective project
management

Because the principles of project management provide guidance, the degree of

application and the way in which they are applied are influenced by the context of the
organization, project, deliverables, project team, stakeholders, and other factors. The
principles are internally consistent, meaning that no principle contradicts any other
principle. However, in practice there may be times when the principles can overlap. For
example, guidance for navigating complexity can present information that is useful in
recognizing, evaluating, and responding to system interactions or optimizing risk
responses. Principles of project management can also have areas of overlap with
general management principles. For example, both projects and business in general
focus on delivering value. The methods may be somewhat different in projects as
opposed to operations, but the underlying principle associated with focusing on value
can apply to both. Figure 3-1 demonstrates this overlap.

The principle labels are listed here without any specific weighting or order. The principle
statements are presented and described in Sections 3.1 through 3.12. Each section
begins with a
figure that provides the principle label across the top with the principle and key points
under the
label. Following the figure, each principle is elaborated in the text. The principle labels

▶ Be a diligent, respectful, and caring steward (see Section 3.1).

are:

▶ Create a collaborative project team environment (see Section 3.2).

▶ Effectively engage with stakeholders (see Section 3.3).
▶ Focus on value (see Section 3.4).
▶ Recognize, evaluate, and respond to system interactions (see Section 3.5).
▶ Demonstrate leadership behaviors (see Section 3.6).
▶ Tailor based on context (see Section 3.7).
▶ Build quality into processes and deliverables (see Section 3.8).
▶ Navigate complexity (see Section 3.9).
▶ Optimize risk responses (see Section 3.10).
▶ Embrace adaptability and resiliency (see Section 3.11).
▶ Enable change to achieve the envisioned future state (see Section 3.12).