Project Management Qualification (PMQ) Quiz 42

Correct: Implementing a formal change control process is the most effective way to manage scope. It ensures that every change is analyzed for its impact on the project constraints, allowing the project manager and stakeholders to make informed decisions rather than allowing scope to grow unchecked. Incorrect: Instructing the team to stop work without a discussion may damage stakeholder relationships and ignore potentially valuable changes that could be handled through proper channels. Incorrect: Increasing the contingency reserve does not address the root cause of scope creep and may actually encourage more undocumented changes, leading to further instability. Incorrect: Accepting the request and removing other features without a formal impact assessment or approval process is a reactive approach that bypasses the necessary governance required for project success. Key Takeaway: Scope creep is best managed through a robust change control system that provides transparency and ensures all modifications to the project scope are justified and resourced.

Correct: Status Accounting is the administrative task of recording and reporting the status of configuration items. It provides a continuous record of the configuration, including the history of changes and the current version, which is exactly what the stakeholder is requesting. Incorrect: Configuration Identification involves defining the scope, naming conventions, and unique identifiers for configuration items at the start of the process, but it does not handle the ongoing reporting of version history. Incorrect: Configuration Verification and Audit is a process used to ensure that the physical deliverable matches the functional and administrative requirements defined in the documentation; it is a check rather than a reporting stream. Incorrect: Configuration Control is the process of evaluating, approving, or rejecting changes to configuration items, but it is not the specific function dedicated to maintaining the historical records and status reports of those items. Key Takeaway: Status Accounting acts as the memory of the configuration management system, ensuring that the status and history of every configuration item are documented and accessible.

Correct: Configuration identification is the process of defining the scope of configuration items and assigning them unique identifiers, such as the numbering system mentioned in the scenario. Status accounting is the process of recording and reporting the status of configuration items throughout their lifecycle, including their current approval state and version history. Incorrect: Configuration auditing and change control are incorrect because auditing involves formal reviews to ensure the physical item matches the documentation, while change control is the formal process for requesting and approving modifications. Incorrect: Configuration verification and baseline management are incorrect because verification is the check to ensure a product meets its design, and baseline management refers to the formal approval of a set of configuration items at a specific point in time. Incorrect: Change request processing and impact analysis are incorrect because these are specific steps within the change control process used to evaluate the consequences of a proposed change rather than identifying or tracking the items themselves. Key Takeaway: Configuration identification provides the foundation by naming and labeling items, while status accounting provides the ongoing visibility into the current state and history of those items.

Correct: A physical configuration audit is a formal examination of the ‘as-built’ configuration of a deliverable against its technical documentation. Its primary purpose is to ensure that the physical product matches the configuration records and that all components are correctly identified and accounted for. Incorrect: A functional configuration audit focuses on whether the deliverable meets the performance and functional requirements specified in the documentation, rather than the physical build itself. Incorrect: Quality assurance audits are focused on the processes and procedures used to create the deliverables, rather than the deliverables themselves. Incorrect: Scope verification (or Validate Scope) is the process of formalizing acceptance of the completed project deliverables by the stakeholders, which usually occurs after the configuration audits have confirmed the product’s integrity. Key Takeaway: Configuration management involves two types of audits: functional (performance-based) and physical (build-based) to ensure the product is exactly what was intended and documented.

Correct: The integration of change control and scope management requires a structured approach where any deviation from the baseline is first evaluated for its impact on cost, time, and quality. Once the impact is understood, a formal change request must be processed through the change control board or the designated authority. If approved, the scope management documents, including the scope statement and work breakdown structure, must be updated to reflect the new baseline. This ensures that the project remains controlled and that all documentation is aligned. Incorrect: Updating the work breakdown structure and scope statement immediately bypasses the formal change control process, which can lead to unauthorized work and resource mismanagement. Implementing the change first and documenting it later is a reactive approach that undermines the purpose of a change control system and risks project failure due to unmanaged impacts. Refusing the change outright without evaluation is poor stakeholder management and ignores the fact that change control is designed to manage necessary changes, not simply to prevent them. Key Takeaway: Effective scope management relies on a robust change control process to ensure that all changes to the baseline are evaluated, authorized, and documented before implementation to maintain project integrity and alignment with objectives.

