In Agile, scope is flexible, and time and resources are generally fixed per sprint. Therefore, when scope seems unmanageable, prioritization is the correct approach. The Scrum team-including the Product Owner-must decide which items provide the most value and can fit within the sprint.
Option B aligns with Agile principles by focusing on value delivery and continuous negotiation. This maintains flexibility while aiming to achieve business objectives.
Option A contradicts Agile team principles by injecting resources mid-sprint.
Option C is partially correct but lacks the negotiation and prioritization step.
Option D contradicts Agile's principle of team-driven planning and adaptive scope.
References:
Agile Practice Guide, Chapter 5: "Agile Planning Concepts"
The Scrum Guide (2020), Section: "Sprint Planning"
PMBOK Guide - Seventh Edition, Performance Domain: Planning and Delivery

* According to the PMBOK Guide, a change request is a formal proposal to modify any document, deliverable, or baseline of a project. Change requests can be initiated by any stakeholder, including the project team, and should be processed through the perform integrated change control process.
* In this scenario, the project team has identified a potential risk that could affect the quality and schedule of the next iteration of the project. The team has also proposed a solution to mitigate the risk by buying new equipment. This solution would require an increase in the project budget, which is a baseline that needs to be approved by the project sponsor or customer.
* Therefore, the project manager should submit a change request to increase the budget and buy new equipment, and follow the change control procedures to obtain the necessary approval and authorization. This would ensure that the project scope, schedule, and quality are not compromised, and that the project stakeholders are aware of and agree with the proposed change.
* The other options are not appropriate because:
* Checking the project budget to verify if there is enough contingency reserve (option A) is not sufficient to address the issue. Contingency reserves are funds set aside to cover known risks that may or may not occur during the project. Even if there is enough contingency reserve, the project manager still needs to submit a change request to use it and update the project baseline.
* Reviewing the cost management plan to determine how to address this issue (option B) is also not sufficient to address the issue. The cost management plan is a component of the project management plan that describes how the project costs will be planned, estimated, budgeted, managed, and controlled. It does not provide specific guidance on how to deal with changes that affect the project budget. The project manager still needs to follow the change control procedures and submit a change request.
* Telling the team members that more equipment is not part of the project's scope (option C) is not a constructive or collaborative way to deal with the issue. The project manager should not ignore or dismiss the team's input and recommendations, especially if they are based on valid and relevant information. The project manager should respect the team's expertise and experience, and work with them to find the best solution for the project.
References:
[PMBOK Guide] - A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition, Project Management Institute, Inc., 2021.

#
In team dysfunction situations, especially with mixed behavior styles (e.g., autocratic and avoidant), a project manager must first seek to understand before intervening. One effective leadership tool is the use of personality assessments or behavioral analysis tools (e.g., DISC, MBTI) to understand team dynamics and communication styles. This approach allows the project manager to adapt their leadership style and foster collaboration based on real data.
The PMBOK Guide - Seventh Edition discusses the importance of tailoring leadership and communication approaches based on individual and team personality traits. It also encourages team building through understanding behavioral characteristics.
Option A is authoritarian and not aligned with modern leadership practices.
Option B is motivational but not diagnostic-it won't address root causes.
Option D is extreme and violates conflict resolution principles.
References:
PMBOK Guide - Seventh Edition, Section 3.1: Project Team Performance
PMI Talent Triangle: Leadership, Behavioral Awareness

According to the PMBOK Guide 7th Edition, one of the principles of project management is to "focus on value". This means that the project manager should deliver products, services, or results that meet the needs and expectations of the customer and other stakeholders. One of the ways to achieve this is to use an adaptive or agile approach, which allows for frequent feedback and collaboration with the customer. Working with the product owner to define the minimum viable product(s) (MVPs) is an example of an agile technique that helps to deliver value early and often, and to validate the customer's requirements. MVPs are versions of the product that have enough features to satisfy the customer's needs and provide feedback for future development. Therefore, this option is the best approach to remove the impediment of the customer's unclear requirements. The other options are not as effective because they do not address the root cause of the problem, which is the lack of customer involvement and validation. Following a predictive approach may lead to delivering a product that does not meet the customer's needs or expectations, and may result in rework or waste. Reinforcing the negotiation and soft skills of the team may help to improve the communication and relationship with the customer, but it does not ensure that the product will deliver value. Developing and monitoring a plan with due dates may help to manage the schedule, but it does not guarantee that the product will satisfy the customer's requirements. References: : PMBOK Guide 7th Edition, PMI, 2021, p. 9 : Agile Practice Guide, PMI, 2017, pp. 25-26

The stakeholder engagement plan is a subsidiary plan of the project management plan that identifies the strategies and actions required to promote productive involvement of stakeholders in project decisions and execution. It is a dynamic document that should be updated throughout the project as stakeholder needs and expectations change. The project manager should explain to the key stakeholder that their needs will be updated in the stakeholder engagement plan and that their continued participation is important for the project success. References: PMBOK Guide, 7th edition, section 13.2.3.1; Professional in Business Analysis (PMI- PBA) Guide, 2nd edition, section 4.2.3.1.