Project Management Qualification (PMQ) Quiz 81

Correct: The Implementer is essential for transforming abstract ideas and strategies into manageable, practical work tasks, while the Completer Finisher is crucial for the final stages of a project to ensure that errors are caught and quality standards are met. This directly addresses the project manager’s concerns about turning ideas into plans and meeting delivery standards. Incorrect: Resource Investigator and Shaper focus on external networking and driving the team under pressure, respectively; while valuable, they do not specifically address the need for practical execution and final quality control. Incorrect: Co-ordinator and Teamworker are people-oriented roles focused on delegation and team harmony, which does not solve the gap in technical execution and finishing. Incorrect: Plant and Monitor Evaluator are already represented in the team by the creative individual and the strategic thinker, so adding more would lead to an imbalance of thinking roles without improving the team’s ability to execute. Key Takeaway: A balanced team requires a mix of thinking, people, and action roles; identifying gaps in execution requires adding action-oriented roles like the Implementer and Completer Finisher.

Correct: According to Herzberg’s Two-Factor Theory, factors such as responsibility, recognition, and the work itself are considered motivators that lead to job satisfaction and higher performance. By delegating autonomy and providing recognition, the project manager is addressing these motivators directly. Incorrect: Negotiating a bonus and upgrading facilities are hygiene factors. While their absence causes dissatisfaction, their presence only prevents dissatisfaction and does not provide long-term motivation. Incorrect: Clarifying reporting lines and safety policies are also hygiene factors related to company policy and working conditions, which do not drive motivation according to Herzberg. Incorrect: While social events improve interpersonal relationships, Herzberg classifies these as hygiene factors rather than true motivators. Key Takeaway: To truly motivate a team, a project manager must look beyond hygiene factors like pay and conditions and focus on providing opportunities for achievement, growth, and responsibility.

Correct: The team described is at a D3 maturity level, characterized by high competence but variable or low commitment/confidence due to the restructure. In situational leadership models, the appropriate response for a D3 team is the Supporting (S3) style. This style involves high relationship support to address the emotional and motivational needs of the team while maintaining low task direction because the team is already technically capable. Incorrect: The Directing style is intended for D1 teams who lack competence but have high commitment; using it here would be seen as micromanagement and would likely further demotivate senior engineers. The Coaching style is intended for D2 teams who have some competence but low commitment; while it provides support, the high level of task direction is unnecessary for this senior team and may be perceived as patronizing. The Delegating style is intended for D4 teams with both high competence and high commitment; because the team is currently struggling with confidence and uncertainty, leaving them entirely to their own devices without support could lead to further performance degradation. Key Takeaway: Effective project leadership requires adapting your style based on the specific maturity level of the team, which is a combination of their technical competence and their psychological commitment to the task or organization.

Correct: Coaching is a task-oriented and performance-driven approach focused on improving specific skills or behaviors in the short term. This makes it the appropriate choice for Sarah, who needs to master a specific software tool to perform her current role. Mentoring is a relationship-oriented and development-driven approach focused on long-term career growth and organizational navigation. This is the correct choice for David, who is looking for strategic guidance and career progression. Incorrect: Using mentoring for Sarah and coaching for David is an inversion of the techniques’ strengths; mentoring is too broad for immediate software training, and coaching on a specific process does not address David’s desire for strategic leadership development. Incorrect: Using coaching for both individuals ignores the fact that David’s needs are developmental and long-term rather than task-specific. Incorrect: Using mentoring for both individuals is inefficient for Sarah’s situation, as she requires immediate, practical skill acquisition which is better served by the structured feedback of coaching. Key Takeaway: Coaching focuses on the ‘how’ of current tasks and performance, while mentoring focuses on the ‘who’ of future career development and professional identity.