Correct: Fast tracking is a schedule compression technique where activities or phases normally performed in sequence are performed in parallel for at least a portion of their duration. In this scenario, overlapping the design and development phases allows the project to recover time without increasing the budget, though it significantly increases the risk of rework if the design changes after development has started. Incorrect: Crashing involves adding resources to shorten the duration of activities on the critical path, which typically increases costs and therefore violates the fixed budget constraint mentioned in the scenario. Incorrect: Resource leveling is a resource optimization technique that adjusts start and finish dates based on resource constraints; it usually results in the project duration increasing rather than decreasing. Incorrect: Resource smoothing is used to ensure resource requirements do not exceed predefined limits by delaying non-critical activities within their float. Since the activity in the scenario is on the critical path, it has no float, and smoothing would not be effective for schedule compression. Key Takeaway: When schedule recovery is required without additional funding, fast tracking is the primary technique used, but it requires careful management of the increased risk of rework.

Correct: Parametric estimating involves using a statistical relationship between historical data and other variables to calculate an estimate for activity parameters such as cost or duration. In this scenario, the project manager used a specific unit rate (meters of cable per day) derived from historical data to calculate the total duration, which is the hallmark of parametric modeling. Incorrect: Analogous estimating is a technique that uses the actual duration or cost of a previous, similar project as the basis for estimating the current project. While it uses historical data, it does not typically involve the use of a statistical unit rate or mathematical scaling to the same degree of precision as parametric estimating. Three-point estimating is incorrect because it requires the use of three different estimates (optimistic, pessimistic, and most likely) to determine a range or a weighted average, which was not performed here. Bottom-up estimating is incorrect because it involves estimating the duration of individual work packages or activities at the lowest level of detail and then aggregating them upward, rather than applying a high-level production rate to a total quantity. Key Takeaway: Parametric estimating is highly dependent on the quality of the historical data and the scalability of the model used, offering higher accuracy than analogous estimating when the underlying data is reliable.

Correct: The PERT (Beta distribution) formula is calculated as (Optimistic + 4 x Most Likely + Pessimistic) divided by 6. In this scenario, the calculation is (10 + (4 x 15) + 26) / 6, which equals 96 / 6 = 16 days. This method is preferred in project management because it weights the most likely estimate four times more heavily than the optimistic or pessimistic extremes, leading to a more realistic expectation than a simple average. Incorrect: The option suggesting 17 days uses the triangular distribution formula (Optimistic + Most Likely + Pessimistic) / 3, which does not apply the PERT weighting. Incorrect: The option suggesting 16 days is the worst-case scenario is incorrect because the pessimistic estimate of 26 days is the worst-case scenario; 16 is a weighted average. Incorrect: The option suggesting 15 days only considers the most likely estimate and ignores the uncertainty and risk represented by the optimistic and pessimistic values. Key Takeaway: PERT (Beta distribution) provides a weighted average that emphasizes the most likely outcome while still accounting for the range of uncertainty in an estimate.

Correct: The Finish-to-Finish (FF) relationship is used when the completion of the successor activity depends on the completion of the predecessor activity. In this scenario, while the activities can overlap, the System Integration Testing cannot be finalized until the Security Audit is finished, which perfectly matches the FF logic. Incorrect: Finish-to-Start (FS) is incorrect because it would imply that the testing cannot even begin until the audit is completely finished, which contradicts the scenario’s mention of simultaneous work. Start-to-Start (SS) is incorrect because it only constrains the beginning of the activities, not their completion; it would not ensure that the testing waits for the audit to finish before concluding. Start-to-Finish (SF) is incorrect as it describes a relationship where the successor cannot finish until the predecessor starts, which is a rare logic type and does not apply to the need for two activities to finish in relation to one another. Key Takeaway: Logical dependencies define the sequence of work; Finish-to-Finish is specifically used when the end of one task is tied to the end of another, often allowing for parallel execution while ensuring a synchronized conclusion.

