In an agile project, user stories are a critical tool for defining and explaining the project scope. Here's why:
1.User-Centric Approach: User stories focus on the needs and expectations of end-users or stakeholders. They describe specific functionality or features from the user's perspective.
2.Concise and Understandable: User stories are brief, simple

In the scenario where a supplier has stated that no technical development or testing is required from the customer, it is imperative for the internal project manager to first verify and align the project requirements with all stakeholders. This ensures that all parties have a common understanding of the project scope and deliverables before proceeding. Hosting an alignment session is a proactive approach to confirm the supplier's statement and to clarify any assumptions or expectations. This step is crucial for the project's success and aligns with the best practices in project management as outlined in the PMBOK guide.
References:
PMBOK Guide and Standards1
ExamTopics discussion on similar PMP exam question1

When a key team member, such as the lead design programmer, leaves in the middle of a project, it's a risk that could have been foreseen and for which a contingency plan might have been created. The project manager should consult the risk response plan, which will have strategies or actions outlined for such eventualities. This is a proactive approach to manage the situation without disrupting the project's progress and ensures that the project manager is prepared to handle the loss of critical personnel effectively1.
References: = The importance of having a risk response plan that includes strategies for potential personnel changes is emphasized in PMI's guidelines for risk management. This approach is supported by resources that describe risk response strategies for mitigation, avoidance, transfer, exploitation, enhancement, sharing, and acceptance, which are essential for ensuring positive project outcomes2. Additionally, the role of the change control board is typically to oversee proposed changes to the project plan, not to manage resource allocation or personnel changes3.

Before establishing communication channels or protocols, it is essential to first understand who the stakeholders are, how they communicate, their locations, and their levels of influence and interest. This is especially important in large, international projects involving virtual collaboration. Developing a stakeholder analysis is a foundational step in building an effective communication strategy.
According to the PMBOK Guide - Seventh Edition, stakeholder engagement is one of the key performance domains. Section 2.4 states: "Understanding stakeholders, their interests, and their expectations is critical to a project's success." Communication strategies should be tailored to stakeholder needs, which cannot be effectively done without performing stakeholder analysis first.
References:
PMBOK Guide - Seventh Edition, Section 2.4, Stakeholder Engagement Performance Domain Agile Practice Guide, Ch. 5: "Tailoring Agile for Communication in Virtual Teams"
-