Project-Management-Professional PMP Book

According to the Professional in Business Analysis (PMI-PBA)® Guide, stakeholder communication is the process of planning, managing, and monitoring the exchange of information among project stakeholders. Stakeholder communication should be customized based on the stakeholders’ needs, preferences, expectations, and level of involvement. In this scenario, the project manager should have customized stakeholder communications based on the key stakeholder’s needs. This would have helped the project manager to keep the key stakeholder informed, engaged, and satisfied throughout the project, and to address any issues, concerns, or feedback that the key stakeholder may have. This would have also helped to avoid the situation where the key stakeholder rejected a feature deliverable due to lack of involvement or awareness. Involved the key stakeholders in the decision-making process, analyzed the changes in stakeholder attributes, or documented the project vision and objectives are actions that should be taken as part of the stakeholder communication plan, not as a substitute for it. These actions do not address the root cause of the situation, which is the inadequate stakeholder communication. References: (Professional in Business Analysis Reference Materials source and documents)

• Professional in Business Analysis (PMI-PBA)® Guide, Chapter 2, Section 2.4.1.1
• A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 10, Section 10.2.2.1
• The Standard for Project Management – Seventh Edition, Chapter 3, Section 3.2.2.1

According to the PBA Guide, the project manager should employ collaborative discussions as the primary tool to gain an understanding of the risks for an agile project1. Collaborative discussions are interactive sessions that involve the project team and other relevant stakeholders to identify, analyze, prioritize, and respond to project risks1. Collaborative discussions can take various forms, such as brainstorming, interviews, focus groups, surveys, or retrospectives1. Collaborative discussions enable the project manager to leverage the collective knowledge and experience of the participants, foster a shared understanding of the project risks, and promote a risk-aware culture within the project team1. Collaborative discussions are especially suitable for agile projects, as they support the agile principles of communication, collaboration, feedback, and adaptation2. Collaborative discussions can be conducted throughout the project life cycle, as part of the agile events such as sprint planning, daily scrum, sprint review, or sprint retrospective3. Collaborative discussions can also be integrated with other risk management tools, such as probability assessments, risk avoidance workshops, or interviews with the project champion, to enhance the quality and effectiveness of the risk management process1. References:

• 1: PBA Guide, Chapter 4, Section 4.3.2.1, Page 88
• 2: Agile Manifesto
• 3: Making Risk Management for Agile Projects Effective

This answer is based on the PMBOK® Guide, which is one of the reference materials for the PMP exam1, and the PMI Guide to Business Analysis, which is one of the reference materials for the PMI-PBA exam2. According to the guides, the project manager is responsible for managing the project team, which includes developing, leading, and motivating the team members, as well as resolving any conflicts or issues that may arise among them12. The project manager should also establish and enforce the ground rules for the project team, which are the agreed-upon standards of behavior and expectations for the team members, such as communication protocols, decision-making processes, meeting guidelines, and conflict resolution methods12. When the project manager observes that two team members have been arguing with each other openly at meetings and bypassing the project manager to influence the sponsor, this indicates a serious breach of the ground rules and a potential threat to the project performance and harmony. The project manager should take the following two actions to address this situation:

• Reiterate ground rules at the next meeting and ensure that all team members are clear about these rules. This action will remind the team members of their roles and responsibilities, and the expected norms of conduct for the project team. It will also reinforce the authority and accountability of the project manager, and the importance of following the agreed-upon procedures for communication and decision-making. This action will help to prevent further escalation of the conflict and restore trust and respect among the team members12.
• Address the behavioral issue with each team member. This action will allow the project manager to understand the root cause of the conflict, and the perspectives and interests of each team member. It will also enable the project manager to provide constructive feedback, coaching, or counseling to each team member, and to facilitate a collaborative resolution that satisfies both parties and aligns with the project objectives. This action will help to improve the performance and morale of the team members, and to foster a positive and productive team culture12.

The other options are not appropriate because they do not address the problem effectively or ethically. Asking the team members to work it out themselves is not a responsible or proactive approach, as it may lead to further deterioration of the relationship and the project outcomes. Discussing this situation with other project managers and asking for advice is not a confidential or respectful way to handle the issue, as it may expose the team members to gossip or criticism, and undermine their trust and credibility. Discussing the behavior directly with their managers and requesting them to correct the behavior is not a fair or empowering way to deal with the issue, as it may create a perception of blame or punishment, and damage the rapport and autonomy of the team members. References:

• PMBOK® Guide
• PMI Guide to Business Analysis