CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach

Pipeline projects are quintessential predictive candidates: regulatory specifications define the scope, fixed contracts lock in deliverables, government approvals require formal documentation and stage gates. The structured, document-intensive nature of predictive methodology aligns with these requirements. Underground conditions are managed as risks within the predictive framework, not through iteration.

**Why not A:** While some pipeline phases could theoretically use iterative planning, the dominant project characteristics — regulatory permits, fixed contracts, and multi-jurisdictional governmental approvals — strongly favor a fully predictive approach. The hybrid suggestion underestimates how pervasive the regulatory and contractual constraints are across all project phases.

**Why not B:** Cross-jurisdictional complexity does not require agile; it requires structured coordination and formal documentation. Frequent stakeholder collaboration is important, but it is managed through the communications plan and stakeholder engagement within a predictive framework, not through agile ceremonies.

**Why not C:** While underground conditions can be unpredictable, these are managed as risks within the predictive framework using contingency plans, not through adaptive iteration. The regulatory specifications and fixed contracts are the dominant characteristics, and they clearly mandate a structured, documentation-intensive predictive approach.