Project Management Qualification (PMQ) Quiz 33

Correct: A lag is a required delay between a predecessor and a successor activity. In this scenario, the 2-day drying time for the sealant is a mandatory wait period after the first task finishes before the next can start, making it a lag in a Finish-to-Start (FS) relationship. A lead is an acceleration of the successor activity, allowing it to start before the predecessor is fully complete. Since the electrical work can start when the walls are 50 percent done (5 days early), this is represented as a 5-day lead on an FS relationship. Incorrect: Applying a 2-day lead to the sealant task would imply the flooring starts before the sealant is finished, which is physically impossible. Applying a 5-day lag to the electrical fix would delay the start of the electrical work until 5 days after the walls are finished, which contradicts the requirement to start early. Incorrect: Using a Start-to-Start relationship with a lag for the sealant would mean the drying time starts when the application starts, which is incorrect logic as drying only begins once application finishes. Incorrect: Using a Finish-to-Finish relationship with a lead for the sealant does not correctly model the mandatory 2-day gap required after the sealant is applied. Key Takeaway: Lag time adds a waiting period (delay) to the schedule logic, while lead time allows for an overlap (acceleration) between dependent activities.

Correct: The schedule baseline is the version of the schedule that has been formally approved by stakeholders. Its primary purpose is to provide a benchmark against which actual performance can be measured. It should only be changed through a formal change control process, typically when a change in scope or a significant event occurs that fundamentally alters the project’s timeline. This ensures that the integrity of performance measurement is maintained. Incorrect: Immediately updating the baseline to reflect every delay bypasses the change control process and renders the baseline useless for performance measurement, as it would always match actual progress. Incorrect: Adjusting the baseline at the project manager’s discretion to minimize variances is unethical and defeats the purpose of project governance and performance reporting. Incorrect: While a baseline is a controlled document, it is not completely unchangeable. If there are approved changes to the project scope or significant external factors, the baseline must be updated through formal channels to remain a relevant tool for management. Key Takeaway: A schedule baseline is a controlled reference point used for performance measurement that can only be modified through formal change control procedures.

Correct: Resource smoothing is the correct technique to use when the project completion date is a fixed constraint. It involves adjusting the timing of activities within their available float so that resource requirements do not exceed specific limits. Because it only utilizes float, it does not affect the critical path or the project end date. Incorrect: Resource leveling is used when resource limits are the primary constraint; however, this technique often results in the project’s original critical path changing and the completion date being delayed, which is not permitted in this scenario. Incorrect: The resource breakdown structure is a hierarchical tool used to categorize resources by type and category for planning purposes, but it is not an optimization technique for resolving over-allocation. Incorrect: Crashing is a schedule compression technique that involves adding more resources to critical path tasks to shorten the duration. While it addresses time, it usually increases costs and resource demand, which would likely exacerbate an over-allocation issue rather than smoothing it out. Key Takeaway: When managing resources under a fixed-deadline constraint, resource smoothing is the preferred method as it balances resource demand without impacting the project finish date by utilizing activity float. If the resource limit cannot be met through smoothing, the project manager may need to negotiate for additional resources or change the scope.

Correct: In project management, effective resource identification requires distinguishing between what people do and what items are consumed or used. Human resources are best categorized by their functional roles and the specific skills or competencies they bring to the project, which allows for accurate task assignment. Physical resources encompass all non-human assets, including equipment, materials, and facilities, and are categorized by their type to ensure proper procurement and logistics. Incorrect: Categorizing human resources by department and reporting hierarchy focuses on organizational structure rather than project needs, and focusing on depreciation for physical resources is an accounting function rather than a resource management function. Incorrect: While availability and lead times are important constraints for resource planning, they do not define the categorization of the resources themselves within a Resource Breakdown Structure. Incorrect: Duration and physical dimensions are specific attributes or constraints of resources, but they do not provide the necessary framework for identifying the fundamental nature of the resources required for project execution. Key Takeaway: A Resource Breakdown Structure (RBS) is a hierarchical representation of resources by category and type, where human resources are defined by skills/roles and physical resources are defined by their tangible nature and utility.

