In the context of project management, particularly when a project is in the execution phase and the client's engagement levels have changed, it is crucial to maintain open communication and collaboration. Discussing the requested changes with the client ensures that their needs are understood and considered. This collaborative approach aligns with the PMBOK Guide's emphasis on stakeholder engagement as a key aspect of project management. It is important to involve stakeholders, especially clients, in decisions that affect the project scope and outcomes. By jointly reviewing the changes, the project manager can work with the client to assess the impact on the project's objectives, timeline, and budget, and make informed decisions that align with the project's goals and the client's expectations.
The approach of discussing changes with the client is supported by the PMBOK Guide, which outlines the importance of stakeholder engagement and collaboration in project management1. Additionally, the Professional in Business Analysis Reference Materials emphasize the role of business analysis in understanding stakeholder needs and facilitating effective communication between stakeholders and the project team2.

According to the PMBOK Guide, the project steering committee is a group of senior stakeholders who provide strategic direction, guidance, and support to the project. The project steering committee is also responsible for resolving high-level issues and risks that may affect the project. In this scenario, the project manager should escalate the issue of funding access to the project steering committee, as they have the authority and influence to resolve it. The project steering committee can help to expedite the funding process, negotiate with the finance department, or find alternative sources of funding. This will help to avoid further delays and ensure the project can proceed with the procurement process. References: PMBOK Guide, 6th edition, page 33-34. PMP Questions page 524, question 524. [Project Steering Committee: Roles and Responsibilities].

In an organization with low tolerance for schedule and budget variance, stakeholder expectations must be managed through clear, consistent, and proactive communication-especially when stakeholders want visibility into risks and progress. Developing a communications management plan (D) is the best approach because it formalizes what information will be shared, how often, in what format, and through which channels. It also defines reporting responsibilities, escalation paths, and governance touchpoints (e.g., weekly dashboards, milestone reviews, risk reviews, variance reporting). This creates predictable transparency and reduces ad-hoc requests or misunderstandings that can lead to distrust or late surprises. Discussing risk response strategies (A) and ensuring a complete risk register (C) are important components of risk management, but they do not, by themselves, establish the systematic visibility stakeholders are asking for.
Adding schedule buffers (B) is a planning tactic that may or may not be acceptable and does not directly address expectations about visibility. A strong communications plan aligns engaged stakeholders, supports timely decisions, and maintains confidence by making progress and risk information easy to access and reliably delivered.

According to the PMBOK Guide's Change Management Process, when a new change is suggested, it should first be identified as a change request by any stakeholder. The project manager and/or project team members then analyze the impact of the change request on the project. This includes documenting the change request and presenting it to the Change Control Board (CCB) for review and decision1. Accepting a suggestion without a formal change request could bypass necessary analysis and documentation processes that ensure the change is beneficial and does not introduce unforeseen risks or issues. References: PMBOK Guide's Change Management Process1; Professional in Business Analysis Reference Materials2.

Before implementing agile methodologies, it is crucial for the project manager to evaluate the organization's culture and readiness for such a transformation. This involves understanding the current processes, mindsets, and capabilities of the team members and the organization as a whole. Agile methodologies require a significant shift in how projects are managed and require an environment that supports collaboration, flexibility, and rapid response to change. Without assessing these factors, the transition to agile may face resistance or fail to be effectively integrated into the organization's practices.
The answer is supported by the PMBOK Guide principles which emphasize the importance of tailoring project management approaches based on the context and environment of the project12. Additionally, the Professional in Business Analysis Reference Materials suggest that understanding the organization and its readiness for change is a key aspect of business analysis, which is integral to successful project management34.