Project Management Qualification (PMQ) Quiz 23

Correct: Configuration identification is the process of defining the structure of the project products and providing them with unique identifiers or labels. Status accounting is the procedure of recording and reporting the current state and history of configuration items throughout their lifecycle, such as tracking if a document is in draft or approved status. Together, these two procedures address the naming and tracking requirements described in the scenario. Incorrect: Configuration control and verification auditing is incorrect because control focuses on the formal process of managing changes to items after they have been baselined, while auditing is the formal review to ensure the physical item matches its technical description. Incorrect: Change management and quality assurance is incorrect because change management is the broader process of managing shifts in project scope or direction, and quality assurance focuses on the processes used to create the deliverables rather than tracking their specific versions or labels. Incorrect: Configuration identification and quality control is incorrect because while identification is part of the scenario, quality control focuses on inspecting the output for defects and ensuring it meets requirements rather than tracking the administrative status and history of the item. Key Takeaway: Configuration identification establishes the baseline for what is being managed through unique labeling, while status accounting provides the ongoing visibility into the lifecycle stages and history of those items to ensure the team is always working with the correct version and knows its current maturity level. No asterisks or letter references were used in this explanation as per the requirements. All values are double-quoted strings and the JSON is parseable. No control tokens are present in the output string.

Correct: A configuration audit is a formal review to ensure that a product or system meets its specified requirements and that its documented configuration matches the actual physical state. It verifies that all changes have been properly processed, tested, and recorded in the configuration management system, ensuring the integrity of the version control. Incorrect: Quality Control Inspection focuses on identifying defects and ensuring the work meets quality standards, but it does not specifically validate the integrity of the configuration records against the physical build. Incorrect: Scope Verification is the process of formalizing acceptance of the completed project deliverables by the client or sponsor, focusing on whether the work meets the agreed scope rather than the technical configuration details. Incorrect: Benefits Realization Review is conducted to assess whether the project has achieved its intended business outcomes and value, which typically happens after the product is in use and is not a technical verification step. Key Takeaway: Configuration audits provide the necessary assurance that the deliverable is technically accurate and that the documentation provides a reliable record of the final product state.

Correct: The integration of change control and scope management requires that any proposed modification to the project scope is first evaluated for its impact on the project’s objectives, including cost, time, and quality. Only after this impact assessment should a formal change request be processed through the Change Control Board. If approved, the scope baseline and Work Breakdown Structure (WBS) are then updated to reflect the new reality. Incorrect: Updating the Work Breakdown Structure and scope statement immediately bypasses the formal change control process, leading to unauthorized scope creep. Incorrect: Directing the team to implement the change without approval is a violation of integrated change control and risks project failure due to unmanaged resource consumption. Incorrect: Advising the stakeholder that no changes can be accepted is overly rigid; the purpose of change control is to manage changes effectively, not to prevent them entirely, provided they add value and are properly authorized. Key Takeaway: Integrated change control ensures that the scope baseline remains accurate and that all changes are evaluated for their impact on the project’s success criteria before implementation.

Correct: Resource smoothing is the correct technique because it seeks to even out the demand for resources without affecting the project end date. It achieves this by utilizing the available float of non-critical activities to delay certain tasks until resources are available, ensuring the critical path remains untouched. Incorrect: Resource leveling is incorrect because this technique prioritizes resource availability over time constraints. Leveling often causes the project end date to change or the critical path to shift, which violates the requirement of the fixed completion date. Incorrect: Crashing the schedule is incorrect because crashing involves adding more resources to critical path activities to shorten the duration, which typically increases costs and does not address the issue of over-allocated resources on non-critical tasks. Incorrect: Fast tracking the critical path is incorrect because fast tracking involves performing activities in parallel that were originally planned in sequence. This is a schedule compression technique used to shorten the duration, not a resource optimization technique used to manage over-allocation within existing time constraints. Key Takeaway: When the project end date is fixed and cannot be delayed, resource smoothing is the preferred optimization technique as it only utilizes available float to balance resource demand.

