Stakeholder engagement is the process of identifying, analyzing, planning, and implementing actions to communicate with, influence, and involve stakeholders throughout the project lifecycle. Stakeholder engagement aims to ensure that stakeholders are satisfied with the project outcomes, and that their expectations and needs are met. According to the Professional in Business Analysis Reference Materials1, stakeholder engagement involves the following steps:
* Identify stakeholders: Determine who are the individuals or groups that have an interest or influence in the project, and what are their roles, responsibilities, expectations, and power.
* Analyze stakeholders: Assess the level of interest and influence of each stakeholder, and their potential impact on the project objectives, scope, schedule, cost, quality, and risks. Use tools such as stakeholder analysis matrix, power/interest grid, or salience model to categorize stakeholders based on their attributes.
* Plan stakeholder engagement: Develop strategies and actions to effectively communicate with, involve, and manage stakeholders throughout the project. Use tools such as stakeholder engagement plan, communication plan, or RACI matrix to define the frequency, mode, content, and responsibility of stakeholder interactions.
* Implement stakeholder engagement: Execute the planned activities to engage stakeholders, and monitor and measure their feedback, satisfaction, and performance. Use tools such as stakeholder register, issue log, change log, or performance reports to track and document stakeholder engagement.
* Evaluate stakeholder engagement: Review and analyze the effectiveness and outcomes of stakeholder engagement, and identify areas for improvement or adjustment. Use tools such as lessons learned, surveys, or interviews to collect and analyze stakeholder feedback and recommendations.
In this scenario, the project manager realizes that a standard stakeholder engagement approach will not suffice, because one of the client representatives, who is not a key decision maker, is extremely opinionated and could become a roadblock to progress due to their perceived level of authority during meetings. This stakeholder could be classified as a high-interest, low-influence stakeholder, who needs to be kept informed and consulted, but not allowed to dominate or derail the project decisions. Therefore, the best option for the project manager is to allocate time to gain buy-in from the stakeholder prior to key decision meetings. This way, the project manager can:
* Understand the stakeholder's perspective, concerns, and expectations, and address them proactively and respectfully.
* Build trust and rapport with the stakeholder, and demonstrate the value and benefits of the project for them and their organization.
* Involve the stakeholder in the project planning and design process, and solicit their input and feedback on the project scope, objectives, deliverables, and requirements.
* Negotiate and compromise with the stakeholder on any conflicting or unrealistic demands, and seek their support and agreement on the project decisions.
* Acknowledge and appreciate the stakeholder's contribution and participation, and recognize their role and authority within their organization.
By allocating time to gain buy-in from the stakeholder prior to key decision meetings, the project manager can enhance the stakeholder engagement, satisfaction, and collaboration, and reduce the risk of resistance, conflict, or delay in the project.
The other options are not the best choices, because:
* Asking that only key decision makers attend the project meetings could alienate and offend the stakeholder, and damage the relationship and trust with them and their organization. It could also create a communication gap and a lack of transparency and accountability in the project.
* Updating the project schedule to cater to this particular stakeholder could disrupt the project workflow and priorities, and create inefficiencies and delays in the project. It could also cause resentment and frustration among other stakeholders, who may feel that their needs and expectations are not being met or respected.
* Updating the risk register to consider the possible project impacts could be a useful step, but it is not sufficient to address the root cause of the problem, which is the stakeholder's opinionated and authoritative behavior. It could also imply that the project manager is avoiding or ignoring the stakeholder, rather than engaging and influencing them.
References:
Stakeholder Engagement.

According to the PMBOK Guide, a hybrid project approach is a combination of predictive, agile, and/or iterative methods that best suit the project context and objectives. A hybrid project approach requires the project manager to establish team behavior and develop an understanding of how to work together, as different team members may have different preferences, expectations, and experiences with different project methods. The project manager should facilitate collaboration, communication, and integration among team members, and align them with the project vision, goals, and values. The project manager should also provide feedback, coaching, and recognition to the team members, and foster a culture of trust, respect, and learning.
The project manager should not advise the team to adjust their work habits and behaviors to allow for better conflict resolution, as this may imply that the project manager is imposing a single way of working on the team, rather than embracing diversity and flexibility. The project manager should not call a team meeting to discuss team members' strengths and weaknesses, as this may create unnecessary tension and conflict among team members, and may not address the specific challenges and opportunities of a hybrid project approach.
The project manager should not establish rules and regulations for team members with consequences if the goals are not reached, as this may create a rigid and punitive environment that discourages innovation, experimentation, and adaptation, which are essential for a hybrid project approach. References: PMBOK Guide, 7th edition, pages 14-15, 25-26, 32-33; Hybrid Project Management: What You Need to Know

Before responding to the concern, the project manager should review the stakeholder engagement plan to confirm whether this key stakeholder was properly consulted and involved. This step ensures that engagement strategies are aligned with project objectives and that no stakeholder was missed in the planning phase.
The PMBOK Guide - Seventh Edition emphasizes the importance of identifying, analyzing, and engaging all stakeholders appropriately, especially in sensitive public sector projects.
Option B is dismissive and can escalate conflict.
Option C assumes prior engagement without confirmation.
Option D is premature without validating the engagement process.
References:
PMBOK Guide - Seventh Edition, Stakeholder Performance Domain
PMI Stakeholder Engagement Practice Guide
##############################################

The project manager should schedule a session with the team to discuss the issues and work with them to define a plan to manage the sprints going forward. This will help to address the team's concerns, resolve the conflicts, and improve the team's morale and performance. The project manager should also communicate with the product owner and other stakeholders to align the expectations and priorities for the project and the support items. The project manager should also use agile principles and practices to adapt to the changing requirements and deliver value to the customer. Requesting a replacement, scheduling a session with the product owner, or asking HR to send the team members to a workshop are not the best ways to proceed, as they may not solve the root cause of the problem, damage the team's trust and cohesion, or delay the project delivery. References:
* PMP Exam Content Outline, Domain II: Process, Task 5: Support team members and stakeholders to meet project objectives and stakeholder expectations.
* A Guide to the Project Management Body of Knowledge (PMBOK Guide), Seventh Edition, Chapter 3:
Project Performance Domain, Section 3.2: Team Performance, Page 77.
* Professional in Business Analysis (PBA) Certification Exam Outline, Domain III: Analysis, Task 5:
Validate Requirements, Page 14.

The project manager should aim to resolve conflicts in a way that promotes understanding and cooperation among all team members. This involves understanding the emotions and perspectives of all parties involved, and finding ways to reduce tension and increase cooperation. Simply issuing warnings or sending individuals to training may not address the root cause of the conflict. Similarly, establishing special rules or treatment for certain individuals may not be fair or effective in the long term. The project manager should strive to create an environment where all team members feel heard, understood, and valued. References: PMBOK Guide - Sixth Edition, Project Management Institute, Inc., 2017, pp. 349-350. Available at: https://www.pmi.org
/pmbok-guide-standards/foundational/pmbok