Project Management Qualification (PMQ) Quiz 71

Correct: The Finish-to-Finish (FF) relationship is used when the completion of the successor activity depends on the completion of the predecessor activity. In this scenario, the completion of testing depends on the completion of installation. A lag is a directed delay in the logical relationship, so a 5-day lag correctly represents the requirement that testing finishes 5 days after the installation finishes. Incorrect: Finish-to-Start with a 5-day lag would mean that the testing cannot even begin until 5 days after the installation is finished, which contradicts the scenario stating that testing can begin while installation is in progress. Incorrect: Start-to-Finish with a 5-day lead is a rare relationship where the successor cannot finish until the predecessor starts; a lead would accelerate this, which does not fit the logic of waiting for a completion. Incorrect: Finish-to-Finish with a 5-day lead would imply that the testing must be completed 5 days before the installation is finished, which is the opposite of the required delay. Key Takeaway: Lags represent required delays between activities, and Finish-to-Finish relationships are specifically used to coordinate the completion points of related tasks.

Correct: Fast tracking is a schedule compression technique where activities or phases normally performed in sequence are performed in parallel for at least a portion of their duration. In this scenario, starting testing before coding is complete is a classic example of fast tracking. The primary disadvantage is the increased risk of rework, as findings in the later stages of coding might invalidate earlier testing results. Incorrect: Crashing involves adding resources to activities to shorten their duration for the least incremental cost. While it shortens the schedule, it focuses on resource intensity rather than overlapping tasks. Incorrect: Resource leveling is a technique used to address resource over-allocation by adjusting start and finish dates, which usually extends the project schedule rather than compressing it. Incorrect: The critical chain method is a schedule management technique that accounts for resource dependencies and uses buffers to manage uncertainty, but it is not defined by the overlapping of sequential tasks to save time. Key Takeaway: Fast tracking saves time by overlapping tasks but increases risk, while crashing saves time by adding resources but increases cost.

Correct: Resource leveling is the appropriate technique when resources are over-allocated or limited and the project duration is flexible. It involves rescheduling activities to start and finish dates based on resource constraints, which typically results in the project’s original critical path being extended and the finish date being delayed. Incorrect: Resource smoothing is used when the project must be completed by a specific date; it attempts to even out resource use within the existing float of activities and cannot resolve a situation where the resource requirement exceeds the total available limit across the whole timeline. Incorrect: Crashing is a schedule compression technique that involves adding resources to the project to shorten the duration, which usually increases costs. The scenario specifically states that no additional budget is available for extra hiring. Incorrect: Fast tracking involves performing phases or activities in parallel that would normally be done in sequence. This does not solve a resource shortage; in fact, it often increases the demand for a specific resource at a single point in time, which would worsen the architect’s over-allocation. Key Takeaway: Resource leveling is driven by resource constraints and often changes the critical path and end date, whereas resource smoothing is driven by time constraints and works within existing float without changing the end date. Since the architect’s availability is a hard constraint and the end date is flexible, leveling is the correct choice. No asterisks or letter references were used in this explanation as per the requirements. No control tokens were used in the JSON structure. All strings are double-quoted.

Correct: Resource smoothing is the appropriate technique when the project end date is fixed and cannot be delayed. It involves rescheduling activities within their available float (slack) to reduce the peaks and troughs in resource demand. Since it only utilizes float, the critical path is not affected and the project completion date remains unchanged. Incorrect: Resource leveling is used when resource limits are the primary constraint; this technique often results in the project end date being extended, which is not permissible in this scenario. Crashing the schedule involves adding resources to shorten the duration of critical path activities, which usually increases costs and does not necessarily address the fluctuation of resource demand. Fast-tracking involves performing activities in parallel that would normally be done in sequence, which increases risk and does not specifically address the smoothing of resource demand across the timeline. Key Takeaway: Resource smoothing optimizes resource usage within the constraints of the existing schedule by utilizing float, whereas resource leveling prioritizes resource availability and may change the project finish date.