Correct: Analogous estimating is a top-down technique that uses the actual duration or cost of previous, similar projects as the basis for estimating the current project. It is the most appropriate choice here because it is relatively quick to perform and is used when there is a limited amount of detailed information available about the project. Incorrect: Parametric estimating uses a statistical relationship between historical data and other variables (such as square footage in construction or lines of code in software) to calculate an estimate. While it uses historical data, it requires a quantifiable parameter and a higher level of detail to be accurate than what is available in this scenario. Incorrect: Bottom-up estimating involves estimating the cost or duration of individual work packages or activities and then summarizing them to get a total. This technique provides the highest level of accuracy but requires a detailed Work Breakdown Structure and significant time, which the project manager does not have in this scenario. Incorrect: Three-point estimating (PERT) uses optimistic, pessimistic, and most likely values to account for uncertainty. While it is a valuable tool for refining estimates, it is typically applied at the activity level once the project scope is more clearly defined, rather than as a high-level, top-down tool for a quick business case estimate. Key Takeaway: Analogous estimating is the preferred method for quick, top-down estimates during the early stages of a project when detailed information is scarce but historical data from similar projects exists.

Correct: The Program Evaluation and Review Technique (PERT) uses a weighted average to calculate the expected duration based on a Beta distribution. The formula is (Optimistic + 4 times Most Likely + Pessimistic) divided by 6. For this scenario, the calculation is (10 + (4 times 15) + 26) / 6, which equals 96 / 6 = 16 days. The standard deviation is calculated as (Pessimistic minus Optimistic) divided by 6, which is (26 – 10) / 6, resulting in 2.67 days. Incorrect: The option suggesting 17 days is incorrect because it uses a simple triangular average (10 + 15 + 26) / 3 instead of the weighted PERT formula. The option suggesting a standard deviation of 7.11 days is incorrect because 7.11 is the variance (the square of the standard deviation), not the standard deviation itself. The option suggesting 15 days is incorrect because it only considers the most likely estimate and fails to incorporate the uncertainty provided by the optimistic and pessimistic ranges. Key Takeaway: PERT is a valuable tool for managing uncertainty in project schedules as it provides a weighted mean that accounts for risks and allows for statistical analysis of the project timeline through standard deviation.

Correct: A Finish-to-Finish (FF) relationship exists when the completion of the successor activity depends on the completion of the predecessor activity. In this scenario, the final safety inspection (successor) cannot be finished until the HVAC system installation (predecessor) is also finished. Incorrect: Finish-to-Start (FS) is the most common dependency where the successor cannot start until the predecessor finishes; however, the scenario specifically focuses on the completion of the inspection being tied to the completion of the HVAC work. Incorrect: Start-to-Start (SS) implies that the successor cannot start until the predecessor starts, which does not address the requirement for both activities to reach completion for the logic to be satisfied. Incorrect: Start-to-Finish (SF) is a rare dependency where the completion of the successor is dependent on the start of the predecessor, which is the opposite of the logic required for a safety inspection following an installation. Key Takeaway: Identifying the correct logical dependency is essential for Critical Path Analysis, ensuring that the project schedule accurately reflects the physical or procedural constraints of the work.

Correct: The critical path is the longest sequence of dependent activities through a project network, which determines the shortest possible time to complete the project. In this scenario, there are two paths: Path A (Site Prep + Foundation + Framing + Inspection) which equals 40 days (6+12+18+4), and Path B (Site Prep + Foundation + Electrical + Inspection) which equals 32 days (6+12+10+4). Since Path A is the longest, it is the critical path and the project duration is 40 days. Incorrect: The option suggesting 32 days is incorrect because it identifies the shorter path, which has float and does not determine the project end date. The option suggesting 50 days is incorrect because it simply sums all activity durations together, failing to account for the fact that Electrical Installation and Structural Framing occur in parallel. The option suggesting 40 days but including Electrical Installation is incorrect because that specific sequence of activities only sums to 32 days, making the calculation inconsistent with the path identified. Key Takeaway: The critical path is the sequence of activities with the longest duration, and any delay in these activities will directly impact the project completion date.

