In Scrum and other agile frameworks, the product owner is responsible for managing the product backlog and prioritizing work based on business value. If new requirements arise, they should not be added mid-sprint.
Instead, they should be assessed, prioritized, and-if accepted-incorporated into planning for the next sprint.
According to the Agile Practice Guide and Scrum Guide, the Sprint Backlog is frozen during a sprint to maintain focus and stability. The Product Owner can then introduce new tasks during the next planning session.
Option A and B violate Scrum principles by modifying the sprint backlog mid-sprint.
Option C reflects a predictive approach that is inappropriate in Agile settings.
References:
Agile Practice Guide, Section 3.1 - Role of the Product Owner
The Scrum Guide (Scrum.org), Sprint Planning and Product Backlog sections
-

During execution, any addition to scope must go through the formal change control process. The project manager should initiate a change request for proper evaluation and approval. This ensures that scope, budget, and schedule impacts are assessed before proceeding.
According to the PMBOK Guide - Seventh Edition, any changes to the baseline during execution must follow the change control procedures defined in the governance structure.
Option A risks scope creep.
Option B is helpful but not sufficient as a next step.
Option C closes the door without considering the critical nature of the request.
References:
PMBOK Guide - Seventh Edition, Delivery and Planning Performance Domains PMI Change Control and Governance Guidelines

Bottom-up estimation is the most detailed and least risky method, especially in complex projects like international construction with localized legal constraints. It allows for the incorporation of precise data, including legal compliance costs, permitting, and regulatory timelines.
The PMBOK Guide - Seventh Edition identifies bottom-up estimating as highly accurate because it breaks down the work into smaller packages and estimates each individually. This method is especially useful when local context is critical and legal factors may impact cost.
Option A (parametric estimation) assumes standard historical metrics, which may not be valid across jurisdictions.
Option B (top-down with contingencies) is higher risk and less precise.
Option C is vague and may miss crucial localized compliance costs.
References:
PMBOK Guide - Seventh Edition, Cost Performance Domain
PMI Practice Standard for Project Estimating
-

Enterprise Environmental Factors (EEFs) include governmental regulations, safety standards, organizational culture, legal requirements, and industry standards. Since the engineers are asking about safety prerequisites- typically defined by regulatory or compliance bodies-the project manager should refer to EEFs, which contain mandatory information regarding safety policies.
According to the PMBOK Guide - Seventh Edition (Environment Domain), EEFs are inputs that influence project success and must be considered when defining requirements like safety.
Option B (benchmarking) helps improve performance but doesn't ensure compliance with formal safety standards.
Option C (lessons learned) provides past project insights but may not reflect updated safety prerequisites.
Option D (hiring an expert) may be unnecessary if the relevant safety standards are already documented in EEFs.
References:
PMBOK Guide - Seventh Edition, External Environment Considerations
PMI, "Environmental Factors and Organizational Process Assets," Resource Guide
##############################################