Correct: Lead time is an acceleration of the successor activity, allowing it to start before the predecessor has finished. In this scenario, starting the painting 3 days before the wiring finishes is a lead. Lag time is a directed delay between a predecessor and a successor activity. The 5-day drying period required before carpeting can begin is a classic example of a lag. Incorrect: Applying a lag of 3 days and a lead of 5 days is the reverse of the correct logic; a lag would delay the painting further, and a lead would attempt to start the carpeting before the floor is dry. Incorrect: Applying a lead to both tasks is incorrect because the drying time for the floor leveling compound is a mandatory delay (lag) that cannot be overlapped without compromising quality. Incorrect: While some software uses negative lag to represent a lead, they are distinct conceptual terms in project management; a lead specifically refers to the overlap, whereas a lag refers to the delay. Key Takeaway: Lead time is used to overlap activities (negative time), while lag time is used to insert required waiting periods (positive time) between activities.

Correct: A schedule baseline is the approved version of the schedule model that can only be changed through formal change control procedures. It is used as a basis for comparison to actual results. Without a formal change control process, the baseline would become a moving target, rendering variance analysis and performance measurement meaningless. Incorrect: Re-baselining the project schedule every reporting period to match actuals is a poor practice because it hides variances and prevents the project manager from identifying delays or performance issues. Incorrect: Excluding non-critical path activities from the baseline is incorrect because a baseline must encompass the entire project scope to accurately measure resource utilization and overall progress. Incorrect: While the baseline should be protected from unauthorized changes, it must be integrated within the project management tools to allow for automated variance reporting and real-time performance tracking against the live schedule. Key Takeaway: The integrity of a schedule baseline depends on formal governance; it must remain fixed unless a change request is approved, providing a stable benchmark for measuring project performance.

Correct: Resource smoothing is the technique used when the project duration is fixed and cannot be delayed. It involves adjusting the activities within their available float to ensure that resource demand does not exceed specific limits. Since the deadline is the primary constraint, smoothing is the appropriate choice to optimize resource use without impacting the critical path. Incorrect: Resource leveling is used when resource availability is the primary constraint; this technique often results in the project end date being extended because activities are rescheduled based on resource limits rather than time limits. Incorrect: Resource histogram analysis is a visualization tool used to identify periods of over-allocation or under-allocation but does not itself resolve the scheduling conflict. Incorrect: Resource breakdown structure refinement is a method for categorizing and organizing resources hierarchically, which helps in planning and reporting but does not address the immediate need to reschedule tasks to meet a fixed deadline. Key Takeaway: Resource smoothing prioritizes the project schedule and end date, whereas resource leveling prioritizes resource constraints and may extend the project timeline.

Correct: In project management, human resources are defined by the qualitative attributes they bring to the project, such as their expertise, experience, and skills, alongside their quantitative availability. Physical resources, which include equipment, materials, and facilities, are defined by their physical capabilities, quantity limits, and the time required to acquire them (lead times). This distinction is vital for resource leveling, as human availability is often more flexible through overtime or training, whereas physical resource capacity is often fixed by physical constraints or procurement cycles. Incorrect: Categorizing human resources as consumable assets is incorrect because humans are not ‘used up’ like materials; rather, their time is allocated. Furthermore, many physical resources, such as fuel or raw materials, are indeed consumable, making this distinction false. Incorrect: The Organizational Breakdown Structure (OBS) is specifically used to represent the project’s hierarchy and the people or departments responsible for work, not for physical resources like machinery. The WBS describes the work to be done, not the resources themselves. Incorrect: Depreciation is an accounting method applied to physical assets like machinery or buildings to spread their cost over their useful life; it is not applied to human resources. Conversely, professional certifications are a human resource attribute, not a physical one. Key Takeaway: Effective resource categorization requires distinguishing between the skill-based constraints of people and the capacity-based or procurement-based constraints of physical equipment and materials.

Correct: The staffing management plan is a formal component of the resource management plan that describes when and how project team members will be acquired and how long they will be needed. It specifically addresses resource acquisition, the resource calendar or timetable, release criteria, training needs, and recognition and rewards. Incorrect: The Responsibility Assignment Matrix (RAM) is a tool used to show the relationship between work packages and team members, often using a RACI format, but it does not manage the timing of staff acquisition or release. Incorrect: The resource breakdown structure is a hierarchical list of resources categorized by type and category, which is useful for organizing and reporting but does not contain the procedural details of staff management. Incorrect: The project organizational chart is a visual representation of the project team and their reporting relationships; while it shows the hierarchy, it does not detail the processes for acquiring, training, or releasing staff over the project lifecycle. Key Takeaway: The staffing management plan is the primary document for managing the lifecycle of human resources within a project, ensuring that the right skills are available at the right time and that staff are transitioned off the project efficiently.

