PMI Updated CAPM Exam Questions and Answers by mikayla

According to the PMBOK® Guide, the Identify Risks process is where the Risk Register is initially created. To identify risks effectively, the project manager must look at various components of the project management plan and other project artifacts.

Risk Management Plan: This is a vital input because it provides the " how-to " for risk activities. It defines the roles and responsibilities, the budget for risk activities, and the categories of risk (often found in the Risk Breakdown Structure or RBS).

Activity Cost Estimates: These are reviewed to identify risks associated with the financial aspects of the project. If an estimate is particularly aggressive or based on volatile market prices, it represents a potential risk that needs to be captured in the register.

Project Documents: This is a broad category that includes the requirements documentation, schedule, and other logs. These documents provide the specific details of what the project is trying to achieve, which allows the team to identify specific threats or opportunities related to those goals.

Other Key Inputs:

Scope Baseline: Used to identify potential risks to the project ' s boundaries.

Schedule Management Plan: Used to identify risks related to timelines and milestones.

Analysis of Other Options:

A. Risk register updates: This is an output of many risk-related processes (like Perform Qualitative Risk Analysis or Plan Risk Responses), not an input to the creation of the initial register.

B. Communication management plan: While communication is important, it is not listed as a primary input specifically used to identify technical or project risks for the register.

D. Project scope statement / Scope baseline: While these are valid inputs, Organizational Process Assets (OPAs) are general environmental factors or historical templates, and this grouping is less comprehensive than option C in terms of the specific project data needed for risk identification.

According to the PMBOK® Guide, Work Performance Data consists of the raw observations and measurements identified during activities being performed to carry out the project work. In the context of Project Cost Management, this data is a primary input to the Control Costs process.

Relationship between Data and Process: Work performance data includes information about project progress, such as which deliverables have started, their progress, and which costs have been incurred (actual costs) versus the work performed (earned value).

The Control Costs Process: This is the process of monitoring the status of the project to update the project costs and managing changes to the cost baseline.

Transformation of Data: During the Control Costs process, this raw Work Performance Data is analyzed and compared against the cost baseline to produce Work Performance Information (such as $CV$, $SV$, $CPI$, and $SPI$). This information communicates how the project is actually performing financially compared to the plan.

Inputs to Control Costs:

Project Management Plan (Cost Baseline, Cost Management Plan).

Project funding requirements.

Work Performance Data.

Organizational Process Assets.

Analysis of Other Options:

A. Plan Cost Management: This is a planning process used to define how the project costs will be estimated, budgeted, managed, monitored, and controlled. It uses the Project Charter and Project Management Plan as inputs, not performance data from execution.

B. Estimate Costs: This process involves developing an approximation of the monetary resources needed to complete project work. It relies on the scope baseline, project schedule, and human resource requirements.

C. Determine Budget: This process aggregates the estimated costs of individual activities or work packages to establish an authorized cost baseline. It occurs during planning, before work performance data is generated.

In accordance with the PMBOK® Guide (Project Schedule Management), specifically within the Define Activities process, Rolling Wave Planning is a form of progressive elaboration where the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level.

Function: This technique allows for work to exist at various levels of detail depending on its position in the project life cycle. During early strategic planning, when information is less defined, work packages may be decomposed only to a certain level. As the project progresses and more information becomes available, those high-level components are decomposed into detailed activities.

Application: It is particularly useful in projects with high levels of uncertainty or those using an adaptive (agile) or hybrid life cycle, where the final product is not fully defined at the start.

Relationship to WBS: While the WBS provides the structural framework, Rolling Wave Planning is the specific scheduling technique used to manage the timing of that detail ' s emergence.

Analysis of Distractors:

A. Historical relationships: This is a tool/technique used in Estimate Activity Durations or Estimate Costs (Parametric Estimating) to predict future results based on past data. It does not dictate the level of detail in the plan based on the life cycle.

B. Dependency determination: This is used in the Sequence Activities process to define the relationship between tasks (e.g., Mandatory, Discretionary, External, or Internal). It determines the order of work, not the level of detail.

C. Bottom-up estimating: This is a technique for estimating duration or cost by aggregating the estimates of lower-level components. It requires a high level of detail to be present before the estimate can be made, rather than allowing for various levels of detail.

According to the PMBOK® Guide and the Standard for Project Management, the determination of project viability occurs during the pre-initiation phase. This evaluation is essential to justify the investment of organizational resources.

Why Choice C is correct: Cost-benefit analysis (CBA) is a financial analysis tool used to determine the economic feasibility of a project. It compares the total expected costs of the project against the total expected benefits (tangible and intangible).

Go/No-Go Decision: If the benefits significantly outweigh the costs (yielding a positive Net Present Value or a favorable Benefit-Cost Ratio), the project is deemed viable.

Business Case: This analysis is a primary component of the Business Case, the document used by sponsors to authorize the project charter.

Objective Comparison: It allows organizations to compare multiple potential projects and select the one that provides the highest value for the investment.

Analysis of other options:

A (Cost of quality): COQ refers to the total cost of conformance (prevention and appraisal) and nonconformance (internal and external failures). This is a tool used during the Plan Quality Management and Control Quality processes after a project has already started; it is not a project-level viability tool.

B (Lessons learned): While looking at past projects can inform the planning of a new one, lessons learned provide historical context rather than a direct financial or strategic justification for a specific " go/no-go " decision on a current business case.

D (Benchmarking): Benchmarking involves comparing your organization ' s practices or products against those of leaders in the industry. While it might highlight a need for a project, it doesn ' t analyze whether a specific project is financially viable for your specific organization.

Key Concept: The Project Management Institute (PMI) emphasizes that project managers must understand the business value of their projects. The Cost-benefit analysis (Choice C) is the fundamental economic tool that translates a project idea into a measurable business decision, ensuring that only projects that contribute to the organization ' s bottom line or strategic goals are initiated.