PMI Updated CAPM Exam Questions and Answers by jensen

According to the PMBOK® Guide, specifically the Project Procurement Management knowledge area, the Plan Procurement Management process is the stage where the project team determines whether to acquire goods and services from outside the organization or to perform the work internally.

Make-or-Buy Analysis: This is a key Tool and Technique of the Plan Procurement Management process. It involves evaluating the costs, risks, and organizational capabilities associated with both options.

Trigger for Decision: In this scenario, the " functional requirement depending on unavailable expertise " is a direct trigger for a make-or-buy analysis. Since the expertise is unavailable internally, the analysis will likely lead to a " buy " decision to mitigate the risk of project failure.

Output: The primary output of this process is the Procurement Management Plan and the Make-or-Buy Decisions document, which outlines the strategy for engaging external vendors to provide the missing expertise.

Why other options are incorrect:

Option B (labeled incorrectly as B/Plan Risk Responses): While choosing to " buy " is a way to transfer risk, the specific formal process for generating a make-or-buy decision is Procurement Management, not Risk Response. Risk Response planning follows the decision to procure.

Option C (Conduct Procurements): This process occurs after the plan is finalized. It involves receiving seller responses, selecting a seller, and awarding a contract. You cannot conduct procurements until you have already made the " buy " decision in the planning phase.

Option D (Plan Risk Management): This process defines how to conduct risk management activities for a project. It does not address specific technical gaps or procurement decisions directly.

According to the PMBOK® Guide (6th and 7th Editions) and the Agile Practice Guide, the choice of a project life cycle depends on the level of certainty regarding requirements and the stability of the environment.

In this scenario, we have a mix of known and unknown variables:

The Known: The software itself is already used in domestic branches, suggesting a degree of " predictability " for the core implementation.

The Unknown: The foreign market introduces significant uncertainty, with " multiple changes expected " due to local regulations, language, or market-specific needs.

A Hybrid life cycle is the most appropriate because it combines elements of both Predictive (Waterfall) and Adaptive (Agile) approaches:

The predictive elements can be used for the standard software deployment steps that the company already understands well.

The adaptive (agile) elements can be used to handle the " multiple changes " and high uncertainty associated with the foreign market through iterative feedback and incremental delivery.

Analysis of Distractors:

A and B (Predictive/Waterfall): These are synonymous in this context. They are used when requirements are well-defined and unlikely to change. Given the statement that " multiple changes are expected, " a rigid predictive approach would likely lead to project failure or significant rework.

D (Product life cycle): This is not a project life cycle. The product life cycle encompasses the entire life of a product from conception through retirement (including multiple projects and operational phases). It is too broad a concept for choosing how to manage a specific implementation project.

According to the PMBOK® Guide, project management involves iterative planning as more information becomes available. This specific iterative technique is formally known as rolling wave planning.

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 far in the future is planned at a higher level.

Mechanism: It is a functional application of the " progressive detailing " mentioned in the question. As the project progresses and more risks and requirements are identified, the " wave " moves forward, and the high-level plans are decomposed into detailed work packages.

Context: This is particularly useful in projects where the full scope is not entirely clear at the start (such as RandD or software development) or in high-uncertainty environments.

A. Expert judgment: This is a tool and technique used in almost every project management process. While experts may help with detailing a plan, " expert judgment " refers to the specialized knowledge or training used to make a decision, not the process of progressive detailing itself.

C. Work performance information: This is an output of various controlling processes (like Control Schedule or Control Costs). it is the processed data used to make decisions, but it is not a planning technique.

D. Specification: A specification is a document that describes the requirements, design, or behavior of a product or service. While a specification can be detailed progressively, it is a document/input, not the act of detailing the overall management plan.

Rolling wave planning is the primary technique used to achieve Progressive Elaboration. In the PMI framework, this acknowledges that as a project evolves, the project management team gains a better understanding of the objectives and deliverables, allowing them to manage the project with greater " granularity " over time.

According to the PMBOK® Guide, specifically within the Plan Quality Management process, the Cost of Quality (COQ) is a critical tool used to ensure that the project deliverables meet the required standards. COQ is divided into two main categories: Cost of Conformance and Cost of Nonconformance.

Internal failure costs fall under the category of Cost of Nonconformance. These are costs incurred because the product or service does not meet quality requirements, but the deficiency is discovered before the product is delivered to the customer.

Rework: The action taken to bring a defective or nonconforming component into compliance with requirements or specifications.

Scrap: The cost of work or materials that cannot be repaired or used and must be discarded.

Timing: Because these failures are found internally (by the project team or quality department), they are generally less expensive than external failures, but they still represent a waste of project resources and time.

A. Inspections: These are Appraisal Costs (part of the Cost of Conformance). These are costs incurred to examine the work and ensure it meets requirements before a failure occurs.

B. Equipment and Training: These are Prevention Costs (part of the Cost of Conformance). These are proactive investments made to keep errors from happening in the first place.

C. Lost Business: This is an External Failure Cost. These costs occur when the product has already reached the customer and fails. Lost business, warranty claims, and damage to reputation are the most expensive types of quality costs.