Correct: The Responsibility Assignment Matrix (RAM) is the most effective tool for clarifying roles and responsibilities at a task or work package level. By using a format like a RACI chart (Responsible, Accountable, Consulted, and Informed), the project manager can ensure that for every activity, there is clear accountability and a defined communication path for those who must be consulted or informed. Incorrect: A project organizational chart is a hierarchical representation of the project team members and their reporting relationships, but it does not define specific involvement or authority levels for individual tasks. A resource breakdown structure is a hierarchical list of resources related by category and resource type, which is useful for organizing and reporting resource data but not for assigning task-level responsibility. A staffing management plan is a component of the resource management plan that describes when and how team members will be acquired and how long they will be needed, focusing on the timeline and acquisition strategy rather than specific task assignments. Key Takeaway: To ensure clear accountability and avoid role confusion in complex projects, a Responsibility Assignment Matrix should be used to map work packages to specific roles and define their level of authority.

Correct: In physical resource management, when a critical facility or piece of equipment is delayed, the project manager must seek alternative solutions to maintain the project’s progress and protect other assets. Assessing the feasibility of temporary climate-controlled storage is a proactive mitigation strategy that protects the sensitive equipment already scheduled for delivery without immediately conceding to a project-wide delay. Incorrect: Canceling the contract and purchasing alternatives regardless of specifications is risky, as the new units might not meet the technical requirements of the research facility, leading to long-term operational failure. Incorrect: Updating the schedule and moving the completion date should be a last resort after all mitigation and work-around options have been explored; jumping to this step ignores the project manager’s responsibility to manage resource constraints. Incorrect: Storing sensitive equipment in a standard warehouse with industrial fans is a failure of physical resource management because it risks damaging high-value assets that require specific environmental controls, potentially leading to much higher costs and longer delays if the equipment fails. Key Takeaway: Physical resource management involves not just procurement, but the ongoing coordination of logistics, storage, and environmental requirements to ensure all project assets are protected and available when needed.

Correct: The scenario describes a resource loading issue where demand exceeds supply. The most appropriate first step when a project has a fixed deadline is resource smoothing. This involves rescheduling activities within their available float so that they do not affect the critical path or the project completion date. By moving non-critical tasks to periods of lower demand, the project manager can balance the resource histogram without delaying the project. Incorrect: Resource leveling is a technique where start and finish dates are adjusted based on resource constraints. This often results in the original critical path changing and the project completion date being delayed, which is undesirable given the fixed-deadline contract. Incorrect: While hiring external consultants is a way to increase capacity, it should not be the first priority. A project manager should first attempt to optimize the existing schedule and resources through smoothing before incurring additional costs and procurement risks. Incorrect: Reducing technical specifications or scope is a significant change to the project baseline. This should only be considered as a last resort after all schedule and resource optimization techniques have been exhausted, as it changes the value delivered to the customer. Key Takeaway: Resource smoothing is the preferred technique for addressing resource peaks when the project end date is fixed, as it utilizes float to balance demand without impacting the schedule duration.

Correct: When resources are scarce and priorities compete across multiple projects, the decision should be based on the overall benefit to the organization. Consulting the PMO or portfolio manager ensures that the decision is made with a holistic view of the portfolio’s health and strategic alignment. Incorrect: Escalating to a sponsor to demand precedence is a siloed approach that ignores the needs of the wider organization and may lead to conflict. Negotiating a 50/50 split is often ineffective because it may result in neither project having sufficient resource capacity to meet critical deadlines or resolve emergencies. Hiring an external contractor is a long-term solution that does not address the immediate conflict, especially given the time required for recruitment and security clearances. Key Takeaway: Resource scarcity in a multi-project environment requires a governance-led approach to prioritize tasks based on organizational value rather than individual project needs.

Correct: Using a competency framework combined with a skills matrix is the most effective method because it provides a standardized benchmark for what is required versus what is currently available. This objective approach allows the project manager to pinpoint specific areas where the team lacks the necessary knowledge, skills, or behaviors, enabling targeted development plans. Incorrect: Informal interviews are subjective and may be influenced by overconfidence or a lack of self-awareness regarding specific technical requirements. Relying solely on HR training records is insufficient because completing a course does not guarantee competency or practical application in a new project context. Assigning tasks to senior members and monitoring progress is a reactive approach that risks project failure if the senior members also lack the specific new skills required for the project. Key Takeaway: A competency framework provides a consistent language and set of standards to measure team capabilities, ensuring that skills gaps are identified early and addressed systematically.

