In a hybrid project funded by a T&M agreement, it is essential for the project manager to plan post-delivery support to manage client expectations effectively. This includes establishing a clear understanding of what constitutes project completion and what are the responsibilities of the project team after the product is delivered. Planning for post-delivery support ensures that any defects found after the product is accepted can be addressed within the agreed terms, thus preventing disputes over additional costs for defect fixes.
References: The answer is supported by the best practices in project management, which advocate for proactive planning for post-delivery support as part of the project's scope. This is in line with the PMBOK Guide's emphasis on the importance of stakeholder engagement and managing expectations throughout the project lifecycle12. Additionally, the Professional in Business Analysis Reference Materials highlight the significance of managing client expectations and delivering value post-project completion3.

In project management, effective communication and stakeholder engagement are crucial. When a business analyst requires input from a marketing consultant, it is the project manager's responsibility to facilitate this interaction to ensure project tasks can continue. The project manager should actively engage with the consultant to understand their constraints and schedule a dedicated time for discussion that aligns with the project needs1. This approach ensures that the project moves forward without unnecessary delays and maintains a collaborative environment.
References:
* "4 Techniques to Facilitate Effective Project Meetings" - Project Management Institute1.

The project manager should perform a qualitative risk analysis to assess the probability and impact of the resource availability problem on the project objectives. The project manager should also identify the triggers and warning signs of the risk, and assign a risk rating or priority to the risk. This will help the project manager to determine the appropriate risk response strategy and plan accordingly. Updating the issue log may not be sufficient, as it does not address the uncertainty and potential impact of the risk. Performing a root cause analysis may not be necessary or feasible, as the resource availability problem may be beyond the project manager's control or influence. Implementing a risk response plan may be premature, as the project manager should first analyze the risk before taking any action. References:
A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition, Chapter 11:
Risk, Section 11.3: Assess Risks
Professional in Business Analysis (PMI-PBA) Handbook, Section 2.3: Domains and Tasks, Domain 5:
Evaluation, Task 6: Assess Solution Limitations
Professional in Business Analysis (PMI-PBA) Examination Content Outline, Domain 5: Evaluation, Task 6:
Assess Solution Limitations

This question belongs to the Process domain because it concerns handling scope change through an appropriate delivery and control mechanism. PMI materials emphasize applying scope management and change control principles to a project, and agile-oriented PMI guidance also emphasizes incremental delivery of working products and features for stakeholder evaluation.
Among the options given, the best answer is to start the process to include the new features in the next iteration. This respects the fact that the request has business value, but it also avoids disrupting the team's current agreed design work. Option B and Option D are clearly incorrect because they bypass formal control and governance. Option C is also wrong because the team should not add features informally just to impress the client. PMP-style reasoning favors handling requested changes in a controlled way, evaluating them, and introducing them through the proper planning cadence rather than injecting them immediately into work already aligned by the team. In an iterative environment, the next iteration is the most suitable place to consider and plan those additions.

The project manager should collaborate with the compliance team member to review and prioritize the requirement's delivery, as this is a way to manage the change request and ensure that the project meets the compliance standards and expectations. The project manager should also communicate the impact of the change on the project scope, schedule, cost, and quality to the project sponsor and other stakeholders, and obtain their approval and support. The project manager should not ask the team to include the compliance requirement in the current sprint and deliver it (choice A), as this would disrupt the sprint planning and execution, and create scope creep and quality issues. The project manager should not add the new compliance requirement to the backlog as the technical team does not have any capacity (choice B), as this would delay the delivery of the compliance requirement and expose the project to legal and regulatory risks. The project manager should not include the compliance lead in the stakeholders list and wait for the next status meeting (choice C), as this would not address the urgency and importance of the compliance requirement, and it would not involve the compliance lead in the decision-making and problem-solving process. References:
PMBOK Guide, 6th edition, page 115: "A change request is a formal proposal to modify any document, deliverable, or baseline." PMBOK Guide, 6th edition, page 119: "The project manager should review all change requests, assess their impact on the project, and either approve them or submit them to the change control board (CCB) or other decision-making authority for approval or rejection." PMBOK Guide, 6th edition, page 120: "The project manager should communicate the approved change requests to the project team and other stakeholders, and update the project management plan and other project documents accordingly." PMBOK Guide, 6th edition, page 39: "Compliance requirements are the set of standards or regulations that the project must adhere to, such as health, safety, security, performance, environmental, or quality standards."