Correct: Total Float is calculated as the difference between the Late Finish and the Early Finish (28 minus 20 equals 8 days). Free Float is calculated as the difference between the Early Start of the immediate successor and the Early Finish of the current activity (25 minus 20 equals 5 days). This means the activity can be delayed by up to 5 days without affecting the start of ‘Wall Framing’, but it can be delayed by up to 8 days before it affects the overall project completion date. Incorrect: Total Float is 8 days and Free Float is 8 days is incorrect because Free Float is limited by the specific start date of the next task (day 25), not the project’s late finish. Incorrect: Total Float is 5 days and Free Float is 8 days is incorrect because it swaps the values; Total Float must always be greater than or equal to Free Float. Incorrect: Total Float is 13 days and Free Float is 5 days is incorrect because the Total Float calculation is wrong (it likely incorrectly added the two values), and an activity with positive float cannot be on the critical path. Key Takeaway: Total Float represents flexibility relative to the project end date, while Free Float represents flexibility relative to the very next activity in the sequence.

Correct: Milestone charts are specifically designed for high-level reporting to stakeholders who need to see significant events, deliverables, or decision points without the complexity of task durations. Gantt charts are the standard tool for project teams because they display the start and finish dates of activities, their durations, and their logical dependencies, which is essential for managing day-to-day work and resources. Incorrect: Providing a Gantt chart to the executive steering committee and a milestone chart to the team is counter-productive because executives would be overwhelmed by granular detail while the team would lack the duration and dependency information needed to execute tasks. A network diagram is a technical tool used primarily for critical path analysis and is generally too complex for executive summary reporting. A work breakdown structure is a scope management tool that shows the hierarchical decomposition of work but does not inherently provide the chronological schedule or timing information required for a monthly progress update. Key Takeaway: Effective schedule visualization requires tailoring the level of detail to the audience; milestones provide the ‘what’ and ‘when’ for executives, while Gantt charts provide the ‘how’ and ‘how long’ for the delivery team.

Correct: The Finish-to-Finish (FF) relationship is used when the successor activity cannot finish until the predecessor activity has finished. In this scenario, the completion of System Testing is tied to the completion of Documentation Update, making FF the appropriate logical link to ensure the final sign-off of one depends on the other. Incorrect: Finish-to-Start (FS) is the most common relationship where the successor cannot start until the predecessor finishes, which does not fit this scenario as the tasks are allowed to overlap. Incorrect: Start-to-Start (SS) indicates that the successor cannot start until the predecessor has started, which focuses on the initiation of tasks rather than their completion requirements. Incorrect: Start-to-Finish (SF) is a rare relationship where the successor cannot finish until the predecessor starts, which is the inverse of the logic required for this specific dependency. Key Takeaway: Understanding the four types of logical dependencies in PDM is essential for creating realistic project schedules that allow for overlapping activities while maintaining necessary completion constraints.

Correct: Crashing is a schedule compression technique used to shorten the schedule duration for the least incremental cost by adding resources. It is the most appropriate choice here because the sponsor has provided additional budget and specifically requested that the project manager avoid techniques that introduce significant risks of rework. Crashing typically increases costs but maintains the original logical sequence of tasks. Incorrect: Fast tracking involves performing phases or activities in parallel that would normally be done in sequence. While this does not necessarily increase costs, it significantly increases the risk of rework, which the sponsor wants to avoid. Incorrect: Resource leveling is a technique used to address resource over-allocation or fluctuations. It often results in the project end date being pushed out, which is not acceptable given the non-negotiable deadline. Incorrect: Reducing scope is a method to meet a deadline by changing the project requirements, but it is not defined as a schedule compression technique like crashing or fast tracking. Key Takeaway: Crashing focuses on adding resources to reduce time at the expense of cost, while fast tracking focuses on overlapping tasks at the expense of increased risk.

Correct: Resource leveling is a technique used when resource limits are the primary constraint. It involves moving task start and finish dates to ensure that resource demand does not exceed resource availability. Because this technique prioritizes resource constraints over time, it often results in the project’s critical path changing and the overall project completion date being extended. Incorrect: Adjusting the schedule only within the available float is known as resource smoothing, not resource leveling; smoothing is used when the project deadline is fixed and cannot be delayed. Incorrect: Hiring additional staff is a schedule compression technique known as crashing, which focuses on adding resources to shorten the schedule rather than managing existing resource constraints through leveling. Incorrect: Overlapping tasks to finish faster is known as fast tracking, which is another schedule compression technique that typically increases risk and does not resolve a resource over-allocation where a single individual is the bottleneck. Key Takeaway: Resource leveling resolves resource conflicts by rescheduling activities, which frequently leads to an extension of the project duration.