Correct: Effective performance management involves addressing issues promptly and privately. By focusing on specific facts rather than personality, and by listening to the team member’s perspective, the project manager can identify root causes such as resource constraints or personal issues. Collaborative goal-setting for the recovery plan ensures the team member remains engaged and accountable. Incorrect: Highlighting delays in a public forum like a steering committee meeting is likely to cause embarrassment and defensiveness, damaging the working relationship and team morale. Incorrect: Issuing a formal written warning as a first step is an escalatory measure that should typically follow informal attempts to resolve the issue; it creates a climate of fear rather than one of development. Incorrect: Ignoring the issue is a failure of the project manager’s responsibility to manage the project’s progress and can lead to the problem escalating or other team members feeling that poor performance is acceptable. Key Takeaway: Constructive feedback should be timely, specific, and focused on problem-solving through a two-way dialogue to maintain motivation and improve project outcomes.

Correct: The Cost Performance Index (CPI) is calculated by dividing the Earned Value (EV) by the Actual Cost (AC). In this scenario, 180,000 divided by 220,000 equals approximately 0.82. A CPI of less than 1.0 indicates that the project is over budget, meaning the project is receiving less than one pound of value for every pound spent. Incorrect: The value of 1.22 is incorrect because it is the result of dividing Actual Cost by Earned Value, which is the inverse of the correct formula. Incorrect: The value of 0.72 is the Schedule Performance Index (SPI), calculated by dividing Earned Value by Planned Value (180,000 / 250,000); while this indicates the project is behind schedule, it does not represent the cost performance index. Incorrect: While the CPI calculation of 0.82 is correct, the interpretation that the project is under budget is wrong, as any CPI value below 1.0 represents an over-budget situation. Key Takeaway: CPI is a measure of cost efficiency where a value of 1.0 means the project is on budget, above 1.0 means under budget, and below 1.0 means over budget.

Correct: Top-down estimation is most appropriate during the early stages of a project when there is limited detail but a need for a quick assessment of viability. It relies on historical data or expert judgment to provide a macro-level view. Bottom-up estimation is used when the project is well-defined, as it involves estimating the cost of individual work packages or activities and aggregating them to provide a highly accurate and detailed total budget. Incorrect: Using bottom-up estimation for the concept phase is incorrect because this method requires a detailed Work Breakdown Structure which is not yet available at the start of a project. Conversely, using top-down for the execution phase is incorrect because it lacks the granularity and accuracy required for a definitive budget. Incorrect: Using parametric estimation for both phases is not ideal because while it can be accurate, it depends on the availability of robust statistical data and does not account for the shift from high-level planning to detailed execution. Incorrect: Using analogous estimation for both phases is insufficient because while it is a useful top-down technique for early estimates, it is generally not accurate enough for the execution phase where detailed cost control is required. Key Takeaway: Top-down techniques are used for speed and strategic decision-making early in the project, while bottom-up techniques are used for accuracy and detailed planning once the project scope is fully decomposed into work packages.

Correct: In project management budgeting, the cost baseline is the approved version of the time-phased project budget, excluding any management reserves. It includes the activity cost estimates and the contingency reserves (which are set aside for identified risks or known-unknowns). The total project budget is then calculated by adding the management reserve (set aside for unidentified risks or unknown-unknowns) to the cost baseline. Incorrect: The statement that the cost baseline represents raw activity estimates is incorrect because the baseline must include contingency reserves to be a valid performance measurement tool. The suggestion that the cost baseline includes management reserves is incorrect because management reserves are not part of the performance measurement baseline, as the project manager does not have immediate authority over them. The claim that the terms are used interchangeably is incorrect because they represent different levels of financial authorization and include different types of risk reserves. Key Takeaway: The cost baseline is the performance measurement baseline for cost, consisting of the work package estimates plus contingency reserves; adding management reserves to this baseline results in the total project budget.

Correct: Direct costs are expenses that can be specifically and exclusively attributed to a particular project. The wages of software developers working specifically on the project deliverables are a prime example because these costs are incurred solely for the benefit of this project and would not exist without it. Incorrect: The monthly electricity bill for the entire building is an indirect cost because it is a shared utility expense that supports multiple projects and general business operations, making it difficult to trace exactly to one project. The annual licensing fee for a company-wide HR system is an indirect cost because it is an overhead expense that benefits the entire organization rather than a specific project. The salary of the corporate legal counsel is also an indirect cost as they provide a general service across the whole company, and their time is not dedicated solely to the execution of this specific software project. Key Takeaway: Direct costs are directly linked to project activities, while indirect costs, often referred to as overhead, are shared across the organization or multiple projects.

