PMP Practice: Determine critical information requirements

Integration of project planning activities requires analyzing interdependencies between competing constraints and collaboratively developing solutions that balance multiple objectives. In this scenario, Ocean faces three constraints: regulatory compliance (non-negotiable), weather-driven schedule risk, and a firm business deadline tied to external commitments. The best approach is to bring key stakeholders together to analyze the full scope of the tradeoff and explore alternative solutions. Alternative testing methodologies, parallel activities, phased implementation, or creative scheduling might address both compliance and weather constraints without defaulting to either extreme. This collaborative analysis ensures the integrated plan reflects all critical factors rather than optimizing for a single dimension. The scenario's closing fact—that the project is currently on schedule and within budget—indicates there is planning flexibility to explore options before defaulting to schedule extension or risk acceptance.

**Why not B:** This approach treats the testing extension as the only option and accepts both the missed deadline and cost overrun without exploring alternatives. While regulatory compliance is critical, the project manager should first investigate whether creative solutions exist that maintain compliance while addressing weather and business constraints. Immediately conceding the deadline without collaborative problem-solving fails the integration responsibility.

**Why not C:** This solution appears to resolve the conflict but introduces a new variable—crashing the schedule through additional shifts—without analyzing its full impact on cost, quality, team capacity, or feasibility. The stem provides no information about available labor resources, union constraints, or whether pipeline work can be safely accelerated. Making this decision unilaterally without stakeholder consultation and proper impact analysis contradicts integrated planning principles.

**Why not D:** This approach prioritizes the construction schedule while pressuring the engineering lead to accept compressed testing that may compromise compliance verification. Having someone 'sign off' on reduced testing does not eliminate regulatory risk—it merely transfers accountability inappropriately. A project manager should never ask a technical expert to certify that a compromised approach meets standards just to preserve schedule. This creates compliance risk and undermines professional responsibility.