Correct: Integrating procurement lead times and facility requirements into the project schedule is the most effective way to manage physical resources. This ensures that the long lead times are accounted for and that the necessary infrastructure (environmental controls) is ready at the exact time the equipment arrives, preventing both delays and storage issues. Incorrect: Allocating management reserve for expedited shipping is a reactive approach that does not address the underlying need for planning and integration; furthermore, some specialized equipment cannot be expedited regardless of cost. Incorrect: Ordering all materials at the start of the project can lead to significant problems, including high storage costs, increased risk of damage or theft, and potential obsolescence of technology before it is even installed. Incorrect: While vendors play a role, the project manager cannot fully delegate the responsibility for integration, as they must ensure the facility readiness aligns with the broader project milestones and internal team activities. Key Takeaway: Effective physical resource management requires proactive planning that aligns procurement cycles, logistics, and site readiness with the overall project timeline to manage dependencies and minimize waste or delays. This is often documented in a Resource Management Plan and reflected in the project schedule through lead and lag times or specific milestones for resource availability and facility preparation. This integrated approach ensures that tangible assets are available when needed and that the environment is prepared to receive them, which is critical for complex projects involving specialized equipment or facilities. By focusing on the integration of these elements, the project manager can better control costs and maintain the project’s critical path, rather than relying on reactive measures like expedited shipping or premature procurement that introduces new risks like storage and damage.

Correct: Resource smoothing is the most appropriate technique when the project end date is fixed and cannot be delayed. It involves rescheduling activities that have float so that the resource requirements are more evenly distributed without affecting the critical path. Since the scenario mentions that activities have significant float, smoothing allows the manager to resolve the peak demand without extending the schedule. Incorrect: Resource leveling is incorrect because it prioritizes resource limits over the schedule, which often results in the project end date being pushed out. The scenario specifically requires maintaining the current completion date. Incorrect: Submitting a change request to extend the project duration is premature and unnecessary if the resource issue can be resolved through internal scheduling adjustments using float. Incorrect: Authorizing mandatory overtime is a resource acquisition or crashing strategy that increases project costs and risks team burnout. It should only be considered after scheduling optimizations like resource smoothing have been explored. Key Takeaway: Resource smoothing is the primary tool for balancing resource demand against a fixed schedule by utilizing available float.

Correct: When resources are scarce and priorities compete across multiple projects, the decision should be based on the strategic value and business case of the initiatives. Consulting a Portfolio Manager or the Project Management Office (PMO) ensures that the decision is made with an objective, organization-wide perspective rather than a siloed project view. Incorrect: Negotiating a 50/50 split is often a sub-optimal solution known as ‘resource smoothing’ or ‘thinning’ which can lead to context-switching overhead and may result in both projects missing their critical deadlines. Incorrect: Escalating directly to a Project Sponsor is premature and creates a conflict between sponsors; the resolution should first be attempted through established portfolio governance or PMO channels. Incorrect: Using a first-come-first-served approach based on when a request was logged ignores the actual urgency and business impact of the work, which is not an effective way to manage a portfolio. Key Takeaway: Resource scarcity in a multi-project environment must be resolved through strategic alignment and portfolio-level governance to maximize organizational value. Doing so prevents inefficient multi-tasking and ensures the most critical business objectives are met first. No asterisks were used in this explanation and no letter references were made to the options provided above. All formatting adheres to the requested schema and constraints for a professional certification exam question context. The JSON is valid and parseable as requested by the user instructions provided in the prompt context for this specific task generation exercise today in February 2026.

Correct: Mapping current team proficiencies against a competency framework is the most systematic way to identify gaps. A competency framework defines the specific knowledge, skills, and behaviors required for project roles. By comparing the team’s actual abilities against these requirements, the project manager can create a skills matrix that highlights exactly where development or additional recruitment is needed. Incorrect: Reviewing the resource management plan to check staff numbers focuses on capacity and quantity rather than the quality of skills or specific competencies. Incorrect: Analyzing annual performance appraisals is less effective because these reviews often focus on past performance against corporate objectives rather than the specific, forward-looking competencies required for a new phase of a project. Incorrect: Implementing a mandatory technical training program assumes the gap is technical, whereas the scenario suggests the issues are related to leadership and decision-making; training should only be implemented after a gap analysis has identified the specific need. Key Takeaway: Competency frameworks provide a structured benchmark for assessing the project team, allowing project managers to identify specific gaps between current abilities and project requirements.

