According to the PMBOK Guide, a change request is a formal petition for change in a project. It's a document that explains what are the changes to be made and the main reasons why they should be implemented1. Change requests can either be submitted by internal or external project stakeholders. When a project manager realizes that some operational project requirements were not captured in the project scope of work, they should issue a change request to include the additional scope, and track the completion of the work items. This is the best way to ensure that the project deliverables meet the customer's needs and expectations, and that the project scope is aligned with the project objectives. The other options are not the best actions to take in this situation. Issuing a change request to remove items from the scope of work and keep the project on schedule (option A) may compromise the quality and value of the project deliverables, and may result in customer dissatisfaction or rejection. Documenting the issue in the lessons learned document, and discussing this with the project sponsor (option C) may be helpful for future projects, but it does not address the current issue or resolve the gap in the project scope. Arranging to pass the cost to the operational area since the customer will benefit (option D) may create conflicts and resentment among the project stakeholders, and may violate the project budget and contract terms. References: PMBOK Guide, 6th edition, pages 115-116, 123-
124.

A release burndown chart is a tool that shows the amount of work remaining in a project over time, based on the estimated effort and the actual progress of the team. It can help the project manager and the steering committee to monitor the project performance, identify any deviations from the plan, and adjust the scope, schedule, or resources accordingly. A release burndown chart can also provide an indication of the time remaining on a medium-sized project by comparing the ideal and the actual burndown lines, and projecting the completion date based on the current velocity and the remaining work. A release burndown chart is especially useful for agile projects that work in short iterations, as it can reflect the changes in the backlog and the scope due to feedback, reprioritization, or new requirements. References:
PMBOK Guide, Sixth Edition, Chapter 6, Section 6.7.2.1
What is a Burndown Chart? by Agile Alliance
Burndown Chart: What it is, How to Use it, Example by Asana
Burnup Chart - Sprint & Release Tracking by Tech Agilist

According to the Project Management Body of Knowledge (PMBOK) Guide, when a new stakeholder joins the project, especially one who can significantly influence the project's direction, the project manager should first ensure that this stakeholder has a clear understanding of the project. This includes the project's objectives, scope, deliverables, milestones, and risks. By presenting the project to the new stakeholder, the project manager can align the stakeholder's expectations and decisions with the project's goals and constraints. This is crucial to maintain the project's progress and manage the change effectively. References:
Project Management Professional (PMP) Reference Materials, PMBOK Guide, Chapter 13: Stakeholder Management.

This question belongs to the People domain because it focuses on stakeholder engagement, communication, and influencing support. PMI's PMP Examination Content Outline emphasizes that project leaders should engage stakeholders, analyze their needs, and address resistance through appropriate communication and collaboration. Since the stakeholder is refusing involvement because they do not see value in the deliverable, the project manager should first meet directly with that stakeholder and discuss the impact and benefits of the deliverable. That is the most appropriate first step because it addresses the root cause of the resistance rather than escalating prematurely.
Option B is too early because the project manager should attempt direct engagement before escalating a stakeholder issue. Option C treats the situation only as a risk, but the immediate problem is active stakeholder resistance that requires engagement. Option D is too vague and delays resolution. PMP-style thinking favors proactive stakeholder communication, expectation management, and building alignment early in the project, especially during charter development when support and resources are being secured. Therefore, meeting with the stakeholder to discuss the impact of the deliverable is the best answer.

In an agile project, when the budget is nearly depleted yet the project is far from completion, it is essential to review the project backlog. This allows the project manager to reprioritize work and identify any possible reductions in project scope that could bring the project back within budgetary constraints. This strategy is in line with agile principles, which emphasize flexibility and the ability to adapt to changing circumstances. By focusing on the most valuable deliverables and potentially descaling the scope, the project can still achieve its most critical objectives within the available budget.
PMBOK Guide - Sixth Edition, Section 8.1 - Plan Quality Management
Professional in Business Analysis (PMI-PBA) Reference Materials