Correct: The scenario describes the Storming stage, which is characterized by conflict, competition for status, and disagreements over tasks and leadership. During this phase, the project manager should move from a directing style to a coaching style, helping the team work through their differences, clarifying roles, and facilitating consensus to move toward the next stage. Incorrect: Forming is the initial stage where team members are generally polite, guarded, and looking for guidance; the scenario describes active conflict which happens after Forming. Incorrect: Norming occurs after the team has resolved its conflicts and begins to develop shared values and work practices; the scenario indicates the team is still in the midst of conflict. Incorrect: Performing is the stage where the team is highly functional, autonomous, and focused on achieving goals with minimal supervision; the described behavior of questioning authority and struggling with roles is the opposite of a performing team. Key Takeaway: The Tuckman model requires project managers to adapt their leadership style based on the team’s maturity, moving from Directing in Forming, to Coaching in Storming, to Supporting in Norming, and finally to Delegating in Performing.

Correct: The Completer Finisher is the role most effectively used at the end of a task to polish and check the work for errors. They are characterized by their painstaking attention to detail and their drive to ensure that deadlines are met and standards are maintained. In this scenario, their presence would address the documentation errors and the lack of follow-through on final tasks. Incorrect: The Resource Investigator is excellent at networking and exploring opportunities outside the team, but they often lose interest toward the end of a project and are not typically detail-oriented. Incorrect: The Shaper provides the necessary drive and courage to overcome obstacles, but they can be impatient with details and may provoke others, which does not directly solve the problem of quality control and administrative accuracy. Incorrect: The Monitor Evaluator is a strategic and discerning role that is best at analyzing options and making impartial judgments, but they are not specifically focused on the execution of final details or the completion of tasks to a high standard of finish. Key Takeaway: A balanced team requires different roles at different stages of the project lifecycle; while creative roles are vital for initiation, the Completer Finisher is essential for quality assurance and successful delivery.

Correct: According to Herzberg’s Two-Factor Theory, factors such as salary, working conditions, and company policy are categorized as hygiene factors. While their absence causes dissatisfaction, their presence only serves to prevent dissatisfaction rather than provide long-term motivation. To truly increase motivation, a manager must focus on motivators, which are intrinsic to the work itself, such as responsibility, autonomy, recognition, and personal growth. Delegating autonomy and providing recognition directly addresses these intrinsic motivators. Incorrect: Negotiating a bonus and upgrading furniture relates to hygiene factors like salary and physical working conditions, which do not create lasting motivation. Incorrect: Clarifying hierarchy and administrative procedures also falls under hygiene factors related to company policy and administration. Incorrect: Demonstrating the link between effort, performance, and rewards is the core of Vroom’s Expectancy Theory, which focuses on the cognitive process of motivation rather than the specific hygiene and motivator factors identified by Herzberg. Key Takeaway: To move beyond a baseline of satisfaction and achieve high levels of motivation, project managers must look past extrinsic rewards and focus on providing team members with meaningful work, recognition, and increased responsibility.

Correct: The scenario describes a team with high competence but low confidence or variable commitment, which corresponds to the M3 maturity level in the Hersey-Blanchard model. The appropriate response is the Supporting (S3) style. This style involves low task direction because the team already possesses the necessary skills, but high relationship support to encourage the team, share decision-making, and rebuild their confidence to act independently. Incorrect: The Delegating style is intended for M4 teams who are both highly competent and highly committed; using it here might leave the hesitant team feeling unsupported. The Coaching style is designed for M2 teams who have some competence but low commitment; providing high task direction to a technically proficient team would be redundant and potentially micromanaging. The Directing style is meant for M1 teams with low competence and low commitment; it is far too restrictive for a team that has already demonstrated high-quality technical output. Key Takeaway: Situational leadership requires the project manager to diagnose the team’s maturity based on both competence and commitment, then shift their style from task-oriented to relationship-oriented as the team develops.

Correct: Coaching is a task-oriented and performance-driven approach focused on improving specific skills or competencies for immediate project needs, which is exactly what the team member struggling with the software requires. Mentoring is a relationship-oriented and development-driven approach that focuses on long-term career growth and understanding organizational culture, making it the appropriate choice for the high-performer looking to advance their career. Incorrect: Using mentoring for the software issue is incorrect because mentoring is generally too broad and long-term for immediate technical skill gaps. Using coaching for the high-performer is less effective because coaching focuses on specific tasks rather than the broad, strategic guidance needed for career transition. Incorrect: Applying coaching to both individuals is incorrect because it fails to recognize the fundamental difference between short-term performance needs and long-term professional development. Incorrect: While a training course might help the struggling team member, placing a high-performer on a performance improvement plan is inappropriate as these plans are typically used for remedial action rather than for supporting the growth of a high-achieving employee. Key Takeaway: Coaching is about the ‘here and now’ and specific tasks, while mentoring is about the future and the person’s overall professional journey within the organization or industry. Both are essential tools for a project manager but serve different purposes in team development and talent management. No asterisks or letter references were used in this explanation as per the requirements provided.