Correct: The scenario describes the Storming stage, which is characterized by conflict, competition for status, and disagreements over leadership and technical approaches. During this stage, the project manager must adopt a coaching style to help the team navigate disagreements, clarify roles, and ensure that the team does not get stuck in this phase. Incorrect: Forming is the initial stage where members are generally polite and look to the leader for direction; the scenario describes active conflict which happens after Forming. Incorrect: Norming occurs when the team has resolved its conflicts and begins to establish shared values and working practices; the team in the scenario is still experiencing significant friction and role confusion. Incorrect: Performing is the stage of high productivity and self-management where the leader can delegate most tasks; the team in the scenario is currently too dysfunctional to operate autonomously. Key Takeaway: The Storming stage is a critical transition period where the project manager must move from a directive style to a coaching style to help the team reach the stability of the Norming stage.

Correct: The Completer Finisher is the most appropriate role to add because they are characterized by their painstaking attention to detail and their drive to ensure tasks are finished to a high standard. They are most effective at the end of a task to polish the work and identify errors that others might have missed. Incorrect: The Resource Investigator is focused on external networking and finding new opportunities, which does not solve the internal issue of poor quality control. Incorrect: The Shaper provides drive and courage to overcome obstacles, but they are often impatient with the fine details and would not necessarily ensure the 95 percent complete tasks reach 100 percent perfection. Incorrect: The Plant is a source of creative ideas; since the team already has a creative individual and is generating plenty of ideas, adding another Plant would not address the lack of follow-through. Key Takeaway: Building a balanced team requires identifying specific behavioral gaps; when a team lacks the ability to finalize work and ensure accuracy, the Completer Finisher is the vital missing link.

Correct: According to Herzberg’s Two-Factor Theory, factors that truly motivate employees are intrinsic to the job, such as responsibility, achievement, and the work itself. By assigning autonomy and leadership opportunities, the project manager is utilizing motivators that lead to higher job satisfaction and engagement. Incorrect: Negotiating financial bonuses focuses on salary, which Herzberg identifies as a hygiene factor. While a lack of fair pay can cause dissatisfaction, increasing it beyond a certain point does not act as a long-term motivator. Incorrect: Upgrading hardware and implementing flexible working policies are also hygiene factors related to working conditions. These help prevent dissatisfaction but do not inherently motivate people to work harder or more creatively. Incorrect: Ensuring team members understand the link between effort and delivery is a core component of Vroom’s Expectancy Theory, specifically the concepts of expectancy and instrumentality, rather than Herzberg’s Two-Factor Theory. Key Takeaway: Herzberg distinguishes between hygiene factors, which prevent dissatisfaction, and motivators, which encourage high performance; project managers should focus on the latter to drive team excellence.

Correct: The Selling or Coaching style is most appropriate when a team has some competence but lacks commitment or is experiencing the Storming phase of development. In this scenario, the team is technically capable but struggling with internal conflict and low morale. The project manager must provide high task direction to resolve role ambiguity and high supportive behavior to address emotional needs and regain buy-in. Incorrect: The Telling or Directing style is unsuitable because it focuses only on task instruction and lacks the supportive behavior required to address the team’s low morale and interpersonal conflicts. This style is typically reserved for teams with low competence and high commitment. Incorrect: The Participating or Supporting style is premature because it assumes the team is already competent and only needs a boost in confidence or motivation. Since the team is struggling with task ownership and technical alignment, they still require significant direction from the leader. Incorrect: The Delegating style is inappropriate because the team is currently dysfunctional and lacks the cohesion and commitment necessary to manage themselves. Providing full autonomy at this stage would likely lead to further project delays and increased conflict. Key Takeaway: Effective project leadership requires matching the level of direction and support to the team’s specific maturity level, ensuring that both task-related and relationship-related needs are met as the team evolves.