Correct: The critical path is defined as the longest sequence of dependent activities through a project network, which determines the shortest possible duration for the project. In this scenario, there are two main paths through the network. The first path consists of Site Preparation, Foundation, Framing, Electrical, and Final Inspection, totaling 47 days (6+12+15+10+4). The second path consists of Site Preparation, Foundation, Framing, Plumbing, and Final Inspection, totaling 45 days (6+12+15+8+4). Since the path through Electrical is the longest, it is the critical path. Incorrect: The option involving Plumbing and 45 days is incorrect because it represents a shorter path with 2 days of float; it does not drive the project end date. The option totaling 55 days is incorrect because it incorrectly sums parallel activities (Electrical and Plumbing) rather than identifying the longest single sequence. The option totaling 43 days is incorrect because it fails to include the Final Inspection activity, which is a required step to complete the project scope. Key Takeaway: To find the critical path, identify all possible sequences of activities from start to finish and select the one with the longest total duration. This path has zero float, meaning any delay to 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 (22 minus 15 equals 7). Free Float is calculated as the difference between the Early Start of the successor activity and the Early Finish of the current activity (18 minus 15 equals 3). This means the activity can be delayed by 3 days before it impacts the ‘Database Coding’ task, and by 7 days before it impacts the overall project completion date. Incorrect: The option suggesting Total Float is 3 and Free Float is 7 incorrectly swaps the definitions and formulas for the two types of float; furthermore, activities with positive float are not on the critical path. Incorrect: The option suggesting Total Float is 12 and Free Float is 8 uses incorrect mathematical calculations; a delay of 10 days would exceed the actual Total Float of 7, causing a project delay. Incorrect: The option suggesting both floats are 7 days correctly identifies Total Float but fails to calculate Free Float correctly based on the successor’s start date; additionally, an activity with positive float does not immediately delay the project completion. Key Takeaway: Total Float represents the amount of time an activity can be delayed without delaying the project finish date, while Free Float represents the amount of time an activity can be delayed without delaying the early start of its immediate successor.

Correct: Milestone charts are specifically designed for high-level reporting to stakeholders who do not need to see the intricacies of every task. They highlight the completion of major deliverables or the reaching of significant stages, making them perfect for steering committees. Incorrect: A detailed Gantt chart provides too much granular information, which can overwhelm senior stakeholders and distract from the high-level status. Incorrect: A network diagram is a technical tool used for planning logic and identifying the critical path; it is not a progress visualization tool suitable for executive summaries. Incorrect: A resource histogram focuses on the utilization of people or equipment rather than the achievement of project milestones or schedule progress. Key Takeaway: The selection of a schedule visualization tool must be tailored to the audience; use milestone charts for executive summaries and Gantt charts for tactical project management.

Correct: The scenario describes two specific dependencies. The first, where Activity B starts 3 days after Activity A starts, is a Start-to-Start (SS) relationship with a 3-day lag. Lag is a delay in the successor activity. The second, where Activity C cannot finish until 5 days after Activity B finishes, is a Finish-to-Finish (FF) relationship with a 5-day lag. Incorrect: The option suggesting a Finish-to-Start with a lead is incorrect because a lead accelerates the successor activity relative to the predecessor’s completion, whereas the scenario links the start of B to the start of A. Incorrect: The option involving Start-to-Finish is incorrect because Start-to-Finish implies the completion of the successor is dependent on the start of the predecessor, which does not match the requirement that C finishes after B finishes. Incorrect: The option suggesting Finish-to-Finish for the first relationship and a lead for the second is incorrect because it misidentifies the trigger points (start vs finish) and uses a lead (acceleration) instead of a lag (delay). Key Takeaway: In PDM, Start-to-Start relationships link the initiations of activities, while Finish-to-Finish links their completions. Lag is used to represent a required delay between these points.

