PMI Updated CAPM Exam Questions and Answers by alfie-james

According to the PMBOK® Guide, specifically within the Manage Communications process (historically referred to as Report Performance), Status review meetings are a primary tool and technique used to exchange and distribute project performance information.

Core Function: Performance reporting involves collecting and distributing performance information, including status reports, progress measurements, and forecasts. Status review meetings provide a structured forum for the project team to present this data to stakeholders.

Discussion and Feedback: These meetings allow for real-time discussion regarding project health, risks, issues, and work completed during the period. It is a collaborative method to ensure all parties have a consistent understanding of the project ' s " actuals " versus the " baseline. "

Information Shared: During these sessions, the Project Manager typically presents:

Work Performance Reports: Graphs and charts showing progress.

Earned Value Management (EVM): Metrics like CV, SV, CPI, and SPI.

Forecasts: Estimated time and cost to complete (ETC and EAC).

Issues and Risks: High-priority items requiring stakeholder attention.

Comparison with Other Options:

Expert Judgment (A): This is a general technique used to interpret data or assess the technical aspects of the project, but it is not a communication method for reporting performance to others.

Project Management Methodology (B): This refers to the overall framework or set of procedures used by an organization to manage projects. While the methodology might prescribe reporting, it is not a specific communication method itself.

Stakeholder Analysis (C): This is a tool used during Identify Stakeholders and Plan Communications Management to determine who needs what information; it is not the method used to actually deliver the performance reports.

According to the PMBOK® Guide, Free Float (FF) is defined as the amount of time that a schedule activity can be delayed without delaying the early start date of any successor or violating a schedule constraint.

Calculating Free Float: The formula for Free Float is:

$$FF = ES_{successor} - EF_{activity} - 1$$

(Note: The " -1 " is used if using the " Day 1 " start convention; if using " Day 0 " , it is simply $ES - EF$).

Analysis of the Network Diagram (Standard PMI Question Set 259-261):

In the standard diagram for this specific question sequence:

Activity H and Activity G are parallel paths leading into the final Activity I.

The Critical Path usually runs through Activity G (A-B-C-F-G-I), meaning Activity G determines the Early Start (ES) for Activity I.

If Activity I has an Early Start of Day 31, and Activity H finishes on Day 20, then Activity H has 10 days of " Free Float " because it can slip until Day 30 without pushing the start of Activity I.

Free Float vs. Total Float: Unlike Total Float (which is the delay allowed without delaying the project finish date), Free Float is strictly concerned with the immediate successor. In this diagram, since Activity H is the last activity before the final node, its Free Float often equals its Total Float, provided there are no other constraints.

Comparison with other options:

A and B (4 or 5 days): These numbers typically represent the duration of individual activities or the float of a different path (like the D-E path) rather than the specific buffer available for Activity H.

D. 11: This is often a result of a calculation error where the finish day of the activity is subtracted from the start day of the successor without accounting for the inclusive nature of the workday (the " off-by-one " error). In PMI standards, if an activity finishes on the evening of Day 20, and the next starts on the morning of Day 31, there are exactly 10 full days of float (Days 21 through 30).

In accordance with the PMBOK® Guide, Progressive Elaboration is the iterative process of increasing the level of detail in a project management plan as greater amounts of information and more accurate estimates become available.

This concept acknowledges that it is rarely possible to define every detail of a project at its initiation. Instead, the project management plan is developed in broad strokes early on and then refined and made more specific as the project team gains a better understanding of the objectives, deliverables, and constraints.

Relationship to Rolling Wave Planning: Progressive elaboration is the broader concept that encompasses Rolling Wave Planning, where near-term work is planned in detail while future work is planned at a high level.

Purpose: It allows a project management team to manage to a greater level of detail as the project evolves, ensuring the plan remains realistic and aligned with current project realities.

Distinction from Scope Creep: Unlike scope creep (uncontrolled changes), progressive elaboration is a controlled, intentional process of refining the existing authorized scope.

Analysis of Distractors:

A. Continuous improvement: Also known as Kaizen, this refers to an ongoing effort to improve products, services, or processes over time. While it is an iterative mindset, it is not the specific term for refining project plan details.

B. Predictive planning: This refers to a project life cycle (Waterfall) where the scope, time, and cost are determined as early as possible. While predictive projects use progressive elaboration, " predictive planning " is not the name of the iterative refinement process itself.

D. Quality assurance: This is the process of auditing the quality requirements and the results from quality control measurements to ensure that appropriate quality standards and operational definitions are used. It does not relate to the detail level of the management plan.

According to the PMBOK® Guide, the Develop Team process is focused on improving competencies, team member interaction, and the overall team environment to enhance project performance.

Co-location (Tight Matrix): This is a specific tool and technique of the Develop Team process. It involves placing many or all of the most active project team members in the same physical location to enhance their ability to perform as a team, reduce friction, and improve communication.

Training: This is another primary tool and technique for this process. Training includes all activities designed to enhance the competencies of the project team members. It can be formal or informal and is aimed at closing skill gaps to ensure the project goals are met.

Objective: The goal of Develop Team is to create a high-functioning unit. By using co-location and training, the project manager is actively building team synergy and individual capability.

Analysis of other options:

A. Acquire Resources: This process is about outlining and guiding the selection of resources and assigning them to their respective activities. It is the act of getting the people, not improving them.

B. Control Resources: This process is concerned with physical resources (equipment, materials, facilities, and infrastructure) rather than the project team. It ensures that the physical resources assigned to the project are available as planned.

C. Manage Team: This process focuses on tracking team member performance, providing feedback, resolving issues, and managing team changes to optimize project performance. While " Develop Team " builds the team ' s capacity, " Manage Team " focuses on their actual output and behavior during execution.

Per PMI standards, Co-location and Training are foundational techniques used to Develop the Team, leading to improved project results through better collaboration and enhanced skills.