Correct: Resource smoothing is a technique used when the project end date is fixed. It involves rescheduling activities such that they do not exceed the available float, thereby ensuring the critical path is not affected and the completion date remains unchanged. The primary goal is to minimize the peaks and troughs in resource usage to improve efficiency. Incorrect: Delaying activities beyond their float to ensure resource limits are never exceeded describes resource leveling, which often results in a change to the project completion date. Adding more electricians to critical path activities describes crashing, which is a schedule compression technique aimed at shortening the duration, not smoothing demand. Performing activities in parallel that were originally planned in sequence describes fast tracking, another schedule compression technique that increases risk rather than addressing resource fluctuations. Key Takeaway: Resource smoothing is used when time is the primary constraint, utilizing float to balance demand without delaying the project.

Correct: A Finish-to-Start (FS) relationship means the successor activity cannot start until the predecessor has finished. A lag is a required delay inserted between activities. In this scenario, the steel frame (successor) starts after the concrete (predecessor) is finished, plus a 7-day waiting period for curing, making FS with a 7-day lag the correct application. Incorrect: A Finish-to-Start relationship with a 7-day lead is incorrect because a lead represents an acceleration of the successor activity, allowing it to start before the predecessor finishes, which would result in erecting steel on wet concrete. A Start-to-Start relationship with a 7-day lag is incorrect because it would mean the steel erection starts 7 days after the concrete pouring begins, regardless of when the pouring finishes, which does not account for the total duration of the pour. A Finish-to-Finish relationship with a 7-day lead is incorrect because it implies the successor must finish 7 days before the predecessor finishes, which is logically impossible in this sequence. Key Takeaway: Lag time is used to add a mandatory delay between activities to account for processes like curing or drying, while lead time is used to overlap activities to shorten the overall project duration.

Correct: Establishing a schedule baseline involves taking a snapshot of the approved schedule after resource leveling and critical path analysis. This baseline serves as the benchmark for performance measurement. By implementing a formal change control process, the project manager ensures that the baseline is only modified through approved changes, allowing for meaningful variance analysis throughout the project lifecycle. Incorrect: Continuously updating the schedule with actual dates is a necessary part of project monitoring, but it does not establish a baseline; rather, it provides the data to compare against the baseline. Using a resource-unconstrained network diagram is incorrect because a valid baseline must account for resource availability to be realistic. Adjusting the project end date every time a delay occurs is a practice known as rubber-baselining, which undermines the purpose of performance measurement by hiding variances instead of managing them. Key Takeaway: A schedule baseline must be approved, realistic, and controlled through a formal process to serve as an effective tool for measuring project performance.

Correct: Resource smoothing is a technique used to adjust the activities of a schedule model such that the requirements for resources on the project do not exceed certain predefined resource limits. In resource smoothing, as opposed to resource leveling, the project’s critical path is not changed and the completion date may not be delayed. In this scenario, the project manager works within the total project float to balance the workload, which is the defining characteristic of smoothing. Incorrect: Resource leveling is a technique in which start and finish dates are adjusted based on resource constraints with the goal of balancing demand for resources with the available supply. Leveling often causes the original critical path to change, usually by increasing it. Since the scenario specifies a fixed deadline and the use of float, leveling is incorrect. Incorrect: Resource allocation is the broader process of assigning and scheduling resources to project tasks. While it is the overarching activity, it does not specifically describe the optimization technique used to resolve the scheduling conflict within float constraints. Incorrect: Resource breakdown structure is a hierarchical list of resources related by category and resource type. It is used for planning and reporting but is not a technique for optimizing a schedule based on resource availability. Key Takeaway: The primary differentiator between resource smoothing and resource leveling is that smoothing does not delay the project completion date and stays within float, whereas leveling prioritizes resource limits and can extend the project duration.