Correct: Fast tracking is a schedule compression technique where activities or phases normally done in sequence are performed in parallel for at least a portion of their duration. This technique is preferred when the budget is fixed because it typically does not involve additional costs, although it does increase project risk and the potential for rework. Incorrect: Crashing involves adding resources to the critical path to shorten the duration, which almost always results in increased costs, making it unsuitable when no additional budget is available. Incorrect: Resource leveling is a technique used to address resource over-allocation and often results in the project schedule being extended rather than compressed. Incorrect: Applying a lag actually adds a delay between activities, which would further extend the project schedule rather than shortening it. Key Takeaway: When schedule compression is required without increasing costs, fast tracking is the primary technique to consider, provided the project can tolerate the increased risk of rework.

Correct: Resource leveling is a technique used to manage resource constraints by adjusting the project schedule. When resource availability is limited and cannot be increased, leveling prioritizes the resource limits over the schedule, which frequently results in the project’s critical path changing and the completion date being extended. Incorrect: Resource smoothing is used when the project end date is fixed and cannot be delayed; it only optimizes resource usage within the available float of activities. Incorrect: Fast tracking is a schedule compression technique that involves performing activities in parallel. This typically increases resource demand during the overlap period rather than resolving a resource shortage. Incorrect: The description of using float to keep the end date unchanged describes resource smoothing, not resource leveling. Resource leveling specifically addresses situations where the resource limit is the primary constraint, even at the expense of the timeline. Key Takeaway: Resource leveling is the appropriate choice when resource limits are fixed and the schedule is flexible, whereas resource smoothing is used when the schedule is fixed and resource optimization is required within existing float.

Correct: Resource smoothing is a technique used when the project end date is the primary constraint. It involves rescheduling non-critical activities within their total and free float to even out the resource demand over time. This minimizes the peaks and troughs without affecting the critical path or the project completion date. Incorrect: Delaying activities beyond their float to ensure resource demand never exceeds capacity describes resource leveling. Unlike smoothing, leveling can change the critical path and delay the project finish date. Incorrect: Adding more resources to critical path activities to shorten the duration is known as crashing. This is a schedule compression technique, not a resource optimization technique for smoothing demand. Incorrect: Performing activities in parallel that were originally planned in sequence is known as fast tracking. While this is a schedule compression technique, it does not address the smoothing of resource fluctuations. Key Takeaway: Resource smoothing is time-constrained, meaning it optimizes resource usage without extending the project duration by utilizing available float.

Correct: A lag is a delay in the successor activity, which is required for the concrete to cure for 4 days after Activity A finishes before Activity B can start. A lead is an acceleration of the successor activity, allowing Activity D to start 2 days before Activity C is finished. Both are applied to the standard finish-to-start logical relationship to modify the timing of the successor. Incorrect: Applying a 4-day lead to the foundation would mean starting the steel frame before the concrete is poured, which is physically impossible, and a 2-day lag on the drywall would delay it further rather than starting it early. Incorrect: Using a start-to-start relationship with a 4-day lag for the foundation does not account for the duration of the pour itself, only its start date, which is risky in construction logic. Incorrect: Start-to-finish relationships are rarely used in project management and do not apply to the logic of overlapping sequential tasks like wiring and drywall. Key Takeaway: Lag time adds a required delay between activities, while lead time allows for an overlap by starting a successor activity before its predecessor is fully complete.

Correct: The schedule baseline is a controlled document that serves as the approved version of the project schedule. When a significant event occurs that impacts the critical path and completion date, the project manager must first assess the impact and look for ways to mitigate the delay (such as crashing or fast-tracking). If the delay is unavoidable, a formal change request must be processed through the integrated change control system. Only after formal approval can the baseline be updated to reflect the new reality, ensuring that future performance measurement is based on achievable targets. Incorrect: Updating the schedule baseline immediately without formal approval bypasses the project’s governance and change control procedures, which undermines the integrity of the baseline. Incorrect: Ignoring the delay and reporting against an unachievable baseline provides misleading data and fails to address the underlying project management need to manage stakeholder expectations and project recovery. Incorrect: Management reserves are typically used for unforeseen risks and their application usually requires high-level approval; furthermore, schedule baselines are never adjusted automatically as they require a formal review of the impact on all project constraints. Key Takeaway: A schedule baseline is a fixed reference point used to measure performance; it can only be changed through formal change control procedures to ensure it remains a valid and approved tool for performance measurement.

