In agile project management, retrospectives are a fundamental part of the continuous improvement process.
They provide an opportunity for the team to reflect on the past iteration, discuss what went well and what didn't, and create a plan for improvements moving forward. Addressing the root cause of the quality issues is essential to prevent them from recurring. By involving the team in the problem-solving process, not only can more effective solutions be found, but it also ensures team buy-in and accountability for the quality of the deliverables. This approach aligns with the principles of the PMBOK Guide and the agile methodology, which emphasize the importance of team collaboration, regular reflection, and adaptation to change.
: The answer is verified using the PMBOK Guide principles that advocate for continuous improvement and the agile practice of conducting retrospectives for process enhancement12. Additionally, the Professional in Business Analysis Reference Materials supports the approach of involving the team in identifying and solving problems to improve project outcomes3.

In agile, the team is accountable for meeting the sprint goal, and impediments should be made transparent as soon as they emerge. The best immediate action is to raise the issue in the daily Scrum (D) so the team can swarm the problem, explore options, and adapt the plan for the remaining sprint time. This may include pairing to solve the technical block, reallocating work, splitting the task, or negotiating scope within the sprint while preserving the sprint goal. Informing the product owner (A) may be needed if scope changes are required, but the team should first attempt to solve the impediment and identify feasible options. Suggesting training (B) does not address the immediate sprint risk. Updating the risk register (C) is a predictive practice and is less useful than taking immediate collaborative action; in agile, impediment removal and rapid replanning are primary. By using the daily meeting to coordinate, the team maximizes the chance of delivering value and learning quickly from the obstacle.

When a major feature is requested by the project sponsor that significantly impacts the project's delivery date and budget, the project manager should communicate these impacts to the stakeholders. This involves presenting the results of the impact analysis and negotiating for the necessary resources and time to accommodate the new feature. This approach ensures that the stakeholders are fully informed of the implications and can make decisions based on the project's best interest. It aligns with the PMBOK guide's emphasis on stakeholder engagement and communication as key aspects of effective change management1.
References:
PMBOK Guide's Change Management Process For PMP Exam1.
Managing Change in Organizations: A Practice Guide2.

In Agile project management, when a resource is lost and new requirements are added to the backlog, the project manager should reevaluate the backlog priority with the product owner. This is because the velocity, or the amount of work the team can handle in a given iteration, has been impacted. The project manager and the product owner need to reassess the priorities in the backlog to ensure that the most valuable items are being worked on given the current capacity of the team12. References:
* Agile Project Management: What Is It and Why Does It Matter?1
* Agile Project Manager Roles and Responsibilities: A Career Guide2

Team velocity is a measure of a team's effective productivity and capacity in agile development. It indicates the amount of work a team can accomplish in a given sprint, usually expressed in story points1. Team velocity can vary from sprint to sprint due to various factors, such as team size, complexity, dependencies, quality, and external interruptions2. Therefore, it is important for the project manager to monitor and review the team velocity over the last several sprints and use the average or trend as a basis for planning and forecasting future sprints3. By adjusting the plan according to the team velocity, the project manager can help the team avoid overcommitting or underdelivering, and set realistic and achievable sprint goals4.
The other options are not the best choices for the project manager in this situation. Switching to a Kanban approach (option A) may not solve the problem of sprint failures, as Kanban is a different agile framework that does not use fixed-length iterations or predefined roles. Kanban focuses on visualizing the workflow, limiting the work in progress, and optimizing the flow of value5. While Kanban can help the team improve efficiency and flexibility, it may not be suitable for every project or organization, and it may require a significant change in the team's culture and processes. Asking the project sponsor to approve overtime (option C) may not be a sustainable or effective solution, as it may lead to burnout, lower quality, higher costs, and reduced motivation among the team members6. Replacing junior team members with more experienced ones (option D) may not be feasible or desirable, as it may disrupt the team's dynamics, trust, and collaboration. It may also create resentment, conflict, and turnover among the team members. Negotiating the project scope to compensate for the budget gap may not be aligned with the project's objectives, stakeholders' expectations, or agile principles7.
: 1: What is team velocity and how to calculate it - LogRocket Blog 2: Home - Team Velocity - Fueled by Apollo 3: How to Calculate Team Velocity in Agile Project Management 4: [How to Use Team Velocity to Plan Sprints | monday.com Blog] 5: Kanban - A brief introduction | Atlassian 6: [The Impact of Overtime on Productivity and Quality in Agile Teams] 7: [Agile Manifesto Principles | Agile Alliance]