Correct: Fixed costs are expenses that do not change in relation to the level of activity or production volume within a project. In this scenario, the security license is a flat fee that remains constant regardless of project activity, making it a fixed cost. Variable costs are expenses that fluctuate in direct proportion to the volume of work or the quantity of resources consumed. Since the total cost of the cabling depends on the number of meters required for the layout, it is a variable cost. Incorrect: Categorizing the security license as variable and cabling as fixed is incorrect because it reverses the fundamental definitions of how these costs behave relative to project volume. Incorrect: Classifying both as fixed costs simply because they are in the baseline is a misunderstanding of cost behavior; the baseline contains both fixed and variable elements that respond differently to changes in project scope or activity. Incorrect: Labeling the cabling as a sunk cost is inaccurate because sunk costs refer to money already spent that cannot be recovered, whereas this is a planned expenditure. While the license could be an indirect cost in some contexts, the primary distinction requested here relates to its behavior as a fixed expense. Key Takeaway: Distinguishing between fixed and variable costs allows project managers to perform more accurate sensitivity analysis and better understand how budget totals will shift if project volume or duration changes during execution. This is a fundamental component of effective cost estimation and control within the PMQ framework.

Correct: Contingency reserves are allocated for identified risks (known-unknowns) that are documented in the risk register. Since the API update was an identified risk, the project manager has the authority to use contingency reserves which are part of the cost baseline. Management reserves are intended for unidentified risks (unknown-unknowns). Because the change in data privacy laws was unforeseen and not in the risk register, it falls under management reserves. Accessing management reserves typically requires a formal change request and approval from senior management or the sponsor because these funds are not part of the performance measurement baseline. Incorrect: Using management reserves for both events is incorrect because the API update was an identified risk and should be covered by the contingency reserve already included in the cost baseline. Incorrect: Using contingency reserves for both events is incorrect because contingency reserves are only for identified risks; unforeseen events like the law change are not covered by the baseline contingency and require management reserve access. Incorrect: Swapping the reserves is incorrect because management reserves are specifically for the unknown-unknowns, while contingency reserves are for the known-unknowns identified during the risk management process. Key Takeaway: Contingency reserves are for identified risks and are part of the cost baseline, while management reserves are for unidentified risks and are part of the total budget but not the cost baseline.

Correct: To determine the status, we calculate the Schedule Variance (SV = EV – PV) and the Cost Variance (CV = EV – AC). Here, SV is 400,000 minus 450,000, which equals negative 50,000, indicating the project is behind schedule. The CV is 400,000 minus 425,000, which equals negative 25,000, indicating the project is over budget. The Cost Performance Index (CPI) is calculated as EV divided by AC (400,000 / 425,000), which equals approximately 0.94. This means for every pound spent, only 94 pence of progress is achieved. Incorrect: The claim that the project is ahead of schedule but over budget is wrong because the Earned Value is less than the Planned Value, resulting in a negative Schedule Variance. Incorrect: The claim that the project is behind schedule but under budget is wrong because budget status is determined by comparing Earned Value to Actual Cost, not Planned Value to Actual Cost; since EV is less than AC, it is over budget. Incorrect: The claim that the project is performing to plan is wrong because both the Schedule Performance Index (0.89) and Cost Performance Index (0.94) show significant deviations from the baseline of 1.0. Key Takeaway: In EVM, a variance less than zero or an index less than one indicates unfavorable performance (behind schedule or over budget).

Correct: Earned Value (EV) is calculated by multiplying the total Budget at Completion (BAC) by the percentage of work actually completed (£500,000 multiplied by 0.35 equals £175,000). The Cost Performance Index (CPI) is then calculated by dividing the EV by the Actual Cost (£175,000 divided by £220,000 equals 0.795, which rounds to 0.80). This indicates the project is over budget. Incorrect: The option stating EV is £175,000 and CPI is 1.26 is incorrect because it divides the Actual Cost by the Earned Value, which is the inverse of the correct formula. Incorrect: The option stating EV is £200,000 and CPI is 0.91 is incorrect because it uses the Planned Value as the Earned Value, failing to account for the actual progress of 35%. Incorrect: The option stating EV is £175,000 and CPI is 0.88 is incorrect because 0.88 is the Schedule Performance Index (SPI), calculated by dividing EV by PV, rather than the Cost Performance Index. Key Takeaway: Earned Value represents the quantified value of work actually performed, and the CPI is the primary metric used to determine if a project is under or over budget relative to the work achieved.