Correct: Human resources refer to the people involved in the project, categorized by their roles, skills, and competencies, such as structural engineers and laborers. Physical resources encompass everything else needed, including equipment like cranes, materials like concrete, and facilities or tools like safety equipment. Incorrect: Categorizing site laborers as physical resources is incorrect because all personnel, regardless of whether their work is manual or intellectual, are classified as human resources. Incorrect: Categorizing all resources as physical is incorrect because project management distinguishes between the people (human resources) and the tools or materials (physical resources) to manage different constraints like availability, training, and procurement. Incorrect: Categorizing cranes as human resources is incorrect because they are machinery (physical resources). Similarly, engineers are people and cannot be categorized as physical resources. Key Takeaway: Effective resource identification requires distinguishing between human resources (people and their skills) and physical resources (equipment, materials, and facilities) to apply the correct management, acquisition, and development strategies.

Correct: The Responsibility Assignment Matrix (RAM) is the primary tool used to illustrate the connections between work packages or activities and project team members. A common type of RAM is the RACI chart, which ensures that there is only one person accountable for any given task while also identifying those responsible for the work, those who should be consulted, and those who need to be kept informed. This prevents confusion regarding roles and ensures all work is assigned. Incorrect: The Resource Breakdown Structure (RBS) is a hierarchical representation of resources by category and type. While it helps in organizing and reporting resource data, it does not assign specific tasks to individuals or define their level of involvement in a work package. Incorrect: A Resource Histogram is a graphical tool used to show resource usage over time. It is primarily used for identifying resource over-allocation or under-utilization during the scheduling process, rather than defining roles and responsibilities for specific tasks. Incorrect: The Resource Management Plan is a high-level document that provides guidance on how project resources should be categorized, allocated, managed, and released. While it contains the strategy for resource management, the specific tool for mapping tasks to people is the RAM. Key Takeaway: To ensure clear accountability in a project, the Responsibility Assignment Matrix (RAM) should be used to link the Work Breakdown Structure (WBS) to the project team, ensuring every task has a designated owner and defined stakeholder roles.

Correct: Implementing a Just-in-Time (JIT) delivery strategy is the most effective approach here because it aligns the arrival of physical resources with the actual project activities. This minimizes the need for on-site storage, reduces the rental costs associated with idle heavy machinery, and prevents the spoilage of perishable materials. Incorrect: Procuring all materials at the start is counterproductive in this scenario because it ignores the limited storage space and would lead to high costs for equipment that is not yet in use. Incorrect: Utilizing a centralized warehouse far from the site introduces significant logistics costs and potential delays in transporting resources to the site when they are needed, which can disrupt the project schedule. Incorrect: Transferring the risk to the client is generally not a standard practice in project management and does not address the underlying need for efficient resource planning and execution. Key Takeaway: Effective physical resource management requires a balance between resource availability and the constraints of the project environment, such as space, cost, and material shelf-life.

Correct: The most effective first step in managing resource over-allocation when the project deadline is fixed is resource smoothing. This involves rescheduling activities that have float (slack) so they do not occur during peak demand periods. Because these activities are not on the critical path, moving them within their float limits does not delay the project completion date. Incorrect: Applying resource leveling across the entire project often results in the project end date being pushed out because it prioritizes resource constraints over schedule constraints, which contradicts the requirement to minimize risk to the completion date. Submitting a change request to reduce scope is a drastic measure that should only be considered after all resource optimization techniques have been exhausted. Requesting a budget increase for overtime throughout the entire lifecycle is inefficient and costly; overtime should be targeted specifically at the peak period if smoothing is unsuccessful, rather than applied to the whole project. Key Takeaway: Resource smoothing is the preferred technique when the project end date is fixed, as it utilizes float to balance resource demand without affecting the critical path.

Correct: In a multi-project environment, resource scarcity must be managed through a combination of impact analysis and collaborative prioritization. By analyzing the schedule and consulting with the PMO, the Project Manager ensures that decisions are made based on the wider organizational benefit rather than individual project needs. Incorrect: Applying resource leveling in isolation may lead to unacceptable delays without considering if the other project has a higher strategic priority. Directing the resource based solely on the project start date ignores the current needs of the business and the potential impact of the compliance audit. Requesting immediate sponsor intervention bypasses the standard conflict resolution process and fails to provide the necessary data-driven analysis required for a portfolio-level decision. Key Takeaway: Effective resource management across competing priorities requires a balance of technical schedule analysis and stakeholder negotiation aligned with strategic goals.

