the project manager should communicate the situation to the appropriate stakeholders who are responsible for managing the supplier relationship and contract. The purchasing department can then take the necessary actions to mitigate the risk of supplier failure or default, such as negotiating new terms, finding alternative suppliers, or terminating the contract. The project manager should not add the situation to the risk register (A) or use the issue log (D) without informing the purchasing department first, as this would not address the root cause of the problem or prevent potential impacts on the project. The project manager should not identify competitors (B) without consulting the purchasing department, as this could violate the existing contract or procurement policies. References:
PMBOK Guide, 7th edition, page 37, section 2.2.6, "Business Environment" PMBOK Guide, 7th edition, page 39, section 2.2.7, "Governance" PMBOK Guide, 7th edition, page 41, section 2.2.8, "Lifecycle" PMBOK Guide, 7th edition, page 43, section 2.2.9, "Tailoring" PMBOK Guide, 7th edition, page 45, section 2.2.10, "Models, Methods, and Artifacts" PMBOK Guide, 7th edition, page 47, section 2.2.11, "Project Performance" PMBOK Guide, 7th edition, page 49, section 2.2.12, "Adaptive Delivery" PMBOK Guide, 7th edition, page 51, section 2.2.13, "Project Management Office" PMBOK Guide, 7th edition, page 53, section 2.2.14, "Project Team" PMBOK Guide, 7th edition, page 55, section 2.2.15, "Stakeholders" PMBOK Guide, 7th edition, page 57, section 2.2.16, "Information Management" PMBOK Guide, 7th edition, page 59, section 2.2.17, "Principles" PMBOK Guide, 7th edition, page 61, section 2.2.18, "Performance Domains" PMBOK Guide, 7th edition, page 63, section 2.2.19, "Tailoring and Models" PMBOK Guide, 7th edition, page 65, section 2.2.20, "Standards Plus" PMBOK Guide, 7th edition, page 67, section 2.2.21, "Glossary" PMBOK Guide, 7th edition, page 69, section 2.2.22, "References" PMBOK Guide, 7th edition, page 71, section 2.2.23, "Index" PMBOK Guide, 7th edition, page 73, section 2.2.24, "Appendix X1: Summary of Key Concepts" PMBOK Guide, 7th edition, page 75, section 2.2.25, "Appendix X2: Summary of Tailoring Considerations" PMBOK Guide, 7th edition, page 77, section 2.2.26, "Appendix X3: Summary of Tools and Techniques" PMBOK Guide, 7th edition, page 79, section 2.2.27, "Appendix X4: Summary of Agile, Iterative, Adaptive, and Hybrid Approaches" PMBOK Guide, 7th edition, page 81, section 2.2.28, "Appendix X5: Contributors and Reviewers" PMBOK Guide, 7th edition, page 83, section 2.2.29, "Appendix X6: PMI Code of Ethics and Professional Conduct" PMBOK Guide, 7th edition, page 85, section 2.2.30, "Appendix X7: Application Area Extensions" PMBOK Guide, 7th edition, page 87, section 2.2.31, "Appendix X8: Summary of Changes" PMBOK Guide, 7th edition, page 89, section 2.2.32, "Introduction" PMBOK Guide, 7th edition, page 91, section 2.2.33, "Performance Domain: Stakeholders" PMBOK Guide, 7th edition, page 93, section 2.2.34, "Performance Domain: Team" PMBOK Guide, 7th edition, page 95, section 2.2.35, "Performance Domain: Development Approach and Lifecycle" PMBOK Guide, 7th edition, page 97, section 2.2.36, "Performance Domain: Planning" PMBOK Guide, 7th edition, page 99, section 2.2.37, "Performance Domain: Project Work" PMBOK Guide, 7th edition, page 101, section 2.2.38, "Performance Domain: Delivery" PMBOK Guide, 7th edition, page 103, section 2.2.39, "Performance Domain: Measurement" PMBOK Guide, 7th edition, page 105, section 2.2.40, "Performance Domain: Uncertainty" PMBOK Guide, 7th edition, page 107, section 2.2.41, "Closing" PMBOK Guide, 7th edition, page 109, section 2.2.42, "Models, Methods, and Artifacts"