Correct: To determine the status, we calculate the Cost Performance Index (CPI) and the Schedule Performance Index (SPI). CPI is calculated as Earned Value divided by Actual Cost (160,000 / 180,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 (160,000 / 200,000 = 0.80). Since the SPI is less than 1.0, the project is behind schedule. The project manager must identify why these variances are occurring to implement corrective actions. Incorrect: The statement that the project is under budget but behind schedule is wrong because the CPI of 0.89 indicates that costs are higher than the value of the work performed. Incorrect: The statement that the project is over budget but ahead of schedule is wrong because the SPI of 0.80 indicates that the project is only progressing at 80 percent of its planned rate. Incorrect: The claim that the project is performing as planned is wrong because both indices show significant negative deviations from the baseline of 1.0, which requires management intervention regardless of arbitrary thresholds. Key Takeaway: In Earned Value Management, a CPI or SPI value less than 1.0 indicates unfavorable performance (over budget or behind schedule, respectively).

Correct: Cost Variance (CV) is calculated as Earned Value (EV) minus Actual Cost (AC). In this scenario, £410,000 – £435,000 equals -£25,000. A negative CV indicates the project is over budget. Schedule Variance (SV) is calculated as Earned Value (EV) minus Planned Value (PV). Here, £410,000 – £450,000 equals -£40,000. A negative SV indicates the project is behind schedule. Incorrect: The statement that the project is under budget and ahead of schedule is wrong because it assumes positive variances, which would only occur if EV was higher than both AC and PV. The statement that the project is £40,000 over budget and £25,000 behind schedule incorrectly swaps the formulas for CV and SV. The statement that the project is £15,000 over budget and £40,000 behind schedule is incorrect because it likely miscalculates the cost variance by comparing Actual Cost to Planned Value instead of Earned Value. Key Takeaway: In Earned Value Management, variances are always calculated by subtracting another metric from the Earned Value. Negative results always represent unfavorable conditions (over budget or behind schedule).

Correct: When current cost performance is expected to continue for the remainder of the project, the formula for Estimate at Completion (EAC) is BAC divided by the Cost Performance Index (CPI). First, calculate the CPI by dividing EV (£350,000) by AC (£400,000), which equals 0.875. Then, divide the BAC (£800,000) by the CPI (0.875) to arrive at £914,286. Incorrect: The value of £850,000 is calculated using the formula AC + (BAC – EV), which is only used when future work is expected to be performed at the originally budgeted rate, not when current trends persist. Incorrect: The value of £450,000 represents the Estimate to Complete (ETC) if the project continues at the budgeted rate, rather than the total Estimate at Completion. Incorrect: The value of £960,000 would be the result of an incorrect calculation or a different forecasting model that accounts for schedule performance (SPI) as well, which was not specified as a requirement here. Key Takeaway: The choice of EAC formula depends on the project manager’s assessment of whether current variances are typical or atypical of future performance.

Correct: Managing project liquidity requires a focus on the timing of cash inflows and outflows rather than just the total budget. By producing a detailed cash flow forecast, the project manager can visualize exactly when the cash shortfall will occur. Negotiating more frequent payments or an advance payment directly addresses the timing mismatch between the project’s obligations and its income. Incorrect: Utilizing the project contingency reserve is inappropriate because contingency is intended to manage identified risks and uncertainties in scope or cost, not to solve structural cash flow timing issues. Incorrect: Delaying payments to suppliers and subcontractors can lead to breached contracts, work stoppages, and damaged professional relationships, which ultimately increases project risk and may lead to higher costs in the long run. Incorrect: The Cost Performance Index (CPI) is a measure of cost efficiency relative to the work performed; it does not provide information about the timing of cash movements or the availability of liquid funds to meet immediate debts. Key Takeaway: Effective liquidity management involves proactive cash flow forecasting and the alignment of payment schedules to ensure the project remains solvent throughout its duration.

Correct: The Cost Performance Index (CPI) is calculated as Earned Value divided by Actual Cost (200,000 / 250,000 = 0.80). When current performance is expected to continue, the Estimate at Completion (EAC) is calculated as the Budget at Completion divided by the CPI (500,000 / 0.80 = 625,000). Reporting these figures alongside a variance analysis is the standard procedure for financial reporting and cost control to ensure stakeholders have a realistic view of the project’s financial health. Incorrect: Reporting a Cost Variance of £50,000 is mathematically incorrect because the variance is actually negative £50,000 (EV minus AC), indicating an over-budget status. Simply maintaining the original budget without acknowledging the trend fails to provide an accurate forecast. Incorrect: Reporting a Schedule Performance Index (SPI) of 0.80 is inappropriate here because the question focuses on cost performance, and SPI measures schedule efficiency (EV / Planned Value), which cannot be determined without the Planned Value. Requesting funds without analysis bypasses the necessary control process. Incorrect: Reporting completion based on Actual Cost is a common error; progress should be measured by Earned Value (which shows the project is 40% complete, not 50%). While scope reduction is a potential strategy, it should not be the immediate reporting action before a full variance analysis and stakeholder consultation. Key Takeaway: Effective cost control requires using Earned Value Management (EVM) metrics to provide objective status updates and realistic forecasts to stakeholders, enabling informed decision-making.

Correct: When an uncertain event (a risk) actually occurs, it ceases to be a risk and becomes an issue. The standard procedure in project management is to move the item from the risk register to the issue log. Because a major sub-contractor bankruptcy is likely to affect project constraints like time, cost, or quality beyond the project manager’s day-to-day control, escalation to the project sponsor is necessary to seek guidance or additional resources. Incorrect: Updating the risk register to 100 percent probability is incorrect because the risk register is for managing uncertainty; once the event has happened, it is a certainty and must be managed as an issue. Closing the risk and initiating a change request before recording it in the issue log is the wrong sequence; the issue must be formally logged and assessed before the full impact on the baseline is known and a change request is submitted. Waiting for the next monthly status report is inappropriate because issues require timely management and resolution to minimize their impact on the project. Key Takeaway: Risks are proactive and deal with uncertainty, while issues are reactive and deal with current realities; the transition from risk to issue must be documented in the issue log to ensure formal tracking and resolution.

Correct: After the identification phase, the next logical step is qualitative risk assessment. This involves evaluating the probability of each risk occurring and the impact it would have on project objectives. This allows the project manager to prioritize risks using a probability-impact matrix, focusing resources on those with the highest scores while moving low-priority risks to a watch list. Incorrect: Initiating quantitative risk analysis for every risk is incorrect because quantitative analysis is a data-heavy, time-consuming process usually reserved for the most significant risks or for determining overall project contingency after qualitative filtering. Creating a detailed risk response plan for all 100 risks is incorrect because it is an inefficient use of project resources; only prioritized risks should have formal response plans. Assigning risk owners and implementing mitigation strategies is premature because the risks have not yet been assessed or prioritized to determine if mitigation is even the appropriate or cost-effective strategy. Key Takeaway: Qualitative risk assessment is the essential bridge between risk identification and risk response planning, ensuring that management effort is focused on the most critical threats and opportunities.

Correct: SWOT analysis is the most effective tool for this scenario because it provides a structured framework to examine internal factors (strengths and weaknesses) and external factors (opportunities and threats), which aligns with the project manager’s goal of evaluating organizational capabilities against market and regulatory conditions. Incorrect: Brainstorming is a creative, unstructured technique used to generate a wide range of ideas quickly, but it does not inherently categorize risks into internal and external domains. Incorrect: The Delphi technique is a method used to gain consensus among a panel of experts through multiple rounds of anonymous questionnaires, primarily to reduce bias rather than to scan the environment. Incorrect: Checklists are useful for ensuring common risks from previous projects are not overlooked, but they are limited by historical experience and may fail to identify novel strategic risks specific to the current project’s unique context. Key Takeaway: SWOT analysis is a strategic tool that helps project managers identify risks by looking at the project from both an internal organizational perspective and an external environmental perspective.

Correct: The primary purpose of a probability and impact grid in qualitative risk analysis is to prioritize risks. By assessing the likelihood of occurrence and the potential effect on project objectives, the project manager can categorize risks into high, medium, or low priority. This allows the team to focus their limited resources on the most critical threats and opportunities. Incorrect: Calculating the exact financial contingency reserve is a function of quantitative risk analysis, specifically using techniques like Expected Monetary Value (EMV), rather than a qualitative grid. Identifying root causes is a task associated with the risk identification process, and while the grid helps prioritize risks, it does not inherently identify the underlying causes. Performing statistical simulations to predict completion dates refers to quantitative techniques such as Monte Carlo analysis, which provides a numerical probability of success rather than a qualitative ranking. Key Takeaway: Qualitative risk analysis is a subjective assessment tool used to rank and prioritize risks so that the project team knows where to focus their management efforts.

Correct: Decision tree analysis is the most appropriate technique for this scenario because it allows the project manager to map out different decision paths and calculate the Expected Monetary Value (EMV) for each. The EMV for Strategy 2 is calculated by multiplying the probability of each outcome by its cost and summing the results: (0.60 multiplied by 400,000) plus (0.40 multiplied by 1,000,000), which equals 240,000 plus 400,000, resulting in 640,000 GBP. Incorrect: Monte Carlo simulation is a technique used to model the probability of different outcomes in a process that cannot easily be predicted due to the intervention of random variables; it is typically used for overall project schedule or cost risk rather than comparing two discrete decision paths. Incorrect: Sensitivity analysis is used to determine which individual risks have the most potential impact on the project (often visualized in a Tornado diagram) but is not used to calculate the EMV of specific decision branches. Incorrect: While decision tree analysis is the correct tool, the value of 700,000 GBP is mathematically incorrect for Strategy 2 as it represents a simple average of the two costs rather than a probability-weighted average. Key Takeaway: Decision tree analysis provides a structured, quantitative method for comparing different options by calculating the probability-weighted average of all possible outcomes for each choice.

Correct: Transfer involves shifting the impact and ownership of a threat to a third party. In this scenario, by hiring a specialist contractor and using a contract with a penalty clause, the project manager has moved the financial and operational consequences of the risk from the project to the subcontractor. Incorrect: Mitigate focuses on reducing the probability or impact of a risk through internal actions, such as additional training or using safer equipment, rather than shifting the liability. Incorrect: Avoidance would require changing the project plan to eliminate the threat entirely, such as choosing a different material for the facade that is not susceptible to breakage. Incorrect: Acceptance means acknowledging the risk and taking no proactive action to change its probability or impact, either by doing nothing or simply setting aside a contingency fund. Key Takeaway: Transfer is a risk response strategy that uses third parties to bear the risk, typically through insurance, warranties, or specific contractual terms like fixed-price agreements or penalty clauses.

Correct: The exploit strategy is selected when the project team wants to eliminate the uncertainty associated with a particular upside risk by ensuring the opportunity definitely happens. By redesigning the power stations to guarantee meeting the criteria, the project manager is taking definitive action to make sure the benefit of the grant is realized. Incorrect: Enhance is incorrect because it involves increasing the probability or impact of an opportunity rather than making it a certainty. Incorrect: Share is incorrect because it involves partnering with a third party to share the benefits of the opportunity, which is not described in this scenario. Incorrect: Reject is incorrect because it involves taking no action and letting the opportunity pass if it does not happen naturally. Key Takeaway: Exploit is the most proactive response for opportunities, aimed at ensuring the positive impact is fully captured by removing any chance of it not occurring.

Correct: Risk management is an iterative process that must continue throughout the project lifecycle. A formal risk review allows the project manager to retire or close risks that are no longer a threat, which keeps the team focused on current issues. It also provides the necessary framework to analyze new risks and ensure that the probability and impact of existing risks are still accurate based on the current project environment. Incorrect: Removing expired risks entirely from the database is poor practice because the risk register should serve as a historical record for lessons learned; instead, they should be marked as closed or retired. Adding a risk without assessment bypasses the qualitative and quantitative analysis needed for proper prioritization. Waiting until a phase gate review is inappropriate because risk management must be proactive; delaying the update could lead to missed opportunities for mitigation. Creating separate sub-registers for new risks while leaving the main register static creates fragmentation and prevents a holistic view of the project’s risk profile. Key Takeaway: The risk register is a live document that requires regular maintenance through formal reviews to ensure it accurately reflects the project’s current risk exposure.

Correct: The fundamental distinction between a risk and an issue is its state of certainty and timing. A risk is an uncertain event or set of circumstances that, should it occur, will have an effect on the achievement of one or more objectives. Once that event actually occurs, as in the case of the server failure, it is no longer a risk but becomes an issue that requires immediate management action. Incorrect: The claim that it remains a risk because it was in the risk register is incorrect; the risk register tracks potential events, but once they happen, they must be managed as issues. Incorrect: The suggestion that risks are only positive is false; risks can be threats (negative) or opportunities (positive). Both risks and issues can have negative impacts. Incorrect: The existence of a contingency plan does not define an event as a risk; issues often have pre-planned responses if they were previously identified as risks, but they are still classified as issues once they manifest. Key Takeaway: Risks are proactive and probabilistic (what might happen), while issues are reactive and certain (what has happened).

Correct: In the issue management process, once an issue is identified and its impact is assessed as being outside the project manager’s delegated limits (tolerances), it must be formally recorded in the issue log and escalated to the next level of management, typically the project sponsor. This ensures that the person with the ultimate accountability for the project’s success can decide on the appropriate course of action. Incorrect: Updating the risk register and waiting for a meeting is inappropriate because an issue is a present problem, not a future uncertainty, and critical issues require timely escalation rather than waiting for scheduled meetings. Incorrect: Adjusting the project baseline immediately is incorrect because a project manager does not have the authority to change the baseline when the impact exceeds their delegated tolerances; this requires formal change control and sponsor approval. Incorrect: Instructing the team to work double shifts using contingency might be a potential solution, but if the issue already exceeds the project manager’s authority regarding schedule or cost, they cannot unilaterally implement a recovery plan without escalation. Key Takeaway: Escalation is a vital part of the issue management process used when the resolution of an issue falls outside the project manager’s delegated authority or when the issue impacts the project’s strategic objectives.

Correct: Effective issue management requires that every item in the issue log has a designated owner who is responsible for managing the resolution. Defining specific actions and target dates allows the project manager to track progress and ensures accountability. The log must be updated regularly to reflect the current status and should only be closed once the resolution has been verified as successful. Incorrect: Transferring the entry to the risk register is incorrect because a risk is an uncertain event, whereas an issue is a current problem that has already occurred; while they are related, they are managed in separate documents. Marking the issue as resolved based only on a proposed solution is premature; an issue should only be closed after the solution is implemented and verified. Escalating to a sponsor and removing it from the log is incorrect because escalation does not absolve the project manager of the responsibility to track the issue, and removing it would lead to a loss of audit trail and visibility. Key Takeaway: An issue log is a live document that requires active ownership, clear action plans, and verified closures to ensure project control is maintained.

Correct: Risk appetite is a high-level, qualitative statement describing the types and amount of risk an organization is prepared to seek or accept in pursuit of its objectives. In this scenario, the desire for innovation despite uncertainty is a strategic appetite. Risk tolerance is the measurable and specific level of variation that the organization is willing to accept around a particular objective, such as the specific 50,000 GBP financial limit mentioned. Incorrect: The suggestion that the 50,000 GBP limit is the risk appetite and innovation is a threshold is incorrect because appetite is strategic and broad, while thresholds are specific trigger points. Incorrect: Defining both as risk thresholds is incorrect because a threshold is a specific level of risk exposure at which an action is triggered, whereas these statements describe the broader attitude and specific boundaries of the organization. Incorrect: Reversing the definitions of appetite and tolerance is incorrect because tolerance must be measurable and granular, while appetite reflects the overall organizational culture and strategic intent. Key Takeaway: Risk appetite provides the strategic direction, while risk tolerance provides the operational constraints used to manage project performance.