Correct: Resource smoothing is the 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. The primary constraint in smoothing is the project completion date; therefore, the technique only delays activities within their free and total float to avoid affecting the critical path. In this scenario, the project manager specifically used the available float to ensure the end date remained unchanged, which is the hallmark 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. Unlike smoothing, leveling often causes the original critical path to change and usually results in a delay to the project completion date. Incorrect: Resource breakdown structure analysis refers to the hierarchical representation of resources by category and type, which is used for planning and reporting but is not an optimization technique for resolving scheduling conflicts. Incorrect: Fast tracking is a schedule compression technique where activities or phases normally done in sequence are performed in parallel for at least a portion of their duration. This scenario describes delaying an activity to resolve a resource conflict, not overlapping activities to shorten the duration. Key Takeaway: Use resource smoothing when the project deadline is fixed and you must optimize resources within the available float; use resource leveling when resource limits are the priority, even if it means extending the project timeline.

Correct: Effective resource categorization involves distinguishing between human resources based on their skills, roles, and competencies, and physical resources based on their nature, such as whether they are consumable (materials) or non-consumable (equipment and facilities). Grouping developers by technical competency and infrastructure as physical assets allows for better planning of availability, utilization, and scheduling. Incorrect: Listing all resources under a single operational expenditure category is a financial accounting method rather than a resource management technique; it fails to account for the different management needs of people versus equipment. Incorrect: Prioritizing identification based on seniority or purchase price is a flawed approach because it ignores the functional requirements of the project and the actual skills needed to complete tasks. Incorrect: Categorizing all resources as consumable is incorrect because human resources and facilities are generally non-consumable assets that are utilized over time rather than used up like raw materials. Key Takeaway: Resource identification and categorization must account for the distinct characteristics of human resources (skills and roles) and physical resources (equipment and materials) to ensure the Resource Breakdown Structure accurately reflects the project’s needs and constraints.

Correct: A resource management plan must define the roles and responsibilities of team members to ensure accountability, provide an organizational chart to show reporting relationships, and include a staff release plan to manage the smooth transition of personnel off the project when their work is complete. Incorrect: Including personal contact details like home addresses is a matter of corporate HR records and privacy policy rather than project resource management planning. Incorrect: While resource costs influence the budget, the resource management plan focuses on the management and allocation of people rather than being the primary document for detailed financial line items and billing rates. Incorrect: It is impossible to guarantee zero staff turnover through a management plan, as turnover is often beyond the project manager’s control; the plan should instead focus on how to manage and mitigate such risks. Key Takeaway: The resource management plan is a strategic document that outlines how human and physical resources will be identified, acquired, managed, and released to support project objectives.

Correct: Effective physical resource management requires proactive problem-solving when supply chain issues arise. Performing a schedule impact analysis allows the project manager to understand the true delay to the project completion. Exploring temporary facilities or alternative sequencing demonstrates the ability to mitigate risks to physical assets and maintain momentum. Incorrect: Procuring standard commercial units is likely to fail because they will not meet the technical specifications required for a medical research facility, leading to quality and performance issues. Incorrect: Delivering sensitive laboratory equipment to an unconditioned warehouse risks damaging the equipment due to lack of climate control, which is a failure to protect physical resources. Incorrect: Suspending all site activities and automatically extending the deadline is a passive approach that ignores the possibility of re-sequencing other work packages that do not depend on the climate control units. Key Takeaway: Physical resource management involves not only procurement but also the strategic mitigation of supply chain disruptions through contingency planning and impact assessment.