In agile methodologies, retrospectives are vital for continuous improvement and learning from the experiences of past sprints2. By facilitating a retrospective meeting that focuses on analyzing the root causes of the bugs and proposing solutions, the project manager can help the team to identify and address the underlying issues that led to the compromised user experience1. This approach aligns with agile principles, which emphasize team collaboration, reflection, and adaptation to improve processes and product quality2. References:
* How to Manage Bugs in Scrum: 10 Best Practices for Agile Teams1.
* Sprint Retrospective: How to Hold an Effective Meeting2.

The project manager should review the risk management plan to evaluate the probability and impact of these delays, and determine the appropriate response strategies. The risk management plan is a document that describes how risk management activities will be planned, structured, and performed throughout the project. It includes the processes, roles and responsibilities, tools and techniques, risk categories, risk appetite, risk thresholds, and risk response strategies for the project1. By reviewing the risk management plan, the project manager can identify the risks that are causing or contributing to the delays, such as cultural differences, communication barriers, or schedule conflicts. The project manager can also assess the likelihood and severity of these risks, and their effect on the project objectives, such as scope, time, cost, quality, and stakeholder satisfaction. Based on this analysis, the project manager can select the best risk response strategies, such as avoid, transfer, mitigate, exploit, share, enhance, or accept, and implement them to reduce the negative impact or increase the positive impact of the risks2. The project manager can also update the risk register, which is a document that records the details of all identified risks, their analysis, and their response plans3.
The other options, implementing crashing, fast-tracking, or conflict management, are not the best ways to handle this situation. Crashing and fast-tracking are schedule compression techniques that can be used to shorten the project duration without changing the project scope4. However, these techniques have drawbacks, such as increasing costs, risks, or rework, and they may not address the root causes of the delays. Conflict management is a process of resolving disagreements among project stakeholders, such as team members, sponsors, customers, or suppliers5. However, conflict management may not be effective if the delays are caused by external factors, such as holidays, that are beyond the control of the project team.
: 1 A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition, Chapter
11.1.3.1 2 A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition, Chapter 11.5.2 3 A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition, Chapter 11.4.2.1 4 A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition, Chapter 6.6 5 A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition, Chapter 9.5

If the customer remains dissatisfied despite frequent communication and reporting, the problem is likely not
"lack of updates" but a mismatch between delivered outcomes and customer expectations. The project lead should review the situation with the customer and adjust with the team (C). This reflects agile's inspect-and- adapt mindset: clarify what "satisfaction" means (value, usability, quality, timing), identify gaps in the current product increments, and agree on corrective actions such as reprioritizing the backlog, refining acceptance criteria, strengthening the Definition of Done, improving demo quality, or incorporating customer feedback more effectively. Reducing communication (A) typically worsens alignment. Explaining the team is new to agile (B) is not a solution and can reduce confidence; customers care about outcomes, not excuses. Changing sprint review frequency (D) treats a symptom and may reduce transparency. Collaborative review and adjustment restores alignment, reinforces customer collaboration, and ensures future iterations target the customer's real needs-key PMP and agile objectives for stakeholder engagement and value delivery.

When a deadline is at risk, the project manager should first perform objective analysis to determine feasible recovery options and their impacts. Conducting simulations (B)-such as schedule risk analysis, critical path assessment, what-if scenarios, or Monte Carlo simulation-helps quantify probability of meeting the date and evaluates which levers (crashing, fast-tracking, scope trade-offs, resource changes) provide the best outcome with acceptable risk. Increasing resources (A) or reducing scope (C) may be valid tactics, but they should not be the first step without analyzing constraints, dependencies, and diminishing returns; adding people can increase coordination overhead, and scope reduction may affect value or contractual obligations. "Work with the team to deliver on time" (D) is too generic and lacks a structured decision basis. Simulation-driven analysis supports informed sponsor decisions, strengthens credibility, and aligns with PMP expectations for schedule management and integrated change control by selecting corrective actions based on evidence rather than urgency alone.