To avoid delivering work that does not add value to the business, the project manager should have taken the following actions:
1.Define a Product Scope: Clearly defining the product scope at the beginning of the project ensures that everyone understands the boundaries of what will be delivered. By having a well-defined scope, the project manager can prevent unnecessary features or functionalities from being included.
2.Stakeholder Alignment: The project manager should have engaged with stakeholders (including business departments) to understand their needs and expectations. This alignment helps ensure that the project team focuses on delivering features that truly add value.
3.Scope Management: Throughout the project, the project manager should have actively managed scope changes. When stakeholders requested functionalities beyond the defined scope, the project manager should have evaluated their impact on business value and made informed decisions.
4.Effective Communication: Encouraging open communication between stakeholders, the product owner, and the project team is essential. Regularly reviewing progress, addressing concerns, and adjusting priorities based on business needs would help avoid unnecessary work.
References: 10. Delivering business value: The most important aspect of project management While options A, B, and C are relevant considerations in project management, the immediate focus should have been on defining and managing the product scope to ensure alignment with business value. Option D directly addresses this aspect1.

According to the Project Management Body of Knowledge (PMBOK) Guide, a project manager's interpersonal and team management skills are crucial for project success. If team members are leaving due to inadequate relationship management competencies, it indicates a need for the project manager to improve their leadership skills. Developing relationship skills and emotional intelligence can help create a more positive work environment, leading to lower turnover rates. Emotional intelligence involves recognizing and understanding emotions in oneself and others, and using this awareness to manage behavior and relationships.
By improving these skills, the project manager can better motivate the team, manage conflict, and retain team members. References: Project Management Professional (PMP) Reference Materials, PMBOK Guide, Chapter 3: Role of the Project Manager.

In Scrum, the product owner is the sole person responsible for managing the product backlog. When a customer requests new features mid-sprint, it is inappropriate to add them directly to the sprint. The correct procedure is to have the Scrum Master direct the customer to the product owner, who will evaluate the request and decide whether to include it in the product backlog for future prioritization.
According to the Agile Practice Guide and the Scrum Guide, only the product owner has the authority to accept or reject items in the product backlog. The Scrum Master facilitates communication and protects the team from scope creep during the sprint.
Option A (Definition of Done) is useful for clarifying quality, not for managing scope changes.
Option C (Acceptance criteria) applies to existing backlog items, not new feature requests.
Option D (Backlog prioritization) is the product owner's job and only happens after the sprint, not mid-sprint.
References:
Agile Practice Guide, Chapter 3: Roles and Responsibilities
The Scrum Guide 2020: Product Owner and Scrum Master Roles
PMBOK Guide - Seventh Edition, Agile Tailoring Considerations

The project manager should address this concern with the functional managers to ensure there will be no further delays in the project. The functional managers are the managers who have authority over the team members in their respective functional areas, such as engineering, marketing, finance, etc. The functional managers are responsible for assigning and releasing the team members to the project, as well as providing them with the necessary training, support, and feedback. The project manager should communicate and coordinate with the functional managers to ensure that the team members are available and committed to the project, and that they are not distracted or overloaded by other nonproject-related tasks. The project manager should also explain to the functional managers the impact of their emails on the team's productivity and morale, and request them to respect the team's priorities and schedules. The project manager should also seek the support and intervention of the project sponsor or the senior management, if needed, to resolve any resource conflicts or issues.
The other options are not the best actions for the project manager to take in this situation. Asking the product owner to speak with the functional managers to ensure future requirements come through the product owner is not relevant or effective, as it does not address the current problem of the team members receiving emails from their functional managers to support other nonproject-related tasks. The product owner is the person who represents the customer's voice and defines and prioritizes the product backlog, which is a list of features and requirements that the customer wants to have in the product. The product owner is not involved in the resource management or allocation of the project, and may not have the authority or influence to negotiate with the functional managers. Logging this as a risk in the risk register and continuing to monitor the issue at subsequent meetings is not proactive or sufficient, as it does not prevent or mitigate the negative impact of the team members receiving emails from their functional managers to support other nonproject-related tasks. The risk register is a document that records the identified risks, their causes, impacts, probabilities, responses, and owners. The project manager should not just document and monitor the issue, but also take action to resolve it as soon as possible. Scheduling a meeting with all of the functional managers to resolve the resource conflicts may be too time-consuming and complicated, as it may involve multiple parties and perspectives. The project manager should not wait for a meeting to address the issue, but rather contact the functional managers individually and directly, and seek their cooperation and understanding. References:
* PMBOKGuide, 6th Edition, Chapter 9, Section 9.2, "Plan Resource Management"
* PMBOKGuide, 6th Edition, Chapter 9, Section 9.3, "Acquire Resources"
* PMBOKGuide, 6th Edition, Chapter 9, Section 9.5, "Control Resources"
* PMBOKGuide, 6th Edition, Chapter 11, Section 11.4, "Plan Risk Responses"
* PMP Project Management Professional Exam Study Guide: 2021 Exam Update, 10th Edition, Chapter
8, Section 8.2, "Planning Resources" 1

The Work Breakdown Structure (WBS) is a key project deliverable that organizes the team's work into manageable sections. The Project Manager can review the WBS to clarify the responsibilities of the data integration team and the data migration team. This can help to resolve any areas of overlap and ensure clear accountability for all project tasks. References: PMBOK Guide, 6th Edition, Section 5.4: Create WBS.