When there is a change in government regulations that affects a project, the project manager should first understand the new regulations and evaluate their impact on the project. This involves studying the new regulations with the team and assessing how they affect various project variables such as scope, cost, schedule, and quality. Once the impact is understood, the project manager can then make necessary adjustments to the project plan. References: PMBOKGuide, 6th Edition, Section 4.3: Direct and Manage Project Work, and Section 11.6: Control Risks.

According to the PMBOK Guide, the Perform Integrated Change Control process is essential for reviewing all change requests, approving changes, and managing changes to deliverables, organizational process assets, project documents, and the project management plan1. It involves an integrated approach to assess the potential impact of a suggested modification before executing it. This ensures that any changes align with project goals and do not adversely affect project constraints such as scope, schedule, cost, and quality. The project manager should not unilaterally implement changes without proper evaluation and authorization, which is typically provided by the change control board (CCB). The CCB's role is to review the impacts of the proposed change and make a decision to approve or reject it2.
References:
A Guide to the Project Management Body of Knowledge (PMBOK Guide)1.
Role of a Change Control Board in Project Management in 20242.

Explanation:

When a project team is demotivated due to a framework that is not compatible with agile delivery, the project lead should ask the PMO to review the framework. This is because the PMO is responsible for defining and maintaining project management standards and practices within an organization. A review can help identify the specific areas where the current framework is lacking and how it can be adapted to support agile methodologies. This aligns with the PMBOK guide's principles of tailoring project management practices to meet the unique needs of each project1.
References:
PMBOK Guide - Sixth Edition
Agile Practice Guide2
Disciplined Agile and PMBoK Guide 7th Edition3

The first step for a new project manager-especially one taking over midstream-is to understand the business objectives and rationale for the project. The business case outlines the expected benefits, strategic alignment, and value proposition, which are essential for understanding how success is defined.
According to the PMBOK Guide - Seventh Edition, the business case is a key input to initiating and monitoring a project's continued alignment with organizational strategy.
Option B is premature without understanding the current baseline and project justification.
Option C is detailed-level work; business context is needed first.
Option D is helpful but comes after understanding the foundational documentation.
References:
PMBOK Guide - Seventh Edition, Value Delivery System and Business Case
PMI Guidelines for Managing Transitions Between Project Managers
-