Correct: Resource leveling is the process of addressing resource over-allocation by adjusting the schedule. When resources are required beyond their capacity (240 hours required vs 160 available) and the activities are on the critical path, leveling will move these activities to a later date, thereby extending the project finish date. Incorrect: Resource smoothing is used when the project end date cannot be delayed; however, it only works if there is available float to delay activities within. Since the scenario specifies the tasks are on the critical path, smoothing is not a viable option to resolve a capacity deficit. Incorrect: The histogram shows the project is over-loaded, not under-loaded, as the demand exceeds the available capacity. Incorrect: Total float is a characteristic of the network logic and activity durations; a project manager cannot simply increase float for critical path activities to resolve resource constraints without changing the logic or durations. Key Takeaway: Resource histograms are essential for identifying resource over-allocation, and leveling critical path activities to match resource limits will almost always result in a schedule extension.

Correct: In a matrix environment where resources are shared, the most effective way to handle scarcity is through negotiation and prioritization based on organizational goals. By collaborating with the other project manager and the resource manager, the project manager ensures that the resource is assigned where they can provide the most value to the organization, balancing urgency and strategic importance. Incorrect: Applying resource leveling in isolation ignores the needs of the other project and the wider organization; it may result in an unnecessary delay if the other project is actually lower priority. Escalating immediately to a sponsor is considered a failure of the project manager’s negotiation responsibilities and should only be done after internal negotiation attempts have failed. Requesting overtime is a short-term solution that risks staff burnout, increased costs, and potential quality issues, and it does not address the fundamental conflict of competing priorities. Key Takeaway: Managing resource scarcity requires a holistic view of the project portfolio and collaborative negotiation to ensure that resource allocation aligns with the organization’s strategic objectives.

Correct: Utilizing a competency framework provides a structured and objective way to define the knowledge, skills, and behaviors required for specific project roles. By performing a gap analysis against this framework, the project manager can identify exactly where the team falls short and develop a targeted plan for professional development or resource acquisition. Incorrect: Reviewing past performance appraisals focuses on historical performance rather than the specific future competencies required for a new project phase. While useful for general assessment, it does not provide a structured map of skills needed for implementation. Requesting budget for contractors before assessing the internal team is premature and may lead to unnecessary costs; a project manager should first understand the internal capabilities before deciding on outsourcing. Facilitating team-building exercises addresses team dynamics and soft skills but does not identify or solve specific technical or leadership competency gaps required for the project’s technical success. Key Takeaway: Competency frameworks are essential tools for identifying skills gaps, allowing project managers to objectively assess current capabilities against the requirements of the project and take proactive steps to bridge those gaps through training or recruitment. This ensures the team is fit for purpose throughout the project lifecycle.

Correct: The scenario describes the Storming stage, which is characterized by conflict, competition for status, and questioning of leadership or processes. During this phase, the project manager must adopt a coaching style, helping the team navigate interpersonal issues, clarifying the project goals, and ensuring that roles are well-defined to move the team toward the next stage. Incorrect: The Forming stage is the initial phase where team members are generally polite, cautious, and observant; the scenario describes active conflict which is beyond this stage. Incorrect: The Norming stage occurs when the team has resolved its conflicts and begins to develop a cohesive way of working; the scenario indicates that the team is still experiencing friction and has not yet reached a state of harmony. Incorrect: The Performing stage is reached when the team is highly functional, autonomous, and efficient; the team in the scenario is currently struggling with basic cooperation and methodology alignment. Key Takeaway: The Tuckman model requires project managers to adapt their leadership style based on the team’s maturity, moving from a directing style in Forming to a coaching style in Storming, a supporting style in Norming, and a delegating style in Performing.

