When a key stakeholder requests additional work that is not in the scope, the first action a project manager should take is to evaluate the impact of the requested change. This involves assessing how the change will affect the project's scope, schedule, budget, quality, risk, and benefits. After a thorough evaluation, the project manager should submit a change request. This formalizes the process and ensures that the requested change is documented, evaluated, and approved (or rejected) systematically within the project's change control procedures.

The team norms document (sometimes part of the team charter) outlines behavioral expectations, communication styles, and rules for collaboration. It's the most appropriate document to provide HR insights into how the team works together.
The PMBOK Guide - Seventh Edition emphasizes defining team agreements early and using them to manage team dynamics.
Option B shows transparency but doesn't offer structured insight.
Option C is broader and not focused specifically on team behavior.
Option D covers communication logistics, not interpersonal norms.
Reference:
PMBOK Guide - Seventh Edition, Team and Stakeholder Performance Domains PMI Agile Practice Guide - Chapter 4, Team Chartering

In this scenario, the project manager should engage with all stakeholders, including the farmers' group, to discuss the project objectives and review their requirements. This is in line with the best practices of stakeholder engagement and management, which are critical for the success of any project. By involving the farmers' group, the project manager can understand their needs and concerns, and work towards a solution that accommodates all parties involved. This approach not only helps in mitigating risks but also ensures that the project delivers value to all stakeholders.

In a multiyear resource-constrained project that is midway through the execution phase, identifying the critical path is crucial when a potential schedule delay is observed. The critical path method (CPM) is a step-by-step project management technique to identify activities on the critical path. It is an approach to project scheduling that breaks the project into work tasks, displays them in a flow chart, and calculates the project duration based on task sequences. This method helps to identify the most important tasks and to focus on them to bring the project back on schedule. Investigating the reasons for the delay is essential to develop an effective recovery plan. This approach is proactive and allows the project manager to address the specific issues causing the delay and take corrective actions to bring the project back on track.
The answer is based on the best practices outlined in the PMBOK Guide and the Agile Practice Guide, which are part of the PMP certification materials. These guides emphasize the importance of the critical path method and proactive management of project schedules.

To address prior tensions and focus the retrospective on constructive improvements, the project manager should set clear expectations for behavior and objectives. A well-structured agenda helps keep the discussion process-oriented and prevents blame. This approach aligns with Agile principles and effective facilitation practices.
Option A prevents open communication and collaboration.
Option B focuses only on leadership, not the whole team.
Option D introduces unnecessary escalation and shifts focus from improvement to contract management.
Reference:
Agile Practice Guide, Chapter 5: Retrospectives and Continuous Improvement PMBOK Guide - Seventh Edition, Team Performance Domain (Feedback and Facilitation)