In a hybrid project, the project manager needs to balance the different approaches and expectations of the stakeholders and the teams. The customer's change request may have been approved based on the assumption that the software team can deliver the software in a timely manner using an agile approach. However, the software team leader's refusal to commit to a delivery date indicates a lack of alignment and collaboration between the teams and the customer. This creates a risk of schedule and scope deviations, as well as potential conflicts and dissatisfaction among the stakeholders. Therefore, the project manager should add this risk to the risk register and monitor it according to the risk management plan. The project manager should also communicate with the software team leader and the customer to clarify the expectations and the rationale behind the change request, and to explore possible ways to mitigate the risk and deliver the software that meets the customer's needs and the hardware team's dependencies. The project manager should not escalate the issue to higher management without trying to resolve it first, as this may undermine the trust and autonomy of the teams. The project manager should not impose the delivery dates on the software team leader, as this may violate the agile principles and demotivate the team. The project manager should not ask the software team leader to use a predictive approach, as this may not be feasible or suitable for the software development process and the customer's requirements. References: (Professional in Business Analysis Reference Materials source and documents)
* PMBOKGuide, 6th edition, Section 1.2.4, p. 19
* PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline, Domain III:
Analysis, Task 5, p. 11
* Business Analysis for Practitioners: A Practice Guide, Section 2.4.2, p. 36