Correct: Effective performance management relies on providing feedback that is specific, objective, and focused on improvement. By holding a private meeting, the project manager maintains the individual’s dignity while addressing the specific technical errors. Exploring the underlying causes allows the manager to understand if the issue is due to a lack of skill, excessive workload, or other external factors, leading to a collaborative solution. Incorrect: Discussing individual performance issues in a group setting like a progress meeting is inappropriate as it can cause public embarrassment, lead to defensiveness, and damage team morale. Incorrect: Reassigning tasks without a discussion avoids the performance management responsibility and fails to develop the team member, potentially leading to further resentment or loss of a valuable resource. Incorrect: Using email for sensitive feedback, especially when copying senior stakeholders like the Project Sponsor, is often seen as punitive rather than constructive. It lacks the necessary two-way dialogue required to resolve performance issues effectively. Key Takeaway: Constructive feedback should be delivered privately and promptly, focusing on specific behaviors and collaborative problem-solving to improve future performance.

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 (EV) divided by Actual Cost (AC), which is 540,000 / 580,000 = 0.93. A CPI of less than 1.0 indicates the project is over budget. SPI is calculated as Earned Value (EV) divided by Planned Value (PV), which is 540,000 / 600,000 = 0.90. An SPI of less than 1.0 indicates the project is behind schedule. Incorrect: The suggestion that the project is ahead of schedule with an SPI of 1.11 is wrong because the SPI is actually 0.90; an SPI above 1.0 would require the EV to be higher than the PV. Incorrect: The claim that the project is under budget with a Cost Variance (CV) of £40,000 is wrong because CV is calculated as EV minus AC (540,000 – 580,000), resulting in a negative £40,000, which signifies an over-budget position. Incorrect: Stating the project is performing well because Actual Cost is lower than Planned Value is a common misconception; comparing AC to PV does not account for the actual work completed (EV), and therefore cannot determine project efficiency. Key Takeaway: In Earned Value Management, any index (CPI or SPI) below 1.0 or any variance (CV or SV) below 0 indicates that the project is underperforming relative to the baseline plan.

Correct: Top-down estimation, often referred to as analogous or high-level estimation, is best suited for the early stages of a project when detailed information is limited but a quick, cost-effective estimate is needed for decision-making. Bottom-up estimation is the most accurate method but requires a detailed Work Breakdown Structure (WBS). It involves estimating the cost of individual work packages or activities and aggregating them to form the total project budget, making it ideal for creating a definitive baseline. Incorrect: Using bottom-up estimation for a feasibility study is generally impractical because the detailed information required to perform it is not yet available, and it is too time-consuming for a preliminary check. Reverting to top-down for the final budget would decrease accuracy when more detail is available. Parametric estimation for both stages ignores the opportunity to increase accuracy through bottom-up methods once the WBS is defined. While three-point estimation is excellent for managing risk, following it with analogous estimation once a WBS is complete is a step backward in terms of accuracy, as analogous estimation is less precise than the bottom-up approach that should be used at that stage. Key Takeaway: Use top-down methods when information is scarce and speed is required, and transition to bottom-up methods for the definitive budget once the project scope is decomposed into work packages.

Correct: The cost baseline is a time-phased budget that includes the estimated costs for work packages and the contingency reserves allocated for identified risks. By distributing these costs over the project schedule, the project manager creates an S-curve or baseline that allows for performance measurement using techniques like Earned Value Management. Incorrect: Combining estimates with management reserves describes the total project budget, not the cost baseline. Management reserves are intended for unforeseen risks and are typically excluded from the performance measurement baseline. Incorrect: Dividing the budget equally across the project duration is incorrect because project activities and resource requirements vary over time; a linear distribution would not provide an accurate baseline for tracking actual progress against planned work. Incorrect: Adjusting bottom-up estimates to fit a top-down business case figure is a budgeting constraint or negotiation tactic rather than the process of establishing a valid cost baseline based on the defined scope of work. Key Takeaway: The cost baseline is the authorized time-phased version of the project budget, excluding management reserves, used to monitor and measure cost performance throughout the project.

