PMI Updated CAPM Exam Questions and Answers by arjun

According to the PMBOK® Guide, specifically within the Estimate Activity Durations and Estimate Costs processes, Parametric Estimating is an estimating technique in which an algorithm is used to calculate cost or duration based on historical data and project parameters.

Accuracy Levels: The accuracy of a parametric estimate is highly dependent on the sophistication of the model and the underlying data. If the historical data is accurate and the model is scalable (e.g., cost per square foot for a building or lines of code for software), it can produce higher levels of accuracy than other top-down methods.

Mechanism: It uses a statistical relationship between historical data and other variables (such as square footage in construction or lines of code in software development) to calculate an estimate for activity parameters, such as cost, budget, and duration.

Comparison:

Analogous Estimating (Choice D): Generally the least accurate as it relies on a " top-down " comparison to a previous similar project.

Three-Point Estimating (Choice B): Improves accuracy by considering uncertainty (Optimistic, Pessimistic, and Most Likely), but is still subjective.

Bottom-up Estimating (Choice A): While often considered the most accurate overall because it aggregates detailed work, the specific question asks which technique ' s accuracy depends on the sophistication and data built into a model, which is the defining characteristic of Parametric Estimating.

According to the PMBOK® Guide, the core purpose of Project Quality Management is to ensure that the project includes all the processes needed to ensure that the project meets the needs for which it was undertaken. This specifically involves fulfilling both the quality and grade requirements of the project.

Quality vs. Grade: This is a fundamental PMI concept.

Quality is the degree to which a set of inherent characteristics fulfills requirements (i.e., does it work as intended?).

Grade is a category assigned to deliverables having the same functional use but different technical characteristics (e.g., a " high-grade " software with many features vs. a " low-grade " software with basic features).

While low quality is always a problem, low grade may be acceptable. Project Quality Management ensures both are managed to meet the project ' s objectives.

Customer Satisfaction: Quality management ensures that the project requirements, including product requirements, are defined, appraised, and met. It focuses on the management of the project and the deliverables of the project to satisfy stakeholder expectations.

Continuous Improvement: It also involves the implementation of continuous process improvement activities as conducted on behalf of the performing organization.

Why other options are incorrect:

Option A: To meet customer requirements by overworking the team: This is contrary to PMI’s ethical standards and the Project Resource Management knowledge area. Overworking a team leads to burnout and a higher " Cost of Quality " through increased errors and attrition.

Option B: To fulfill project schedule objectives by rushing planned inspections: Rushing inspections (Appraisal activities) increases the risk of undetected defects. Quality Management emphasizes Prevention over Inspection, not compromising quality to meet a schedule.

Option D: To exceed customer expectations: While this sounds positive, in the PMI framework, " exceeding expectations " is often referred to as Gold Plating. Gold plating (adding extra features not in the scope) is considered a waste of resources and can introduce new risks and costs to the project without formal approval.

According to the PMBOK® Guide and the Agile Practice Guide, risk management in agile/adaptive environments is not a one-time or infrequent event; it is integrated into the heart of the iterative cycle.

Continuous Risk Management: In adaptive environments, risk is identified, analyzed, and managed during each iteration. Because agile projects deal with high variability and uncertainty, the team reassesses the risk profile frequently—often during iteration planning and daily stand-ups.

Small Batches and Feedback: By breaking the work into small increments (iterations), the team can uncover risks early. Each iteration provides a " fail-fast " opportunity, where technical or requirements-related risks are exposed through the delivery of a working product increment.

Risk-Adjusted Backlog: The project manager and the product owner work together to prioritize the backlog. High-risk items (often called " Risk-Reducers " ) are frequently pulled into early iterations to prove concepts or tackle technical challenges before significant resources are spent.

Why other options are incorrect:

Option A: Adding more risk categories is a matter of tailoring the Risk Management Plan, but it doesn ' t address the specific behavioral or procedural change required by an agile environment.

Option C: While you might refine a probability and impact matrix, simply adding " new values " does not account for the rapid, iterative nature of an adaptive project.

Option D: Increasing reserves is a way to handle financial or schedule impact (Active Acceptance), but it is not the primary management consideration for agile. Agile projects actually aim to reduce the need for large, unknown reserves by providing transparency and frequent course correction.

According to the PMBOK® Guide, specifically within the Plan Procurement Management process, different contract types are used depending on the nature of the project and the level of risk the buyer or seller is willing to assume.

The Firm-Fixed-Price Contract (FFP) is the most common type of contract used by most buying organizations.

Fixed Price at Outset: In an FFP contract, the price for goods or services is set at the beginning and is not subject to change unless the scope of work changes (usually via a formal change order).

Risk Allocation: This contract type places the greatest amount of risk on the seller. If the seller ' s costs increase during the performance of the contract, the buyer is not obligated to pay more. The seller is legally obligated to complete the work at the agreed-upon price.

Administrative Effort: For the buyer, FFP contracts require the least amount of auditing and oversight compared to cost-reimbursable contracts, as the primary focus is on the quality and timeliness of the deliverables rather than the seller ' s internal costs.

Suitability: This is best used when the product or service is well-defined and the specifications are unlikely to change significantly.

Analysis of other choices:

Choice A (Fixed Price with Economic Price Adjustments - FP-EPA): This is a fixed-price contract that allows for pre-defined adjustments to the contract price due to changed conditions, such as inflation or cost increases for specific commodities. It is used for multi-year projects but is not the " most common " general-purpose contract.

Choice B (Cost-Reimbursable - CR): In this type, the buyer pays the seller for actual costs incurred plus a fee (profit). This places the risk on the buyer, as the final cost is not fixed at the outset.

Choice D (Fixed-Price-Incentive-Fee - FPIF): This allows for some flexibility by giving the buyer and seller the ability to share in cost savings or overruns based on a pre-determined formula. While it has a price ceiling, it is more complex than a standard FFP.