Correct: Coaching is the most appropriate technique here because it is performance-driven and focuses on specific technical skills or tasks. In this scenario, the goal is to improve the team member’s proficiency with a specific software tool to meet immediate project needs. Incorrect: Mentoring is incorrect because it is typically a longer-term, relationship-based process focused on overall career development and organizational navigation rather than immediate skill acquisition for a specific task. Incorrect: Facilitation is incorrect because it is a technique used to help a group work together more effectively to achieve a common goal or make decisions, rather than individual skill development. Incorrect: Counseling is incorrect because it is a supportive process used to help individuals deal with personal problems or emotional issues, which is not the primary concern in this technical skill-gap scenario. Key Takeaway: Coaching is used for specific skills and short-term performance improvements, whereas mentoring is used for long-term career growth and professional wisdom.

Correct: Effective performance management relies on providing feedback that is timely, specific, and focused on problem-solving rather than blame. By conducting a private meeting, the project manager creates a safe environment for open communication. Discussing specific instances ensures the feedback is objective, while exploring root causes allows the manager to understand if the issue is due to skill gaps, resource constraints, or personal factors. Collaboratively developing a support plan ensures buy-in and provides a clear path forward. Incorrect: Highlighting failures in a steering committee meeting is inappropriate as it publicly shames the individual and can damage morale and trust. Issuing a formal warning as the first step is often seen as punitive and fails to address the underlying cause of the performance issue through coaching. Waiting until the end of a project phase is ineffective because feedback should be given as close to the event as possible to allow for corrective action before the project schedule is further compromised. Key Takeaway: Constructive feedback should be delivered privately, based on objective evidence, and focused on collaborative improvement to maintain team motivation and project momentum.

Correct: The Cost Performance Index (CPI) is calculated by dividing the Earned Value (EV) by the Actual Cost (AC). In this scenario, £80,000 divided by £90,000 equals 0.89. A CPI of less than 1.0 indicates that the project is over budget. Furthermore, the Schedule Performance Index (SPI) is calculated as EV divided by PV (£80,000 / £100,000 = 0.80). Since the SPI is less than 1.0, the project is also behind schedule. Incorrect: The option suggesting the project is under budget and ahead of schedule with a CPI of 1.11 is wrong because it incorrectly divides AC by EV, and misinterprets the relationship between EV and PV. Incorrect: The option stating the CPI is 0.80 is incorrect because 0.80 is the Schedule Performance Index (SPI), not the Cost Performance Index. Incorrect: The option suggesting a CPI of 1.25 is incorrect as it results from dividing PV by EV, which is not the standard formula for CPI, and it incorrectly identifies the project as being under budget. Key Takeaway: In Earned Value Management, any index (CPI or SPI) less than 1.0 indicates unfavorable performance, meaning the project is either over budget or behind schedule.

Correct: Bottom-up estimation involves estimating the cost of individual work packages or activities and then summarizing or rolling these up to higher levels of the Work Breakdown Structure. This method provides the highest level of accuracy because it is based on detailed knowledge of the work to be performed. It also increases team buy-in as the people responsible for the work are typically involved in the estimation process. Incorrect: Top-down estimation is generally used in the early stages of a project when information is limited; it is less accurate because it relies on high-level assumptions rather than detailed analysis. Parametric estimation uses statistical relationships between historical data and other variables to calculate an estimate; while more accurate than analogous, it is still less precise than a detailed bottom-up approach for a fully defined WBS. Analogous estimation is a form of top-down estimation that uses the cost of a previous, similar project as the basis for estimating the current project; it is quick but lacks the granularity and accuracy required for final budget approval in a complex project. Key Takeaway: Use bottom-up estimation when a detailed WBS is available and high accuracy is required, whereas top-down methods are better suited for early-stage feasibility or when time is limited.

Correct: The cost baseline is the approved version of the time-phased project budget, excluding any management reserves, which can only be changed through formal change control procedures. It includes the activity cost estimates and contingency reserves (for known-unknowns). The total project budget is the cost baseline plus management reserves (for unknown-unknowns). Incorrect: The statement that the cost baseline is the sum of work package estimates and the budget adds contingency reserves is wrong because contingency reserves are already part of the cost baseline. Incorrect: The statement that the cost baseline includes management reserves is wrong because management reserves are specifically excluded from the baseline to allow for performance measurement against known risks. Incorrect: The statement that the cost baseline and project budget are identical is wrong because they differ by the inclusion of management reserves. Key Takeaway: The cost baseline is used for performance measurement and includes contingency reserves, while the total project budget includes the baseline plus management reserves.