Correct: Direct costs are expenses that can be specifically and exclusively attributed to a particular project. The rental of specialized scaffolding for the renovation is a direct cost because it is incurred solely for the benefit of this specific project and would not exist if the project were not taking place. Incorrect: The monthly electricity bill for corporate headquarters is an indirect cost, also known as overhead, because it supports the entire organization and cannot be easily or accurately traced to a single project. Incorrect: The salary of the Human Resources Director is an indirect cost because their work supports the whole company across multiple projects and functional areas rather than being dedicated to one specific project’s deliverables. Incorrect: General liability insurance for all company operations is an indirect cost because it is a shared business expense that provides coverage for the entire entity rather than being a project-specific insurance policy like a performance bond. Key Takeaway: The primary distinction is traceability; direct costs are uniquely linked to project work, while indirect costs are shared across the organization or multiple projects simultaneously. No asterisks or letter references were used in this explanation as requested. No control tokens were used in the JSON structure.

Correct: Variable costs are those that change in direct proportion to the level of activity or volume of work produced by the project. Since the cloud computing costs depend on the number of data processing cycles, they will fluctuate based on how much the system is used. Fixed costs are those that remain constant regardless of the project’s output or activity level within a certain range. The office lease is a set monthly fee that does not change based on how much work the project team completes. Incorrect: The suggestion that both are fixed costs is incorrect because the cloud computing expense is usage-based and will vary month-to-month. Incorrect: The suggestion that cloud computing is fixed and the lease is variable is a reversal of the standard definitions; the lease is the stable element while the cloud usage is the fluctuating element. Incorrect: Categorizing the office lease as a variable cost is incorrect because rent is a classic example of a fixed cost that remains stable over the term of the lease. Categorizing cloud computing as an indirect cost might be true in some accounting contexts, but it does not address the fundamental nature of it being a variable cost in this scenario. Key Takeaway: Distinguishing between fixed and variable costs allows project managers to perform better sensitivity analysis and understand how changes in project scope or activity levels will impact the total budget.

Correct: Contingency reserves are specifically allocated for identified risks that have been documented in the risk register, often referred to as known-unknowns. Since the soil instability was an identified risk, it is appropriate to use the contingency reserve. Management reserves are intended for unforeseen events that were not identified during risk planning, known as unknown-unknowns. The unprecedented trade policy change falls into this category and requires management approval to access these funds. Incorrect: Using management reserves for both is incorrect because the soil instability was a known risk and should have been covered by the contingency reserve which is part of the cost baseline. Incorrect: Using contingency reserves for both is incorrect because contingency reserves are only for identified risks; the trade policy change was unforeseen and therefore sits outside the scope of the contingency reserve. Incorrect: Requesting a budget increase for an identified risk is unnecessary if a contingency reserve exists, and using contingency for an unidentified risk like the trade policy change violates standard project governance. Key Takeaway: Contingency reserves are for identified risks and are part of the cost baseline, while management reserves are for unidentified risks and are not part of the cost baseline but are part of the total project budget.

Correct: To determine the status, we calculate the Schedule Variance (SV) and Cost Variance (CV). SV is Earned Value minus Planned Value (350,000 – 400,000 = -50,000), indicating the project is behind schedule. CV is Earned Value minus Actual Cost (350,000 – 385,000 = -35,000), indicating the project is over budget. To find the Estimate at Completion (EAC) assuming current performance continues, we use the formula BAC divided by the Cost Performance Index (CPI). CPI is EV / AC (350,000 / 385,000 = 0.909). Therefore, EAC = 800,000 / 0.909 = £880,000. Incorrect: The suggestion that the project is ahead of schedule is wrong because the Schedule Variance is negative, meaning less work was completed than planned. The suggestion that the EAC is £835,000 is incorrect because that figure is calculated using the formula AC + (BAC – EV), which assumes future work will be performed at the originally budgeted rate rather than the current performance rate. The suggestion that the project is under budget or has an EAC of £770,000 is incorrect because the Actual Cost is higher than the Earned Value, resulting in a CPI of less than 1.0. Key Takeaway: When cost performance is expected to continue at the same rate, EAC is calculated by dividing the total budget by the current cost performance index (CPI).

