CAPM CAPM Syllabus Exam Questions Answers

According to the PMBOK® Guide, the Cost Baseline is the approved version of the time-phased project budget, excluding any management reserves, which can be changed only through formal change control procedures. It is the primary output of the Determine Budget process.

Process Context: The Determine Budget process aggregates the estimated costs of individual activities or work packages to establish an authorized cost baseline.

Components: The cost baseline includes all authorized budgets but excludes management reserves. Management reserves are intended to cover " unknown unknowns " and are not part of the performance measurement baseline (PMB) but are part of the total project budget.

Usage: It is used as a basis for comparison to actual results to measure and monitor cost performance. In an S-curve graph, the cost baseline represents the cumulative values of the project ' s expected spending over time.

Analysis of other choices:

Choice A (Control Costs): This is a monitoring and controlling process. Its primary outputs include work performance information, cost forecasts, and change requests. It uses the cost baseline as an input to measure variance.

Choice C (Estimate Costs): This process develops an approximation of the monetary resources needed to complete project work. Its primary output is Cost Estimates, which are then used as an input to the Determine Budget process to create the baseline.

Choice D (Estimate Activity Resources): This process identifies the types and quantities of material, human resources, equipment, or supplies required. While this impacts cost, it is a resource management process, not the budget-setting process.

According to the PMBOK® Guide and the general principles of the Project Life Cycle, various project characteristics change as the project progresses from initiation to closure.

Cost of Changes: At the start of a project, the cost of making changes is at its lowest. This is because very little work has been completed, few resources have been committed, and no physical deliverables have been built yet. As the project moves toward completion, the cost of changes increases significantly because rework may involve scrapping completed components or re-ordering materials.

Stakeholder Influences: These are typically at their highest at the start of the project. Stakeholders have the greatest opportunity to influence the final characteristics of the project ' s product and the project ' s scope without significantly impacting cost.

Risk and Uncertainty: Both risk and uncertainty are at their highest at the start of the project. As the project progresses, team members gain more information, and many risks are either resolved or mitigated, causing these factors to decrease over time.

Comparison Summary:

Start of Project: High Risk, High Uncertainty, High Stakeholder Influence, Low Cost of Changes.

End of Project: Low Risk, Low Uncertainty, Low Stakeholder Influence, High Cost of Changes.

In the PMBOK® Guide, when a stakeholder requests a change—such as adding a new feature—the project manager must follow the established procedures for Integrated Change Control.

Why Choice C is correct:

The " Master " Document: The Project Management Plan is the primary document that defines how the project is executed, monitored, controlled, and closed. It contains several subsidiary plans that provide the specific " guidance " requested here.

Change Management Plan: Contained within the Project Management Plan, this sub-plan describes the formal process for submitting, evaluating, and approving or rejecting project changes.

Scope Management Plan: This sub-plan explains how the project scope will be defined, developed, and managed. It dictates how the team handles new feature requests to prevent scope creep.

Governance: The project management plan tells the stakeholder who has the authority to approve the feature (e.g., the Change Control Board or the Project Sponsor) and what forms or analysis are required.

Analysis of other options:

A and B (Release Plans): Whether for a product or a project, a release plan is a high-level timeline that shows when specific sets of functionality will be delivered to the customer. While it shows what is currently planned, it does not provide the process guidance for how to add something new.

D (Product management plan): This is a broader document focused on the entire lifecycle of a product (from conception to retirement). While relevant for a Product Manager, in the context of a specific project (which is a temporary endeavor to create a product), the " Project Management Plan " is the definitive source for operational guidance during the project life cycle.

Key Concept: The Project Management Institute (PMI) emphasizes that the Project Management Plan (Choice C) is the " playbook " for the project. It ensures that when a stakeholder wants to add a feature, they don ' t just tell a developer to build it; instead, they follow a structured, documented process that assesses the impact on the project ' s time, cost, and quality.

In accordance with the PMBOK® Guide and the Practice Standard for Work Breakdown Structures, the Work Breakdown Structure (WBS) is the specific term used to describe the hierarchical decomposition of the total scope of work to be carried out by the project team.

Deliverable-Oriented: The WBS is organized around the " deliverables " or " outcomes " of the project rather than the individual actions. Each level of the WBS provides a more detailed definition of the project ' s physical or functional components.

Hierarchical Decomposition: This involves breaking down the project into smaller, more manageable components. The top level represents the entire project, while the lowest level is known as the Work Package, which is the point at which cost and duration can be reliably estimated and managed.

The 100% Rule: A key principle of the WBS is that it includes 100% of the work defined by the project scope and captures all deliverables—internal, external, and interim.

Comparison with Other Options:

WBS Directory (A): This is likely a distractor term. The correct related document is the WBS Dictionary, which provides detailed narrative descriptions of the work for each WBS element.

Activity List (B): This is a list of the specific actions or tasks required to complete the work packages. It is an output of the Define Activities process and is task-oriented, not deliverable-oriented.

Project Schedule (D): This is a model that presents linked activities with planned dates, durations, milestones, and resources. It is derived from the WBS but is not the decomposition itself.