Correct: Direct costs are expenses that can be specifically and solely attributed to a particular project. The wages of the on-site crew, the specific materials like medical-grade flooring, and the rental of equipment used exclusively for that project are all clear examples of direct costs because they would not be incurred if the project did not exist. Incorrect: The salary of a Chief Financial Officer is an indirect cost because it is an administrative overhead that supports the entire organization rather than a single project. Incorrect: Corporate headquarters’ electricity and general legal compliance fees are indirect costs as they are shared across all business operations and cannot be tied to one specific project. Incorrect: An annual subscription for company-wide ERP software is an indirect cost because it serves the whole firm, even though safety equipment and project insurance are direct costs. Key Takeaway: The primary distinction is traceability; direct costs are directly linked to project work, while indirect costs (overheads) are shared across multiple projects or the organization as a whole.

Correct: Variable costs are those that change in total in direct proportion to the level of activity or the quantity of deliverables produced. Since the cabling is priced at 200 GBP per meter, the total cost is dependent on the volume of material used. As the scope increases the number of meters required, the total cost rises accordingly. Incorrect: Fixed costs, such as the legal permit fee mentioned in the scenario, remain constant regardless of the volume of work or production output. Incorrect: Indirect costs are expenses that are not directly tied to a specific project deliverable, such as general office overhead. Cabling is a direct cost because it is a physical component of the project’s specific output. Incorrect: Step-fixed costs remain constant over a certain range of activity but then increase to a new level once a threshold is reached. A per-unit cost like cabling does not follow this pattern; it scales linearly with every unit added. Key Takeaway: Understanding the distinction between fixed and variable costs is essential for accurate forecasting and for assessing the financial impact of scope changes on the project budget.

Correct: Management reserves are intended for unknown-unknowns, which are unforeseen events that were not identified during risk management planning. Because these funds are not part of the project cost baseline, the project manager must follow a formal change control process to have the funds moved into the baseline for use. Incorrect: Utilizing the contingency reserve is incorrect because contingency reserves are specifically allocated for known-unknowns, which are risks that have been identified and recorded in the risk register. Incorrect: Updating the cost baseline immediately using management reserves is incorrect because management reserves are typically not under the direct control of the project manager and require higher-level approval before the baseline can be adjusted. Incorrect: Using the contingency reserve first is incorrect because reserves are not interchangeable; contingency is for identified risks, and using it for unidentified issues would leave the project vulnerable to the risks for which the contingency was originally intended. Key Takeaway: Contingency reserves are for identified risks (known-unknowns) and are part of the cost baseline, while management reserves are for unidentified risks (unknown-unknowns) and sit outside the cost baseline, requiring formal approval to access.

Correct: The Cost Performance Index (CPI) is calculated by dividing the Earned Value by the Actual Cost (200,000 / 220,000), which equals approximately 0.91. A CPI of less than 1.0 indicates that the project is over budget. To determine the schedule status, we look at the Schedule Performance Index (SPI), which is Earned Value divided by Planned Value (200,000 / 250,000), resulting in 0.80. An SPI of less than 1.0 indicates the project is behind schedule. Incorrect: The option suggesting the project is ahead of schedule and under budget with a CPI of 1.10 is wrong because the Actual Cost is higher than the Earned Value, and the Earned Value is lower than the Planned Value. Incorrect: The option suggesting the project is behind schedule and under budget with a CPI of 0.80 is wrong because 0.80 is the value for the Schedule Performance Index (SPI), not the CPI, and the project is over budget, not under. Incorrect: The option suggesting the project is ahead of schedule and over budget with a CPI of 1.25 is wrong because 1.25 is the result of dividing Planned Value by Earned Value, which is not a standard performance metric, and the project is actually behind schedule. Key Takeaway: In Earned Value Management, any index (CPI or SPI) less than 1.0 signifies that the project is performing worse than planned, while any index greater than 1.0 signifies performance that is better than planned.