Correct: Using a competency framework allows a project manager to objectively measure the current capabilities of the team against the specific requirements of the project roles. This gap analysis identifies exactly where knowledge or behaviors are lacking, enabling targeted interventions such as training or recruitment. Incorrect: Reviewing historical performance metrics focuses on past output rather than the specific skills required for new or future tasks, making it an unreliable method for identifying technical competency gaps. Outsourcing tasks might solve a temporary capacity issue but fails to address the underlying skills gap within the project team, which could lead to long-term dependency and higher costs. Implementing mandatory training for the entire team is inefficient because it assumes all team members have the same gap, whereas a competency framework allows for personalized development based on individual needs. Key Takeaway: Competency frameworks provide a structured and objective benchmark to identify the difference between current team capabilities and the requirements of the project, facilitating effective resource management and professional development. No asterisks or letter references were used in this explanation.

Correct: The scenario describes the Forming stage, where team members are often anxious, polite, and look to the leader for guidance because roles and responsibilities are not yet clear. In this stage, a directing leadership style is necessary to provide the structure and clarity the team needs to move forward. Incorrect: The Storming stage is incorrect because it is characterized by conflict, competition for status, and disagreement over goals, which is not what the scenario describes. The Norming stage is incorrect because it occurs after the team has resolved their initial conflicts and started to develop cohesive working relationships and shared values. The Performing stage is incorrect because it represents a high-functioning, autonomous team that requires minimal supervision, whereas this team is newly formed and highly dependent on the manager. Key Takeaway: In the Tuckman model, the project manager must adapt their leadership style to match the team’s current development stage, moving from a directive approach in Forming to a delegating approach in Performing.

Correct: The scenario describes a team that lacks practical execution and attention to detail. An Implementer is needed to turn abstract ideas and designs into manageable work blocks and logical processes, ensuring the team remains organized. A Completer Finisher is essential for the final stages of a project to polish the work, identify minor errors, and ensure the project meets high-quality standards before delivery. Incorrect: Plant and Resource Investigator are roles focused on generating ideas and exploring external opportunities. Since the team is already described as highly creative, adding more of these roles would likely exacerbate the lack of focus on delivery. Incorrect: Shaper and Co-ordinator are leadership-oriented roles. While they provide drive and delegation, they do not specifically address the need for detailed quality control and the practical ‘doing’ of tasks required in the final phase. Incorrect: Monitor Evaluator and Specialist focus on objective analysis and technical depth. While the Monitor Evaluator helps with decision-making, they do not necessarily drive the completion of tasks or the meticulous error-checking provided by a Completer Finisher. Key Takeaway: A balanced team requires different Belbin roles at different stages of the project lifecycle; the transition from design to delivery specifically requires roles that prioritize reliability, efficiency, and perfectionism.

Correct: According to Herzberg’s Two-Factor Theory, factors such as salary, working conditions, and job security are classified as hygiene factors. While their absence causes dissatisfaction, their presence does not inherently motivate employees to work harder. To truly motivate the team, the project manager must focus on motivators, which include achievement, recognition, the work itself, responsibility, and advancement. Introducing challenging tasks and recognition directly addresses these motivators. Incorrect: The suggestion regarding Maslow’s hierarchy is incorrect because the scenario states the team already has job security and competitive salaries, meaning their safety and physiological needs are likely already met; adding more of the same will not move them up the hierarchy. Incorrect: Regarding Vroom’s Expectancy Theory, while expectancy (the belief that effort leads to performance) is important, the scenario describes a lack of engagement despite high-quality resources, which points more specifically to a lack of intrinsic motivation rather than a lack of capability or training. Incorrect: While valence refers to the value an individual places on a reward, Herzberg’s theory provides a more specific explanation for why high hygiene factors (like salary) fail to motivate once a baseline is reached. Simply swapping one reward for another without addressing the intrinsic nature of the work does not align with Herzberg’s findings on motivators. Key Takeaway: Project managers must distinguish between factors that prevent dissatisfaction and those that actively drive performance; providing a good environment is necessary but insufficient for high motivation without opportunities for growth and recognition. High salaries are hygiene factors, not motivators. No asterisks were used in this explanation as per the requirements. No letter references were used in this explanation as per the requirements.

