Troubleshooting Scenario Questions

Reduce the sprint backlog yourself to ensure the team can succeed

Why wrong: As a Scrum Master, directly reducing the sprint backlog yourself undermines the team's self-organizing principle and their ownership of the commitment. The Development Team is responsible for determining what they can realistically achieve within a sprint, and imposing changes from outside disempowers them, hindering their ability to learn from past experiences and improve their estimation process. This action would violate the Scrum framework's emphasis on team autonomy and shared accountability for sprint goals.

Add more team members to increase capacity

Why wrong: Adding more team members is often a counterproductive response to a team consistently failing to meet commitments, especially if the underlying issue is poor estimation. New members require onboarding, which initially decreases overall team productivity, a phenomenon known as Brooks's Law. Furthermore, this action fails to address the fundamental problem of inaccurate forecasting and commitment, potentially masking the real issue rather than resolving it through improved team practices.

Extend the sprint duration to give the team more time

Why wrong: Arbitrarily extending the sprint duration disrupts the consistent rhythm and empirical feedback loop that short, fixed-length sprints provide. While sprint length can be adjusted, it is a significant process change that should be a deliberate decision made by the Development Team and Product Owner, not an imposed solution to a commitment problem. This action would mask the underlying estimation issues and delay the opportunity for the team to learn and adapt within a stable sprint cadence.

Adjust the sprint backlog to deprioritize features dependent on the component

Why wrong: This action is premature as a first step because it assumes a specific solution without fully understanding the problem's scope or potential alternatives. While adjusting the backlog might become necessary, it should only occur *after* a thorough impact analysis has been performed and stakeholders have been consulted. Deprioritizing features without understanding the full critical path impact or exploring mitigation options could lead to suboptimal decisions and unnecessary delays or scope reductions.

Escalate the issue immediately to the project sponsor and request additional budget

Why wrong: Escalating immediately to the project sponsor without first conducting an impact analysis demonstrates a lack of proactive problem-solving and accountability from the project manager. A PMP is expected to analyze the situation, understand its implications, and propose potential solutions or options before involving higher management. Requesting additional budget without a clear, data-backed justification for the cost increase and an explanation of how it addresses the critical path impact is unprofessional and unlikely to be approved.

Initiate legal proceedings against the vendor for breach of contract

Why wrong: Initiating legal proceedings is an extreme measure that should be considered only as a last resort, after all other contractual and negotiation avenues have been exhausted. As a first step, it is highly premature, costly, time-consuming, and can severely damage vendor relationships, potentially hindering future project success or collaboration. A project manager should first review the contract, engage in discussions with the vendor, and explore alternative solutions or remedies outlined in the agreement before contemplating legal action.

File a claim against the vendor for breach of contract.

Why wrong: Filing a claim for breach of contract is an adversarial and premature response that escalates the situation to a legal dispute without first attempting to collaboratively resolve the issue or understand its full project impact. Project management best practices prioritize problem-solving and mitigation through negotiation and alternative strategies before resorting to costly and time-consuming legal actions, which should be considered a last resort after exhausting other options.

Update the risk register and inform the sponsor about the delay.

Why wrong: While updating the risk register and informing the sponsor are essential communication and documentation activities, this option is insufficient as a complete response to a critical vendor failure. It describes monitoring and reporting the issue but fails to include the crucial steps of analyzing the actual impact on project objectives and proactively developing and implementing specific mitigation strategies to address the materialized risk. A project manager must do more than just report; they must also act.

Immediately find a new vendor to deliver the component.

Why wrong: Immediately finding a new vendor without prior analysis is a reactive and potentially inefficient approach. This action could lead to suboptimal choices, incur unnecessary costs, or even violate existing contractual obligations with the current vendor. A project manager must first assess the full impact of the delay and evaluate all available mitigation strategies before committing to a potentially costly and complex solution like replacing a key supplier, ensuring the chosen path is the most effective.

Immediately contract the alternative vendor to avoid further delay

Why wrong: Immediately contracting an alternative vendor without proper analysis or formal approval constitutes an unauthorized commitment and bypasses established project change control and procurement management processes. This action could lead to unbudgeted costs, scope creep, or contractual disputes, violating the project management plan and organizational governance. Such a unilateral decision undermines the project manager's accountability and the project's integrity.