Correct: To find the Cost Variance and SPI, you must first calculate the Earned Value (EV). EV is the Budget at Completion multiplied by the percentage of work completed (500,000 x 0.35 = 175,000). Cost Variance (CV) is calculated as EV minus Actual Cost (175,000 – 220,000 = -45,000). The Schedule Performance Index (SPI) is calculated as EV divided by Planned Value (175,000 / 200,000 = 0.875). Incorrect: CV = -£20,000; SPI = 0.800 is incorrect because it uses an incorrect calculation for Earned Value or confuses the relationship between PV and AC. Incorrect: CV = -£45,000; SPI = 1.143 is incorrect because the SPI formula was inverted, dividing Planned Value by Earned Value instead of Earned Value by Planned Value. Incorrect: CV = £45,000; SPI = 0.875 is incorrect because the Cost Variance is negative, as the actual costs exceed the earned value, indicating the project is over budget. Key Takeaway: Earned Value Management (EVM) requires calculating the value of work performed (EV) first to determine both cost and schedule health. A negative variance or an index below 1.0 indicates the project is performing worse than planned.

Correct: To determine the status, we calculate the indices. SPI is Earned Value divided by Planned Value (540,000 / 600,000 = 0.90). An SPI less than 1.0 indicates the project is behind schedule, specifically achieving only 90 percent of the work planned to date. CPI is Earned Value divided by Actual Cost (540,000 / 575,000 = 0.939, rounded to 0.94). A CPI less than 1.0 indicates the project is over budget, meaning for every dollar spent, only 94 cents of value is being earned. Incorrect: The statement that the project is ahead of schedule but over budget is incorrect because the SPI is 0.90, not 1.11; an SPI below 1.0 always indicates a delay. Incorrect: The statement that the project is behind schedule but under budget is incorrect because the CPI is 0.94, not 1.06; a CPI below 1.0 indicates the project is over budget, not under. Incorrect: The statement that the project is performing exactly to the cost baseline is incorrect because the Actual Cost (575,000) is higher than the Earned Value (540,000), resulting in a CPI of 0.94 rather than 1.00. Key Takeaway: Both CPI and SPI are efficiency indicators where a value of 1.0 represents on-target performance, values greater than 1.0 represent favorable performance (under budget or ahead of schedule), and values less than 1.0 represent unfavorable performance (over budget or behind schedule).

Correct: Cost Variance (CV) is calculated as Earned Value (EV) minus Actual Cost (AC). In this scenario, £410,000 minus £460,000 equals -£50,000, indicating the project is over budget. Schedule Variance (SV) is calculated as Earned Value (EV) minus Planned Value (PV). Here, £410,000 minus £450,000 equals -£40,000, indicating the project is behind schedule. Incorrect: The option stating the project is under budget and ahead of schedule incorrectly interprets negative variance values as positive performance. The option stating the project is over budget by £40,000 and behind schedule by £50,000 has swapped the formulas for CV and SV. The option stating the project is over budget by £10,000 and ahead of schedule by £40,000 uses an incorrect calculation for cost variance and misinterprets the schedule variance direction. Key Takeaway: In Earned Value Management, a negative variance indicates that the project is performing worse than planned, either by costing more or taking longer than the baseline.

Correct: When current cost performance (CPI) is expected to continue for the remainder of the project, the formula for Estimate at Completion (EAC) is BAC divided by CPI. First, calculate CPI as EV / AC (£250,000 / £300,000 = 0.833). Then, EAC is £500,000 / 0.833 = £600,000. The Estimate to Complete (ETC) is the additional money required to finish the project, calculated as EAC – AC (£600,000 – £300,000 = £300,000). Incorrect: The option stating EAC is £600,000 and ETC is £250,000 correctly identifies the EAC but calculates ETC as BAC – EV, which fails to account for the continuing cost inefficiency. The option stating EAC is £550,000 and ETC is £250,000 uses the formula for atypical variances (AC + BAC – EV), which assumes future work will be completed at the original budgeted rate; this contradicts the scenario’s premise that current performance will continue. The option stating EAC is £550,000 and ETC is £300,000 incorrectly applies the atypical variance formula for EAC while using a different logic for ETC, leading to an inconsistent forecast. Key Takeaway: If project variances are expected to persist, the CPI must be used to forecast both the total final cost and the remaining spend.