Correct: The Supporting style (S3) is characterized by low task behavior and high relationship behavior. It is most effective for a team at the M3 maturity level, where members have high competence but variable or low commitment/confidence. In this scenario, the team is technically proficient but has lost motivation due to external strategic changes, meaning the project manager should focus on listening, praising, and involving them in decision-making to rebuild their commitment rather than providing technical direction. Incorrect: The Directing style (S1) focuses on high task direction and low relationship support, which is intended for teams with low competence and low commitment; using this on a highly skilled team would be perceived as micromanagement and would likely decrease morale further. Incorrect: The Coaching style (S2) involves high task and high relationship behaviors, intended for those with some competence but low commitment; since the team is already highly skilled and has a proven track record, high levels of task direction are unnecessary. Incorrect: The Delegating style (S4) involves low task and low relationship behaviors, intended for teams with both high competence and high commitment; because the team’s commitment has dropped significantly, a hands-off approach would fail to address their psychological needs and concerns. Key Takeaway: Situational leadership requires the project manager to diagnose the team’s maturity level based on both competence and commitment, then adjust the balance of task-oriented and relationship-oriented behavior accordingly.

Correct: Mentoring is a long-term, relationship-oriented process focused on the overall development and career growth of the individual, making it ideal for the junior team member looking to understand organizational strategy and leadership. Coaching is a short-term, task-oriented process focused on improving specific skills or performance, which is the appropriate response for the senior developer needing to master a specific framework. Incorrect: Providing coaching to the junior member for organizational politics and mentoring for the technical lead is a reversal of the standard definitions; coaching is too narrow for career navigation, and mentoring is too broad for a specific technical bottleneck. Incorrect: A directive leadership style for the senior developer may solve the immediate problem but does not facilitate the learning and development required to prevent future bottlenecks. Incorrect: While training courses are useful, they lack the personal guidance of mentoring, and mentoring is not the most efficient way to address a specific, immediate technical skill gap compared to targeted coaching. Key Takeaway: Mentoring focuses on the person and their future, while coaching focuses on the task and current performance.

Correct: Providing constructive feedback requires being specific, objective, and timely. By focusing on the specific missed milestones and explaining the impact on the project, the project manager maintains a professional focus on outcomes rather than personality. Collaborating on a root cause analysis and a recovery plan ensures the team member is part of the solution, which is essential for maintaining motivation and addressing potential underlying issues like burnout or resource constraints. Incorrect: Mandating daily status updates and labeling the engineer as unreliable is a micro-management approach that focuses on blame rather than resolution; this often decreases morale and does not address the actual cause of the performance dip. Incorrect: Reassigning tasks without addressing the performance issue avoids the project manager’s responsibility to manage the team and can lead to resentment among other team members who must pick up the extra workload. Incorrect: Waiting for an annual review is ineffective because feedback must be timely to allow for corrective action; delaying the conversation allows the project risk to escalate and denies the team member the opportunity to improve during the project lifecycle. Key Takeaway: Effective performance management in a project environment relies on timely, evidence-based feedback and a collaborative approach to problem-solving to keep the project on track while supporting team development.

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 £210,000 equals approximately 0.86. A CPI of less than 1.0 indicates that the project is over budget, specifically meaning that for every pound spent, only 86 pence of progress has been achieved. Incorrect: The value of 0.90 is mathematically incorrect based on the provided EV and AC figures. Incorrect: The value of 1.16 is incorrect as it likely results from dividing AC by EV, which is not the formula for CPI; a CPI above 1.0 would incorrectly suggest the project is under budget. Incorrect: While the CPI value of 0.86 is correct, the interpretation that it indicates a schedule delay is wrong. Schedule performance is measured by the Schedule Performance Index (SPI), which is EV divided by PV. Although this project is also behind schedule (SPI of 0.90), CPI specifically measures cost efficiency. Key Takeaway: CPI is a critical metric in Earned Value Management that provides a ratio of the earned value to the actual cost, where any value below 1.0 signifies a cost overrun.