Correct: To find the Schedule Variance (SV), we first calculate the Planned Value (PV) and Earned Value (EV). Since the project is 10 months long and 4 months have passed with work distributed evenly, the PV is 40 percent of 500,000 USD, which is 200,000 USD. The EV is the actual percentage of work completed (35 percent) multiplied by the BAC, resulting in 175,000 USD. SV is calculated as EV minus PV (175,000 – 200,000), which equals -25,000 USD. The Cost Performance Index (CPI) is calculated as EV divided by AC (175,000 / 210,000), which equals approximately 0.83. Incorrect: The option showing SV = -25,000 USD and CPI = 1.20 is incorrect because it likely results from inverting the CPI formula (AC / EV) instead of using EV / AC. The option showing SV = 25,000 USD and CPI = 0.83 is incorrect because it suggests the project is ahead of schedule by subtracting EV from PV instead of PV from EV. The option showing SV = -10,000 USD and CPI = 0.75 is incorrect as it uses incorrect values for both the variance and the index calculations. Key Takeaway: Earned Value is the value of the work actually performed; if it is lower than the Planned Value, the project is behind schedule (negative SV), and if it is lower than the Actual Cost, the project is over budget (CPI less than 1.0).

Correct: To determine the project status, we calculate the Cost Performance Index (CPI) and the Schedule Performance Index (SPI). CPI is calculated as Earned Value divided by Actual Cost (80,000 / 90,000 = 0.89). Since the CPI is less than 1.0, the project is over budget. SPI is calculated as Earned Value divided by Planned Value (80,000 / 100,000 = 0.80). Since the SPI is less than 1.0, the project is behind schedule. Therefore, the project manager must address both cost overruns and schedule delays. Incorrect: The option stating the project is under budget and ahead of schedule is wrong because both indices are below 1.0, which represents unfavorable performance. Incorrect: The option stating the project is over budget but ahead of schedule is wrong because the SPI of 0.80 clearly indicates the project is behind its planned timeline. Incorrect: The option stating the project is under budget but behind schedule is wrong because the CPI of 0.89 indicates that the project has spent more than the value of the work actually completed. Key Takeaway: In Earned Value Management, an index (CPI or SPI) of less than 1.0 indicates that the project is performing worse than planned, while an index greater than 1.0 indicates performance is better than planned.

Correct: Cost Variance (CV) is calculated as Earned Value (EV) minus Actual Cost (AC). In this scenario, £460,000 minus £490,000 equals -£30,000. A negative CV indicates the project is over budget. Schedule Variance (SV) is calculated as Earned Value (EV) minus Planned Value (PV). Here, £460,000 minus £500,000 equals -£40,000. A negative SV indicates the project is behind schedule. Incorrect: The option stating a CV of -£40,000 and SV of -£30,000 is incorrect because it transposes the formulas for cost and schedule. Incorrect: The option stating positive variances of £30,000 and £40,000 is incorrect because it incorrectly subtracts the values (e.g., AC minus EV instead of EV minus AC) or misinterprets the meaning of the negative result. Incorrect: The option stating a CV of -£30,000 and an SV of £40,000 is incorrect because the schedule variance calculation (460,000 minus 500,000) results in a negative value, not a positive one. Key Takeaway: In Earned Value Management, variances are always calculated by subtracting the reference value (Planned Value for schedule, Actual Cost for cost) from the Earned Value. Negative results always indicate unfavorable performance (over budget or behind schedule).

Correct: When current variances are considered atypical and the project is expected to proceed at the originally planned rate for the remaining work, the formula for Estimate at Completion (EAC) is Actual Cost (AC) plus the remaining budget (BAC minus EV). In this scenario, the calculation is £200,000 + (£500,000 – £150,000), which equals £550,000. Incorrect: The value of £666,667 is the result of using the formula BAC divided by CPI (Cost Performance Index), which is only used when current variances are expected to be typical and continue for the remainder of the project. The value of £350,000 represents the Estimate to Complete (ETC), which is the amount of money still needed to finish the project, rather than the total cost at completion. The value of £530,000 is an incorrect calculation that might occur if a project manager incorrectly added Actual Cost to the remaining Planned Value instead of using Earned Value. Key Takeaway: The choice of EAC formula is determined by the project manager’s assessment of whether past performance is a reliable indicator of future performance. If variances are atypical, we add the actual costs already spent to the remaining original budget.