Correct: Managing project liquidity is primarily about the timing of cash movements rather than just the total amount of money spent. By negotiating interim progress payments or an advance payment, the project manager addresses the funding gap where expenditures exceed income. This ensures the project has sufficient working capital to meet its obligations as they fall due. Incorrect: Improving the Cost Performance Index or reducing material quality addresses cost efficiency but does not solve the fundamental timing issue of cash flow. A project can be under budget but still fail due to a lack of liquidity. Incorrect: Unilaterally extending payment terms to subcontractors can lead to supply chain failure, legal disputes, and reputational damage, which increases project risk significantly. Incorrect: Increasing the total budget does not solve the immediate liquidity crisis if the timing of the payments remains the same; it merely increases the total amount to be paid eventually. Key Takeaway: Effective cash flow management requires balancing the timing of cash inflows and outflows to maintain liquidity throughout the project lifecycle, often requiring specific contractual payment terms like mobilization payments or monthly valuations instead of infrequent milestones or back-ended payments.

Correct: The Cost Performance Index (CPI) is calculated as Earned Value (EV) divided by Actual Cost (AC). In this scenario, £400,000 / £500,000 equals 0.80. A CPI of less than 1.0 indicates the project is over budget. To forecast the total cost at completion (EAC) assuming current trends continue, the formula is BAC / CPI, which is £800,000 / 0.80, resulting in £1,000,000. Incorrect: The assessment that the project is performing well because the Actual Cost is 62.5 percent of the budget is flawed because it ignores the value of the work actually completed (EV); the Estimate to Complete (ETC) would actually be £500,000 (EAC minus AC) under these conditions, not £300,000. Incorrect: The Cost Variance (CV) is calculated as EV minus AC (£400,000 – £500,000), which results in a negative variance of -£100,000, indicating an over-budget situation, not a positive variance. Incorrect: While the project might be behind schedule, the Schedule Variance (SV) is calculated using Planned Value (PV), which is not provided in this scenario; furthermore, resource leveling is a technique used to address resource over-allocation and usually extends the schedule rather than directly reducing actual costs already incurred. Key Takeaway: Effective cost control in project management requires the use of Earned Value Management (EVM) metrics like CPI and EAC to provide an objective view of financial performance rather than simply looking at the remaining balance of the budget or the total spend to date. Any CPI below 1.0 signifies that the project is delivering less value than the cost being incurred, necessitating corrective action or revised forecasting.

Correct: In project management, a risk is an uncertain event, whereas an issue is something that has already happened and is impacting project objectives. When a risk materializes, it must be transitioned to the issue log. Because a critical supplier bankruptcy likely exceeds the project manager’s delegated authority and may threaten the project’s viability, escalation to the project sponsor is the necessary next step. Incorrect: Updating the risk register to 100 percent probability is incorrect because the event is no longer a risk; it is a certainty that requires issue management protocols rather than risk management. Incorrect: Qualitative risk analysis is a tool used to prioritize uncertain future events. Since the bankruptcy has already occurred, the impact is a reality, and the time for prioritization based on probability has passed. Incorrect: Submitting a formal change request to extend the completion date is premature. While a change request may eventually be necessary, the project manager must first log the issue, assess the full impact, and consult with the sponsor before proposing specific baseline changes. Key Takeaway: Risks are proactive and deal with uncertainty, while issues are reactive and deal with current realities; once a risk occurs, it is managed through the issue management process.

Correct: After identifying risks, the next step in the risk management process is assessment. Qualitative assessment involves evaluating the probability of occurrence and the potential impact on project objectives. This allows the project manager to prioritize risks, focusing resources on those that pose the greatest threat or offer the most significant opportunity. Incorrect: Assigning owners and developing detailed mitigation strategies for every single risk before prioritization is inefficient and a poor use of project resources. Not all risks require the same level of planning or management. Incorrect: While quantitative analysis like Monte Carlo simulation is valuable, it is typically performed after qualitative assessment or reserved for the most significant risks. It is a more time-consuming and data-intensive process that is not the immediate next step for a raw list of 100 risks. Incorrect: Transferring all high-impact risks to insurance is a specific risk response strategy. Responses should only be decided after the risks have been assessed and prioritized, and insurance may not be the most cost-effective or appropriate response for every high-impact risk. Key Takeaway: The risk management process follows a logical sequence: identification must be followed by assessment to ensure that response planning is focused on the most critical project risks.