A RAM is a tool that maps the project work packages or activities to the project team members or roles. It helps to define and assign the responsibilities, accountabilities, and authorities of each team member for each project task. It also helps to identify and resolve any gaps, overlaps, or conflicts in the resource allocation. A RAM can be presented in various formats, such as a RACI chart, a RASCI chart, or a linear responsibility chart12.
Developing an approved RAM can help the project manager to manage the team effectively, especially when some team members, such as the site engineers, may not be fully focused on the project due to other priorities or constraints. A RAM can help the project manager to communicate and clarify the expectations and deliverables of each team member, and to monitor and control their performance and progress. A RAM can also help the project manager to coordinate and collaborate with the other stakeholders, such as the production managers, to ensure that the project and the production imperatives are aligned and balanced34.
The other options are not as effective or relevant for managing the team:
* B. Commit each team member's time and deliverables and aim for overall project completion:
Committing each team member's time and deliverables is important, but it may not be sufficient or realistic to manage the team, especially when some team members, such as the site engineers, may have competing or conflicting demands on their time and attention. Aiming for overall project completion is a desirable goal, but it may not be achievable or sustainable without proper planning, communication, and coordination among the team members and the other stakeholders.
* C. Continue the project implementation without the site engineers to ensure the schedule is maintained:
Continuing the project implementation without the site engineers may not be feasible or advisable, as the site engineers may have critical skills, knowledge, or experience that are essential for the project success. Excluding the site engineers from the project may also create risks, issues, or gaps in the project quality, scope, or integration. Moreover, it may damage the relationship and trust between the project manager and the site engineers, and reduce their motivation and commitment to the project.
* D. Contract external resources to fulfill the role of the site engineers who cannot sup-port the project:
Contracting external resources may be an option to supplement or replace the internal resources, such as the site engineers, who cannot support the project. However, this option may not be the best or the first choice, as it may involve additional costs, time, or risks for the project. Contracting external resources may also require approval, negotiation, or procurement processes that may delay or complicate the project. Furthermore, it may affect the morale, loyalty, or performance of the internal resources, who may feel threatened, replaced, or undervalued by the external resources.
References:
1: Responsibility Assignment Matrix - Project Management Knowledge 2: What is a Responsibility Assignment Matrix (RAM) in Project Management? 3: How to Create a Responsibility Assignment Matrix (RAM) for Your Project 4: How to Use a RACI Matrix to Manage Project Resources : [Project Team Management: How to Manage Your Team Effectively] : [How to Manage Project Team Conflicts] : [Project Procurement Management: The Ultimate Guide]

The stakeholder register is a key input for managing communications. In Agile, frequent communication and stakeholder inclusion are vital. If there's a failure due to incorrect contact data, the Scrum Master should proactively review and verify the full stakeholder register to ensure it's accurate and complete, preventing recurrence.
According to the PMBOK Guide - Seventh Edition (Stakeholder and Communication Performance Domains), it is the responsibility of the project team to maintain accurate stakeholder information. This promotes engagement, transparency, and effective decision-making.
Option A places undue burden on the product owner and is inefficient.
Option B shifts responsibility to the stakeholder.
Option C demonstrates poor accountability.
References:
PMBOK Guide - Seventh Edition, Stakeholder Performance Domain
Agile Practice Guide, Chapter 4 - Stakeholder Engagement
##############################################

The project manager should share the organization's decision with the team and make plans to adopt an agile approach in the upcoming project because this is the best way to align the team with the new direction and prepare them for the change. Agile approaches are based on values and principles that emphasize collaboration, flexibility, and customer satisfaction, which may differ from the traditional predictive methods that the team is used to. Therefore, the project manager should communicate the rationale and benefits of the agile approach, and involve the team in planning and executing the project using agile practices and tools. The other options are not the best choices because they do not support the organization's decision or the project sponsor's preference. Preparing a risk report that captures the probability and impact of risks, and then sharing it with the project sponsor (option A) may imply that the project manager is resistant or skeptical about the agile approach, and may not address the team's readiness or capability. Making a request to human resources for new team members who have agile experience (option C) may undermine the existing team's skills and motivation, and may not be feasible or necessary. Asking the project sponsor to change the approach back to predictive as that is the team's strength (option D) may contradict the organization's strategy and the project sponsor's authority, and may not reflect the project manager's willingness to learn and adapt. References: PMBOK Guide, 6th edition, pages 18-19, 686-687. Exam PMP topic 1 question 434 discussion. Episode 434: The PMP Exam is Changing on 1 July 2020.

According to the PMBOK Guide, 7th edition, one of the principles of project management is to collaborate with stakeholders and team members1. This principle emphasizes the importance of establishing and maintaining a shared understanding of the project vision, objectives, and expectations among all project participants. It also suggests that project managers should foster a team culture that supports collaboration, trust, learning, and adaptation1.
In an agile project, the team rules are a set of agreements that define how the team will work together, communicate, and deliver value2. The team rules should be established at the beginning of the project and reviewed periodically to ensure they are still relevant and effective2. The team rules should also be aligned with the agile values and principles, such as responding to change over following a plan and individuals and interactions over processes and tools3.
In this scenario, the project manager observes that the team is having problems meeting their goals in the second iteration. This could indicate that the team rules are not clear, not followed, or not suitable for the current situation. Therefore, the best course of action for the project manager is to provide feedback to the team and conduct a meeting to review the team rules. This will help the team to identify and resolve any issues or conflicts that are affecting their performance, and to update or modify the team rules as needed. This will also help the new team member who does not have agile experience to understand and adapt to the team's way of working.
The other options are not as effective as option A. Option B, conducting a retrospective meeting to find a root cause, is a good practice for agile teams, but it is usually done at the end of each iteration, not in the middle. A retrospective meeting is also focused on evaluating the past iteration and identifying improvement actions for the next one, not on reviewing the team rules. Option C, requesting agile training for the new member, may be helpful, but it does not address the immediate problem of the team's performance. It also assumes that the new member is the only source of the problem, which may not be true. Option D, coaching the new team member in agile methodology, is also a good practice, but it is not the primary responsibility of the project manager. The project manager should delegate the coaching task to a more experienced team member or a mentor, and focus on facilitating the team's collaboration and alignment.
: 1: PMBOK Guide, 7th edition, page 9 2: PMBOK Guide, 7th edition, page 95 3: Agile Manifesto, 4

The project manager should proactively engage with the stakeholders to address their dissatisfaction and work with them to find a solution. This is consistent with the stakeholder engagement plan, which defines the strategies and actions for managing stakeholder expectations and involvement. The project manager should not ignore the stakeholder issue, rely on the management team to intervene, or try to socialize with the stakeholders without addressing the root causes of the problem. References:
* PMP Exam Content Outline (2021), Domain III: Executing the Project, Task 8: Engage with stakeholders to meet expectations and foster relationships, p. 131
* A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 13:
Project Stakeholder Management, Section 13.3.1.1: Stakeholder Engagement Plan, p. 5182
* Professional in Business Analysis (PBA) Examination Content Outline (2018), Domain III: Analysis, Task 6: Manage Stakeholder Collaboration, p. 15