PMI Updated CAPM Exam Questions and Answers by claire

According to the PMBOK® Guide (6th Edition), understanding the distinction between a " metric " and a " measurement " is vital for the Project Quality Management knowledge area.

Quality Metrics: These are established during the Plan Quality Management process. A metric is a specific description of a project or product attribute and how the Control Quality process will measure it. Examples include the number of defects, percentage of tasks completed on time, or reliability requirements. It is the " standard " or " unit " of measurement.

Quality Measurements: These are the actual results obtained during the Control Quality process. They are the outputs of monitoring and recording the results of executing the quality activities. Essentially, the measurement is the " actual data point " captured when comparing the work against the metric.

Why Answer A is correct: It correctly identifies that Metrics are the attributes (the definition of what will be measured) and Measurements are the results generated during the monitoring and control phase of the project (specifically within the Control Quality process).

Analysis of Distractors:

B (Quality metrics are the result... and measurements are product attributes): This is the reverse of the actual definitions. Metrics are planned; measurements are the result of execution.

C (Quality metrics and measurements are the same concept): In PMI terminology, they are distinct. One is the " rule " (metric) and the other is the " reading " (measurement).

D (Quality metrics is the general objective...): While metrics support objectives, this is not the technical definition provided in the PMBOK® Guide. Quality objectives are high-level goals, while metrics are specific, quantifiable descriptions used to verify those goals.

According to the PMBOK® Guide (6th Edition), specifically within the Define Activities process (Project Schedule Management), Decomposition is the primary tool and technique used to divide and subdivide the project scope and project deliverables into smaller, more manageable parts called activities.

While decomposition is also used in the Create WBS process to break down the project into work packages, in the Define Activities process, it goes one step further. It takes those work packages (the lowest level of the WBS) and breaks them down into the specific actions required to produce the deliverable.

Key Characteristics of Decomposition in this context:

Granularity: It transforms " deliverables " (nouns) into " activities " (verbs).

Result: The final output of this technique in this process is the Activity List, which provides a basis for estimating, scheduling, executing, monitoring, and controlling the project work.

Involvement: The project team members who will perform the work usually participate in this decomposition to ensure accuracy.

Analysis of Distractors:

A (Data analysis): This is a broad category of techniques (like alternative analysis) used to evaluate different ways to meet requirements, but it is not the specific mechanical process of breaking down work packages into activities.

B (Leads and lags): These are used during the Develop Schedule process to adjust the timing of activities that have already been identified and sequenced.

C (Precedence diagramming method): This is a technique used in the Sequence Activities process to create a logical schedule network diagram. It determines the relationship between activities, but it is not used to generate the activities from work packages.

According to the PMBOK® Guide, specifically within the Estimate Costs and Estimate Activity Durations processes, Analogous Estimating is a technique used to estimate the duration or cost of an activity or a project using historical data from a similar activity or project.

Basis of Estimation: It uses values such as scope, cost, budget, and duration or measures of scale (such as size, weight, and complexity) from a previous, similar project as the basis for estimating the same parameter or measure for a current project.

When to Use: It is frequently used when there is a limited amount of detailed information about the project (e.g., in the early phases of a project).

Characteristics:

Cost and Time: It is generally less costly and time-consuming than other techniques.

Accuracy: It is generally less accurate than parametric or bottom-up estimating.

Reliability: It is most reliable when the previous projects are similar in fact and not just in appearance, and the project team members preparing the estimates have the needed expertise.

Top-Down Nature: Analogous estimating is a form of expert judgment and is often referred to as a top-down approach because it looks at the project as a whole rather than its individual components.

Comparison with other options:

B. Parametric: This technique uses a statistical relationship between historical data and other variables (e.g., square footage in construction) to calculate an estimate. It is more data-driven than analogous estimating.

C. Bottom-up: This involves estimating the cost or duration of individual work packages or activities and then summarizing (rolling up) these estimates to higher levels. It is the most accurate but also the most time-consuming.

D. Top-down: While analogous estimating is a type of top-down estimation, " Top-down " is a general category. In the context of specific PMI tools and techniques for estimating, Analogous is the formal term used to describe the use of previous similar projects as the primary basis.

According to the PMBOK® Guide, specifically within the Acquire Resources process, Pre-assignment is a tool and technique used when project team members are identified in advance.

Definition: Pre-assignment occurs when physical or team resources for a project are determined before the project starts or before the human resource management plan is completed.

Common Scenarios for Pre-assignment:

Certain people are promised as part of a competitive proposal or bid.

The project is dependent upon the specific expertise of a particular person (as mentioned in the question: " crucial to the task " ).

Staff assignments are defined within the Project Charter itself.

Impact on the Project Manager: When resources are pre-assigned, the project manager does not have to negotiate for them or acquire them through a standard hiring process; however, they must ensure these specific individuals are available when the scheduled activities occur.

Analysis of Other Options:

A. Acquisition: This refers to the process of gaining resources from outside sources (e.g., hiring new employees or subcontracting) when the performing organization lacks the required staff.

B. Negotiation: This involves the project manager working with functional managers or other project teams within the same organization to " borrow " or assign staff to their project. This is used when the resources are not pre-assigned.

C. Virtual team: This is a technique where people with little or no time spent meeting face-to-face work together. While it helps in utilizing staff who are not in the same geographic location, it is a method of organizing the team rather than a method of selecting a specific crucial member in advance.