When there are changes in team composition, especially due to organizational restructuring, a team alignment session is essential to reset expectations, re-establish collaboration norms, clarify scope, and build cohesion. According to the PMBOK Guide (Seventh Edition), project managers should take the lead in fostering team performance and alignment, especially when the team has undergone major transitions.
Option A is premature and defeatist; the issue should be explored with the team first.
Option B is rigid and dismisses the real concern about feasibility.
Option D may follow after alignment but should not be the first step without full team engagement.
Reference:
PMBOK Guide - Seventh Edition, Team Performance Domain
PMI's Guidelines on Organizational Change and Transition
-

When a key stakeholder requests additional work that is not in the scope, the first action a project manager should take is to evaluate the impact of the requested change. This involves assessing how the change will affect the project's scope, schedule, budget, quality, risk, and benefits. After a thorough evaluation, the project manager should submit a change request. This formalizes the process and ensures that the requested change is documented, evaluated, and approved (or rejected) systematically within the project's change control procedures.

The first step should be to engage the team in a discussion to understand the challenges and concerns regarding the quality feedback mechanism. This collaborative approach allows for a comprehensive review of the quality process and identification of areas for improvement. It ensures that all team members, including those who are high-performing and those facing difficulties, have a voice in the process and can contribute to enhancing the quality of output. This aligns with PMI's principles of continuous improvement and stakeholder engagement in quality management12.
: The approach is supported by PMI's guidelines on quality management, which advocate for involving the team in quality discussions and using feedback to improve processes12. Additionally, the PMI Professional in Business Analysis emphasizes the importance of engaging stakeholders and team members in continuous improvement practices34.

In a situation where customer feedback indicates a strong demand for a new feature, it is advisable to deliver a minimum viable feature (MVF) that can provide immediate value while full development continues. This approach aligns with Agile project management principles, which prioritize rapid delivery of value through iterative and incremental development1. By planning for an MVF, the project manager can demonstrate responsiveness to customer needs and provide a tangible product increment within a short timeframe, thus satisfying the urgent request from the marketing department without disrupting the ongoing work of Company B2.
Reference:
PMI. (2021). A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition.
Atlassian. (2023). Minimum Viable Product (MVP): What is it & Why it Matters2.
MPUG. (2023). Understanding the Minimum Viable Product (MVP) in Agile Project Management1.

Effective communication is crucial for the success of virtual teams. Regularly collecting feedback from team members can help the project manager understand the effectiveness of current communication methods and identify areas for improvement. This approach aligns with PMI's emphasis on continuous engagement and iterative improvement in project management processes.
: The answer is supported by PMI's resources on best practices for managing and developing virtual project teams, which suggest that understanding team dynamics and maintaining open lines of communication are essential for virtual team engagement and performance12.