A self-organizing team is a team that has the authority and autonomy to decide how to perform their work, without being directed or controlled by external factors. A self-organizing team is able to adapt, collaborate, and innovate, and deliver value to the customer and the organization. According to the Professional in Business Analysis Reference Materials1, self-organizing teams are based on trust, collaboration, and empowerment of individuals.
In this scenario, a new team member is added to a self-organizing team, but the new team member is reluctant to speak and take part in team discussions or decisions. This could indicate that the new team member is not comfortable, confident, or familiar with the team culture, dynamics, or expectations. This could affect the team performance, cohesion, and satisfaction.
Therefore, the best two actions that the team should take to engage this new team member are:
Revisit the team's discussion on team behaviors and norms: This action can help the new team member to understand the team values, principles, and rules that guide the team's work and interactions. It can also help the team to clarify and align their expectations, roles, and responsibilities, and to address any issues or conflicts that may arise. By revisiting the team behaviors and norms, the team can create a shared vision and a sense of belonging for the new team member, and foster trust and respect among the team members.
Coach the new team member to improve engagement with the team: This action can help the new team member to develop the skills, knowledge, and confidence to participate and contribute to the team's work and decisions. It can also help the new team member to receive feedback, support, and guidance from the team, and to learn from their experiences and best practices. By coaching the new team member, the team can empower and motivate the new team member, and enhance their performance and satisfaction.
The other options are not the best choices, because:
Report to the project manager about the new team member's behavior: This action can undermine the autonomy and self-organization of the team, and create a dependency and a hierarchy that may conflict with the team culture and values. It can also damage the trust and relationship between the team and the new team member, and make the new team member feel isolated, judged, or rejected. Instead of reporting to the project manager, the team should try to resolve the issue internally, and involve the project manager only if necessary or requested.
Force the new team member to participate in activities that are considered easy: This action can demotivate and discourage the new team member, and make them feel undervalued, underestimated, or patronized. It can also prevent the new team member from developing their full potential and skills, and from delivering value to the team and the customer. Instead of forcing the new team member, the team should encourage and support the new team member, and assign them tasks that are challenging, meaningful, and aligned with their interests and abilities.
Facilitate an open discussion on all ideas and perspectives: This action can be helpful and beneficial for the team in general, but it may not be enough or appropriate for the new team member, who may not feel ready or willing to share their ideas and perspectives with the team. It may also put pressure or stress on the new team member, and make them feel overwhelmed or intimidated by the team's expectations or opinions. Instead of facilitating an open discussion, the team should create a safe and supportive environment for the new team member, and respect their pace and preferences.
References:
Self-Organizing Teams: A Complete Guide.

Agile project management is designed to handle continuous changes. The agile approach allows for flexibility and adaptability, making it well-suited to projects where the environment is dynamic and changes are frequent2. In an agile project, changes are not seen as disruptions but as opportunities for improvement1.
Therefore, the project manager should accommodate critical and urgent changes in the current iteration. This approach allows the team to respond to changes in a timely manner and ensures that the product or service being developed remains relevant and valuable1.
References: = Agile Change Management: Overview, Principles, Best Practices, 10 Steps to Introduce Change Management into Agile Projects

In a hybrid approach, project managers need to adapt to different project life cycles and methodologies, including agile. Agile teams are self-organizing and empowered, and they value collaboration and feedback over command and control. Therefore, project managers are expected to become coaches or facilitators for agile teams, rather than traditional managers or leaders. They should support the team's autonomy, alignment, and accountability, and help them overcome impediments and deliver value. The capacity-building activities may not have adequately prepared the project managers for this role shift, which could cause issues in motivating the agile staff. References: PMBOK Guide, 7th edition, section 2.2.3; Professional in Business Analysis (PMI-PBA) Guide, 2nd edition, section 2.2.3.

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.

The correct answer is C because the scenario requires disciplined risk management rather than an immediate, informal, or purely administrative reaction. The selected response - C. Update the risk register with the team and escalate to the project sponsor and steering committee. - directly addresses the condition described in the question and keeps the project aligned with authorized objectives. PMBOK-aligned practice requires the project manager to identify the event or uncertainty, assess probability and impact, document ownership, and select a response that protects project objectives. This is especially important when project constraints, stakeholder expectations, quality expectations, delivery cadence, or business value may be affected. The competing options are weaker because they either bypass the accountable role, defer action without analysis, escalate before the project manager has prepared decision-quality information, or solve a symptom without correcting the underlying process issue. The selected answer also preserves transparency, ownership, and traceability, which are essential for sound project governance and effective delivery. PMBOK Guide Eighth Edition topics: business environment, risk management, stakeholder communication, impact analysis, governance, value delivery, and continuous improvement.