Ask the original vendor to expedite delivery at no extra cost

Why wrong: Asking the original vendor to expedite delivery at no extra cost is an unrealistic expectation, especially since the vendor has already communicated an inability to deliver as planned. This approach fails to acknowledge the vendor's constraints and is unlikely to resolve the core issue of the impending delay. It does not offer a viable mitigation strategy and could strain the vendor relationship without providing a practical solution to the project's critical path impact.

Update the risk register and accept the four-week delay

Why wrong: Simply updating the risk register and accepting a four-week delay without exploring any mitigation strategies is a passive approach to risk management, especially for a known issue impacting a key vendor. Project managers are expected to proactively identify and implement appropriate risk responses to minimize negative impacts on project objectives. This option fails to demonstrate due diligence in seeking solutions to prevent or reduce the delay.

Replace the team member with a more reliable resource

Why wrong: Replacing a team member prematurely is a drastic and costly measure that should be considered only as a last resort after all performance management and coaching efforts have failed. This action incurs significant expenses related to recruitment, onboarding, and potential loss of institutional knowledge, which can severely disrupt project progress, budget, and team stability. Effective project management prioritizes developing existing team members.

Ignore the issue as the team member is technically strong

Why wrong: Ignoring performance issues, even for a technically strong individual, is detrimental to overall team morale and productivity. This inaction can create a perception of unfairness among other team members who may be picking up the slack or adhering to higher standards. Such an oversight can erode trust, foster resentment, and ultimately degrade the team's collective efficiency and the project's quality, as unaddressed problems tend to escalate.

Reassign all critical tasks to other team members

Why wrong: Reassigning all critical tasks to other team members is a short-term, reactive solution that fails to address the root cause of the original team member's performance issues. This approach not only overburdens other project resources, potentially leading to burnout, decreased efficiency, and resentment, but also prevents the struggling team member from developing and contributing effectively, hindering long-term team capability and skill development within the project.

Immediately notify the project sponsor and ask for guidance

Why wrong: Immediately notifying the project sponsor and asking for guidance before taking any action is an inappropriate initial response. While stakeholder communication is vital, the project manager is empowered and expected to manage identified risks by implementing the planned responses first. Escalation to the sponsor should occur after the PM has initiated the planned response and assessed its effectiveness, or if the risk exceeds the PM's authority or the scope of the existing plan.

Assess the impact of the delay on the project schedule and then decide

Why wrong: Assessing the impact of the delay on the project schedule *after* the risk has occurred indicates a failure in the initial risk planning process. Comprehensive impact analysis, including schedule implications, should have been completed during the Plan Risk Responses process to inform the development of appropriate contingency plans. At the point of risk occurrence, the focus must shift from analysis to immediate execution of the pre-determined response to minimize disruption.

Ask the supplier to find an alternative source at no extra cost

Why wrong: Asking the supplier to find an alternative source at no extra cost is a reactive and potentially unrealistic demand that deviates from a planned risk response. This approach lacks the structured preparation of a contingency plan and may not be feasible or contractually enforceable, potentially leading to further delays or disputes. Effective risk management prioritizes implementing pre-approved strategies over improvising solutions that might not align with project objectives or stakeholder agreements.

Bring up the issue in the next team meeting to encourage accountability

Why wrong: Bringing up a performance issue in a public team meeting is generally counterproductive and can severely damage team morale and trust. This approach often leads to defensiveness and resentment from the team member, rather than fostering genuine accountability or a willingness to improve. Effective project managers prioritize private, direct communication for sensitive topics to maintain psychological safety and encourage open dialogue, which is essential for collaborative problem-solving.

Remove the team member from the project

Why wrong: Removing a team member from the project without first attempting to understand and address the performance issue is an extreme and premature action. Such a drastic measure can significantly disrupt project progress, necessitate costly re-staffing, and negatively impact the morale of the remaining team members who might perceive it as unfair or arbitrary. Project managers are expected to exhaust all reasonable attempts at coaching, support, and conflict resolution before considering such severe consequences.

Report the issue to the team member's functional manager