Correct: The scenario identifies two specific gaps: a lack of systematic organization and a lack of attention to detail in final deliverables. The Implementer is an action-oriented role characterized by the ability to turn ideas and concepts into practical, manageable tasks and systematic processes. The Completer Finisher is essential for quality control, as they are driven by a desire for perfection and are skilled at identifying errors and omissions at the end of a task. Together, these roles provide the execution and quality assurance the team currently lacks. Incorrect: Shaper and Specialist are not the best fit because while a Shaper provides drive and pressure to overcome obstacles, they do not necessarily focus on systematic organization or fine details. A Specialist provides deep technical knowledge but may focus too narrowly on their subject matter rather than the overall project process. Incorrect: Co-ordinator and Teamworker focus more on the social and leadership aspects of the team. A Co-ordinator is excellent at delegating and clarifying goals, and a Teamworker helps with cohesion and conflict reduction, but neither specifically addresses the need for systematic task execution or final quality polishing. Incorrect: Monitor Evaluator and Plant is incorrect because the team already has a Plant, and adding another would likely lead to more competing ideas rather than better execution. A Monitor Evaluator provides logical judgment and critical thinking, which helps in decision-making but does not directly solve the problem of organizing tasks or finishing them to a high standard. Key Takeaway: For a team to be balanced and effective, it must transition from the thinking and social roles required in early stages to the action-oriented roles like Implementer and Completer Finisher required during execution and delivery phases to ensure quality and structure. Throughout the project lifecycle, the project manager must identify which of the nine Belbin roles are missing based on current team performance issues and recruit or develop those specific behaviors to maintain balance and ensure project success.

Correct: According to Herzberg’s Two-Factor Theory, factors such as achievement, recognition, and the work itself are considered motivators. These are the elements that actually encourage employees to work harder and find satisfaction in their roles. Since the team already has good hygiene factors like salary and working conditions, adding more of these will not increase motivation; instead, the manager must focus on growth and responsibility. Incorrect: Negotiating a further increase in base salary and improving furniture focuses on hygiene factors. Herzberg argued that hygiene factors can only prevent dissatisfaction but do not create motivation once a certain threshold is met. Incorrect: Implementing stricter supervision and clearer policies also falls under hygiene factors related to company policy and administration. While necessary for a functioning workplace, they do not inspire higher performance. Incorrect: Organizing social events focuses on interpersonal relations, which is another hygiene factor. While it may improve the atmosphere, it does not provide the intrinsic satisfaction required for true motivation according to this theory. Key Takeaway: To motivate a team that is already comfortable, a project manager must move beyond hygiene factors and provide opportunities for personal growth, achievement, and recognition.

Correct: The team is described as having high competence (strong technical skills) but low commitment or confidence (demotivated and uncertain due to scope changes). In situational leadership models such as Hersey-Blanchard, this corresponds to a team at a high development level in terms of skill but a lower level in terms of psychological readiness. The Supporting style is most effective here because it emphasizes relationship-building and morale-boosting to restore confidence, while stepping back from technical direction which the team does not actually need. Incorrect: Directing is intended for teams with low competence and high commitment (enthusiastic beginners). Since this team is already technically competent, providing high task direction would be perceived as micromanagement and would likely further damage motivation. Incorrect: Coaching is typically used when the team has some competence but still lacks full mastery or commitment. While the team lacks commitment, they already possess high technical competence, making the high task focus of the coaching style redundant and potentially frustrating. Incorrect: Delegating is only appropriate for teams that demonstrate both high competence and high commitment. Because the team is currently demotivated and expressing uncertainty, a total lack of support or direction could lead to further project slippage or a total breakdown in team morale. Key Takeaway: Effective project leadership requires the ability to diagnose the team’s maturity level and shift between task-oriented and relationship-oriented behaviors to meet their specific needs at a given time.

Correct: Coaching is a performance-driven, task-specific intervention designed to improve a particular skill or behavior in the short term. This is the correct approach for Sarah, who needs to overcome a specific technical hurdle to maintain project momentum. Mentoring is a relationship-oriented, development-driven process focused on the long-term growth and career trajectory of the individual. This is appropriate for David, as he seeks to understand the broader organizational context and prepare for future roles. Incorrect: Mentoring Sarah for a year does not solve the immediate project bottleneck, and coaching David with a simple checklist fails to address the complexity of organizational politics and leadership development. Incorrect: While project managers focus on delivery, ignoring the long-term development of team members through mentoring can lead to lower retention and missed opportunities for succession planning. Incorrect: Formal training might be too slow for Sarah’s immediate needs, and promoting David without prior development or mentoring is a high-risk strategy that ignores the necessary preparation for leadership. Key Takeaway: Coaching focuses on how to do the job now, while mentoring focuses on how to grow for the future.