Before taking any action, the project manager should gather more context and engage the team to assess feasibility. This includes evaluating schedule impacts, resource constraints, regulatory implications, and whether scope trade-offs are required. This approach aligns with the PMBOK Guide's recommendation to evaluate change impacts before making decisions.
Option A is misaligned; root cause analysis is more appropriate for problem resolution, not for scope acceleration.
Option B assumes approval and feasibility without review.
Option C applies to Agile backlog reprioritization but this is a regulatory milestone, likely not in a product backlog.
References:
PMBOK Guide - Seventh Edition, Delivery and Planning Performance Domains PMBOK Guide - Sixth Edition, Section 4.6: Perform Integrated Change Control

The project manager should take two actions to deal with the situation of the neighbors resisting the project and threatening legal action. One action is to publish information on the city's website about the benefits that the new tram station will bring, such as improved transportation, reduced traffic, increased safety, and enhanced economic development. This action can help to inform and educate the public about the project's value proposition and address any misconceptions or concerns that the neighbors may have. The project manager can also use other communication channels, such as social media, newsletters, or press releases, to reach a wider audience and increase awareness and support for the project12.
Another action is to register this situation as a risk and develop a mitigation plan. A risk is an uncertain event or condition that can have a positive or negative effect on the project's objectives. The situation of the neighbors opposing the project and threatening legal action is a negative risk that can potentially cause delays, cost overruns, reputation damage, or even project cancellation. The project manager should identify and document this risk in the risk register, along with its probability, impact, and priority. The project manager should also develop a mitigation plan to reduce the likelihood or severity of the risk. The mitigation plan may include actions such as engaging with the neighbors, negotiating with them, offering them compensation, or seeking legal advice34. References: = PMBOK Guide, Sixth Edition, pages 376-377, 414-415; 8 Steps for Better Issue Management, Step 5: Communicate with the team; PMBOK Guide, Sixth Edition, pages 395-
396, 443-444; Project Risk Management - A Quick Guide, Step 3: Plan Risk Responses.

To estimate the savings using in-house resources, the project manager would apply the PERT formula to calculate the expected duration of the project. The PERT formula is ( TE = \frac{(O + 4M + P)}{6} ), where TE is the expected time, O is the optimistic time, M is the most likely time, and P is the pessimistic time1.
Given the optimistic term of 4 months, the most expected term of 5 months, and the pessimistic term of 6 months, the expected duration (TE) would be ( TE = \frac{(4 + (4 \times 5) + 6)}{6} = \frac{(4 + 20 + 6)}{6}
= \frac{30}{6} = 5 ) months.
The total cost for in-house resources for 5 months would be:
* Two engineers: ( 2 \times US$700 \times 5 = US$7,000 )
* One project manager: ( US$1,600 \times 5 = US$8,000 )
* Additional expenses: ( US$2,000 \times 5 = US$10,000 )
Total in-house cost: ( US$7,000 + US$8,000 + US$10,000 = US$25,000 )
The company paid US$60,000 to an external subcontractor last year. Therefore, the estimated savings would be: ( US$60,000 - US$25,000 = US$35,000 ) However, since the options provided do not include US$35,000, and the closest option to the calculated savings is US$40,000, the answer would be C. US$40,000. This discrepancy might be due to additional factors not accounted for in the question's details, such as indirect costs or a margin of error in the estimates.
References:
Program Evaluation and Review Technique (PERT) Formula1
PERT Example Calculation2
Professional in Business Analysis (PMI-PBA) Examination Content Outline3

When a delay occurs, it is essential for the project manager to engage with the team to understand the reasons behind the delay. This approach aligns with the principles of both Project Management and Business Analysis, where communication and problem-solving are key to addressing project challenges. By discussing the issue with the team, the project manager can gather insights into the root causes of the delay and work collaboratively to find a solution that minimizes the impact on the project milestone. This method is preferred over immediately seeking assistance from senior management or reallocating resources, which may be more disruptive and less informed actions at this stage.
The approach of discussing delays with the team is supported by the PMI's guidance on dealing with project delays, which emphasizes the importance of understanding the causes of delays and working with the team to resolve them1. Additionally, the Professional in Business Analysis materials highlight the significance of stakeholder engagement and communication in managing project challenges2.