Why wrong: Reporting the issue directly to the team member's functional manager without first engaging in a direct discussion with the team member themselves is an inappropriate escalation. The project manager holds primary responsibility for managing the performance and conduct of their project team members and should always attempt to resolve issues directly at the lowest possible level. Bypassing this crucial step can undermine the project manager's authority, damage the PM-team member relationship, and may be seen as a failure of leadership in conflict resolution.

Wait to see if the vendor can resolve the issue

Why wrong: Passively waiting for a vendor to resolve an issue, especially when a risk has already occurred, is a reactive and often detrimental approach in project management. This inaction allows the risk event to potentially escalate, causing further delays, increased costs, or quality degradation beyond the initial impact. Effective risk management demands immediate execution of planned responses rather than hoping for an external resolution without a defined strategy.

Escalate the issue to the project sponsor for guidance

Why wrong: Immediately escalating an identified risk with a pre-planned response to the project sponsor is an inappropriate first step for the project manager. The project sponsor's role is typically for strategic guidance, approval of significant changes, or addressing risks beyond the project manager's authority or those that were previously unidentified. The PM is expected to utilize the established risk management plan and execute documented responses before seeking higher-level intervention.

Reassign the work to an internal team

Why wrong: Reassigning work to an internal team as an immediate, unplanned response to a materialized risk is an ad-hoc solution that deviates from structured risk management. Such an action may introduce new unforeseen risks, such as resource overload, skill gaps within the internal team, or increased project costs due to unplanned resource allocation. The most effective approach is to follow the specific, pre-defined risk response strategy outlined in the risk register.

Escalate the issue to the project sponsor immediately without taking any action

Why wrong: Escalating to the sponsor without taking action bypasses the risk response process defined in the risk register; the correct first step is to analyse the risk and select a response strategy (e.g., fast-tracking or crashing) within the project manager’s authority. This option is tempting because escalation is appropriate when a risk exceeds the project manager’s authority or requires sponsor-level decisions, such as a budget increase beyond the contingency reserve.

Update the risk register and continue monitoring, as the risk was expected

Why wrong: This option is incorrect because merely updating the risk register and continuing to monitor is insufficient when an identified risk has actually occurred. While updating the register is a necessary administrative step *after* taking action, the immediate priority is to *implement* the pre-planned risk response. Passive monitoring is for risks that have not yet materialized or for tracking the effectiveness of a response, not for the initial action when a known risk eventuates.

Ask the team to find a workaround without consulting the risk register

Why wrong: This option is incorrect because workarounds are ad-hoc responses developed for *unidentified* or *unplanned* risks that suddenly materialize. For an *expected* risk, a specific risk response strategy should have been developed and documented in the risk register during planning. Bypassing the risk register and immediately seeking a workaround for a known risk demonstrates a failure to leverage prior planning and established risk management processes.

Update the risk register and escalate to the project sponsor.

Why wrong: While updating the risk register is a crucial step in the Monitor Risks process, it is not the *initial* action when a known risk event occurs. The immediate priority is to execute the pre-planned response to contain the impact. Escalation to the project sponsor is typically reserved for situations where the existing mitigation plan proves ineffective, the risk impact exceeds thresholds, or new, unplanned risks emerge that require higher-level intervention.

Meet with the supplier to negotiate an earlier delivery date.

Why wrong: Meeting with the supplier to negotiate an earlier delivery date could indeed be a viable strategy to address a delay. However, this specific action should only be pursued if it is explicitly part of the pre-defined mitigation plan for this particular risk, or if the existing plan has failed. The project manager's first responsibility is to execute the established risk response, rather than immediately devising a new, ad-hoc solution.

Immediately inform the project sponsor and stakeholders about the delay.

Why wrong: While timely communication with the project sponsor and stakeholders is vital for transparency and managing expectations, it is not the *absolute first* action when a risk materializes. The project manager's initial priority is to take immediate corrective action by implementing the pre-approved mitigation plan. Once the response is underway and the situation is being managed, then communicating the status, impact, and response actions becomes the next critical step.

Ask the vendor to expedite the delivery at no extra cost

Why wrong: While negotiation is possible, the immediate step is to activate the contingency plan.

Immediately source an alternative vendor without formal approval

Why wrong: Sourcing without approval bypasses procurement processes and may violate contracts.

Notify the sponsor and request a schedule extension

Why wrong: Notifying stakeholders is important but implementing the contingency plan takes precedence.