A project manager is assigned to a project. The project schedule and costs are tight, and the project manager determined that there is a lack of resources to deliver this project. What should the proj

Simply communicating resource requirements without a plan to address the shortfall doesn't solve the problem, especially when constraints are tight.

While updating the risk register is a good practice, it's not the primary action to resolve the resource deficiency problem and ensure project viability; it's merely documenting a symptom.

Reducing project scope unilaterally without formal stakeholder approval is inappropriate; the WBS defines scope, but changes to it must follow a change control process.

When resources are insufficient for the defined scope under tight schedule and cost constraints, the project becomes unachievable as planned. The most responsible action is to initiate a formal scope change request with stakeholders, proposing adjustments to the project scope that are realistically deliverable with the available resources, schedule, and budget. This ensures alignment and sets realistic expectations.