Agile project management welcomes changes in scope, but it also requires a trade-off of other items in the product backlog. The product owner owns the backlog and has to be able to make these decisions regarding trade-offs between stories and features. The project manager should guide the agile team to add the new scope to the product backlog and prioritize it according to the project goals and customer value. The project manager should also conduct regular backlog grooming sessions to assess and update the backlog items. The new scope should not be added to the current sprint, unless it is small enough to be completed by the time the sprint ends and does not affect the sprint goals. Creating a parallel sprint, pausing the sprint, or moderating the expectations for sprint quality are not agile practices and would compromise the project's agility, quality, and delivery. References:
* How Agile Addresses Changing Project Scope
* Agile Twists & Turns: How to Handle Scope Changes
* How to change your project's scope (the right way)
* Agile Scope Management: Refactor Your PMP

In a situation where there is disagreement about the value of certain activities in a project, especially when the project is at risk of running over budget, the project manager should:
Collaborate with the functional manager to determine which critical activities could be accommodated by the budget (A): This approach allows for a shared understanding of the project's constraints and priorities. It also provides an opportunity for the functional manager to contribute to the decision-making process, which can lead to better buy-in and less resistance1.
Conduct a meeting with the functional manager to explain why the activities needed to be stopped : Clear communication is key in managing conflicts. By explaining the reasons behind the decision, the project manager can help the functional manager understand the situation better. This can lead to a more constructive discussion and potentially a compromise1.
1
https://www.pmbypm.com/conflict-management-strategies/

Agile project management emphasizes flexibility, collaboration, and customer satisfaction. In an agile approach, customer and team collaboration is a key principle. This approach allows for changes and evolution in requirements and solutions through collaborative effort. It's particularly beneficial in environments where it's important to be able to adapt quickly to changes. Therefore, if collaboration with the business is a critical factor for the project, an agile approach would be suitable12. References:
* Project Management Professional (PMP) Certification | PMI2
* PMP Examination Content Outline - June 2019 - Project Management Institute1

Stakeholder engagement is a critical function of a project manager, especially when there is disagreement over decisions. The best course of action is to clarify the rationale behind the selection and use data-driven reasoning to influence the dissenting teams toward consensus.
According to the PMBOK Guide - Seventh Edition (Stakeholder and Communication Performance Domains), the project manager must ensure that stakeholders understand the process and are aligned with outcomes. Engaging in respectful discussions and influencing team members through facts and process transparency supports long-term collaboration and buy-in.
Option A escalates prematurely.
Option B is authoritarian and damages trust.
Option C neglects stakeholder engagement.
References:
PMBOK Guide - Seventh Edition, Stakeholder Engagement and Decision-Making Principles PMI Influence Without Authority Toolkit
##############################################

When new stakeholders join with conflicting priorities, effective engagement begins with structured stakeholder identification and analysis. Identifying and categorizing stakeholders (B) allows the project manager to assess influence, interest, impact, expectations, and preferred communication methods, then tailor engagement strategies accordingly. Categorization (e.g., power/interest grid, influence/impact mapping) helps determine who needs close management, who needs to be kept satisfied or informed, and how to handle conflicts through appropriate decision forums and escalation paths. Simply inviting everyone to status meetings (A) is inefficient and often increases frustration-especially for stakeholders who feel meetings are irrelevant. Interacting individually (C) can be useful, but without stakeholder analysis it becomes ad hoc and may miss key groups or fail to address governance needs. "Recognizing diversity" (D) is important but vague and not an actionable first step. By categorizing stakeholders, the project manager can design a targeted engagement plan, reduce conflict through clear decision rights, and align cross-functional collaboration to support the new phase's objectives.