CAPM Exam Dumps - Certified Associate in Project Management (CAPM)

According to the PMBOK® Guide, the Determine Budget process involves aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline. To do this accurately, the project manager must review specific project documents that provide the necessary data and context for those costs.

Basis of Estimates, Cost Estimates, Project Schedule, and Risk Register (Choice B): These are all primary Inputs to the Determine Budget process:

Cost Estimates: These provide the direct monetary requirements for each activity within a work package.

Basis of Estimates: This document provides the supporting detail behind the cost estimates, explaining how they were derived and what assumptions were made (e.g., current exchange rates, labor categories).

Project Schedule: The budget must be time-phased. The schedule contains the planned start and finish dates for activities, which determines when the funds will be expended.

Risk Register: This is reviewed to determine the necessary Contingency Reserves. Identified risks and their planned responses have associated costs that must be factored into the total budget.

Choice A: While Contracts and Procurement Documents are inputs, " Requirements Documentation " is a more indirect input. Choice B is more comprehensive regarding the core data needed to build the mathematical baseline.

Choice B: The Business Case and Project Charter are higher-level documents usually used during project initiation. While they provide the " ceiling " for the budget, they do not provide the granular data required to determine the detailed budget during the planning phase.

Choice D: The Scope Baseline is a critical input, but the Resource Management Plan and Activity List are typically used to create the cost estimates in the previous process (Estimate Costs). By the time you are determining the budget, you are using the outputs of those earlier steps.

By aggregating these specific documents, the project manager creates the Cost Baseline, which is the approved version of the time-phased project budget, excluding any management reserves.

In Adaptive (Agile) project management, specifically within the Scrum framework as detailed in the Agile Practice Guide and the Scrum Guide, there is a clear distinction between Events (ceremonies) and Artifacts. The question states that " project events " have already been defined and that " artifacts " are missing.

Why Choice B and D are correct:

Artifacts are designed to maximize transparency of key information. They represent work or value.

B (Sprint Backlog): This is a primary Scrum artifact. It consists of the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.

D (Increments): An Increment is a concrete stepping stone toward the Product Goal. It is a primary artifact representing the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.

Analysis of other options:

A, C, and E (Daily Scrum, Sprint Review, Sprint Retrospective): These are Events (ceremonies), not artifacts. Since the team member specifically pointed out that " artifacts are missing " after " events " were defined, these options would be redundant.

Daily Scrum: A 15-minute event for the developers.

Sprint Review: An event held at the end of the sprint to inspect the increment.

Sprint Retrospective: An event to plan ways to increase quality and effectiveness.

Key Concept: The Project Management Institute (PMI) emphasizes the importance of the three pillars of Scrum: transparency, inspection, and adaptation. Artifacts (Choice B and D) provide the transparency needed for the events (Choice A, C, and E) to be effective. Without the artifacts, there would be nothing tangible to inspect or adapt during the defined project events.

In accordance with the PMBOK® Guide (Project Integration Management), the Direct and Manage Project Work process is the process of leading and performing the work defined in the project management plan and implementing approved changes to achieve the project’s objectives.

The primary and most significant output of this process is Deliverables.

Nature of Deliverables: A deliverable is any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project.

Execution Focus: Because Direct and Manage Project Work is the " doing " phase of the project, this is where the actual physical or digital components of the project are created.

Data Flow: Once deliverables are produced in this process, they typically move to the Control Quality process for inspection to become " Verified Deliverables, " and subsequently to Validate Scope to become " Accepted Deliverables. "

Other Outputs: This process also produces Work Performance Data, Issue Logs, Change Requests, and updates to the Project Management Plan and project documents.

Analysis of Distractors:

B. Activity lists: This is an output of the Define Activities process (Project Schedule Management). It is a planning document, not a result of the execution process.

C. A work breakdown structure (WBS): This is an output of the Create WBS process (Project Scope Management). It serves as a framework for the work but is not the work itself.

D. A scope statement: This is an output of the Define Scope process (Project Scope Management). It provides the detailed description of the project and product but is a planning artifact.

According to the PMBOK® Guide, Make-or-Buy Analysis is a specific tool and technique used during the Plan Procurement Management process. This analysis is fundamental to determining whether particular work can best be accomplished by the project team or should be purchased from outside sources.

Plan Procurement Management: This is the process of documenting project procurement decisions, specifying the approach, and identifying potential sellers. Since the decision to " make " or " buy " dictates the entire procurement strategy, it must occur during the planning phase.

The Analysis: It involves evaluating the risks, costs (both direct and indirect), and organizational capacity. For example, while it might be cheaper to " buy " a software solution, the organization might decide to " make " it to retain intellectual property or ensure long-term support.

Output: The results of this analysis lead to Make-or-Buy Decisions, which are formal documented decisions that influence the procurement statement of work and the procurement strategy.

Analysis of other options:

A. Conduct Procurements: This process focuses on obtaining seller responses, selecting a seller, and awarding a contract. The decision to buy has already been made by this stage.

C. Analyze Procurements: This is not a formal PMI process name. While analysis occurs throughout procurement, it is not a categorized process in the PMBOK® Guide.

D. Control Procurements: This process involves managing procurement relationships, monitoring contract performance, and making changes/corrections. It occurs during the monitoring and controlling phase, long after the initial make-or-buy decision.

In the PMI framework, the Make-or-Buy Analysis ensures that the project manager and the performing organization optimize resources by choosing the most cost-effective and least risky path for deliverable production.

According to the PMBOK® Guide, specifically in the Control Costs process within the Project Cost Management knowledge area, the Cost Performance Index (CPI) is the specific metric used to measure the cost efficiency of a project.

Definition of CPI: CPI is a measure of the cost efficiency of budgeted resources, expressed as the ratio of earned value ($EV$) to actual cost ($AC$). The formula is:

$$CPI = \frac{EV}{AC}$$

Efficiency Indicator: Because it is an index (a ratio), it tells you how much value you are getting for every dollar spent.

A CPI of 1.0 indicates the project is exactly on budget (spending $1 to get $1 of work).

A CPI greater than 1.0 indicates that the work is being performed with better efficiency than planned (under budget).

A CPI less than 1.0 indicates that the work is being performed inefficiently (over budget).

Importance: CPI is considered the most critical EVM metric as it influences the calculation of the Estimate at Completion (EAC). It provides a clear snapshot of how efficiently the project team is using the financial resources allocated to the project.

Why other options are incorrect:

Option A: Cost variance (CV): While CV also relates to cost performance, it is expressed as a currency value ($CV = EV - AC$) rather than a ratio. It shows the magnitude of the deviation from the budget, but not the " efficiency rate " or " percentage " of efficiency.

Option C: To-complete performance index (TCPI): TCPI is a measure of the cost performance that must be achieved with the remaining resources to meet a specific goal (like the original BAC or a new EAC). It describes the efficiency required for the future, not the efficiency of the work already completed.

Option D: Variance at completion (VAC): VAC is a projection of the final budget deficit or surplus ($VAC = BAC - EAC$). It is a forecasting metric used to see where the project will end up, not a measure of current work efficiency.

In the PMBOK® Guide, the act of deciding which processes are appropriate for a specific project is known as Tailoring. Even in a Predictive approach, the project manager does not blindly follow every possible process; instead, they select the most relevant tools and techniques based on the project’s unique context.

Why Choice A is correct:

Collaboration: The Project Manager (PM) should not work in a vacuum. Engaging the project team allows the PM to leverage the specialized expertise of team members to identify which processes are necessary to create the specific deliverables required.

Value-Driven: By focusing on the " project objectives, " the team ensures that every process included in the management plan adds value and contributes to the final goal, rather than just adding administrative overhead.

Buy-in: Involving the team early in the planning process (specifically during the Develop Project Management Plan process) fosters a sense of ownership and clarity regarding their roles and responsibilities.

Analysis of other options:

B (Integrate hybrid approach): The question specifically states this is a " predictive approach. " Forcing a hybrid model solely due to a six-month timeline is a change in strategy that may not be appropriate if the scope is stable and well-defined.

C (Identify processes for only current phase): While this describes Rolling Wave Planning, the question asks about determining the processes for the Project Management Plan (the master document). A PM plan must define the overall methodology for the entire project lifecycle, even if certain details are elaborated later.

D (Follow organizational methodology for all deliverables): This is " rigid " project management. Organizations provide a methodology as a framework, but PMI emphasizes that the PM must still tailor that framework. Producing " all " deliverables without considering necessity leads to waste.

Tailoring Considerations: The PM and the team should consider the project’s size, complexity, and regulatory environment. For a six-month project, " Lean " predictive management might be preferred over a heavy, documentation-intensive process. Choice A ensures the resulting plan is " fit for purpose. "

According to the PMBOK® Guide, there is a distinct difference between how product scope and project scope are measured.

Project Scope Completion: The completion of the project scope is measured against the Project Management Plan. Specifically, it is measured against the Scope Baseline, which is a key component of the plan. The Scope Baseline consists of the approved version of the Project Scope Statement, the Work Breakdown Structure (WBS), and the WBS Dictionary.

Product Scope Completion: In contrast, the completion of the product scope is measured against the Product Requirements.

The Baseline Concept: Because the Project Management Plan contains the formal definitions of what work is included (and what is excluded), it serves as the " yardstick " for determining if the project has successfully completed its intended tasks. During the Validate Scope process, the actual work performed is compared to this plan to gain formal acceptance from the customer or sponsor.

Analysis of Other Options:

A. requirements documentation: This is used to measure the completion of the product scope (the features and functions that characterize a product, service, or result).

B. project scope statement: While the scope statement is part of the baseline, the PMBOK® Guide explicitly states that project scope completion is measured against the Project Management Plan as it contains the integrated baseline.

D. work performance measurements: These are used to assess the status and progress of project activities, but they are not the standard against which final completion is verified. Measurement against these helps identify variances, but the " finish line " is defined by the plan.

According to the PMBOK® Guide (Project Management Body of Knowledge), specifically within the Project Cost Management knowledge area and the Control Costs process, the Schedule Variance (SV) is a measure of schedule performance expressed as the difference between the earned value and the planned value.

To calculate the SV for Task 8 using the data provided in the table:

Identify the variables for Task 8:

Earned Value (EV) = 9,000

Planned Value (PV) = 10,000

Apply the SV Formula:

$$\text{SV} = \text{EV} - \text{PV}$$

Perform the calculation:

$$\text{SV} = 9,000 - 10,000 = -1,000$$

Option B (-1,000): This is the correct calculation. A negative schedule variance indicates that the project is behind schedule compared to the plan. In this instance, Task 8 has accomplished $1,000$ less work than was scheduled to be completed by this point.

Option C (1,000): This would be the result if you incorrectly subtracted EV from PV ($10,000 - 9,000$). A positive SV would indicate the project is ahead of schedule, which is not supported by the Task 8 data.

Option A (-2,000): This would be the result if you incorrectly subtracted AC from PV ($8,000 - 10,000$). This calculation does not represent a standard Earned Value metric.

Option D (2,000): This result is mathematically inconsistent with the provided Task 8 figures.

In the PMI framework, the Schedule Variance (SV) is a critical indicator used in the Monitor and Control Project Work process. While it eventually reaches zero when the project is completed (because all PV is earned), during execution, it serves as an early warning sign that the project may require schedule compression techniques like crashing or fast-tracking to meet the baseline finish date.