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

A mobile app for a rapidly changing market requires flexibility to adapt to evolving user needs and preferences — characteristics better suited to an adaptive (agile) approach. The other examples have stable, well-defined requirements making them good candidates for predictive methodology.

**Why not A:** Building a residential home according to pre-approved architectural drawings has well-defined requirements, sequential construction phases, and regulatory compliance needs — all strong indicators for a predictive approach. The drawings define scope upfront, making predictive planning effective.

**Why not B:** Installing a well-understood enterprise software system following a standard protocol has stable, documented requirements and a proven installation process. These characteristics make it a strong candidate for predictive methodology.

**Why not C:** Constructing a bridge with detailed engineering specifications has clearly defined requirements, sequential work phases, and regulatory constraints. Bridge construction follows established engineering processes that align perfectly with predictive project management.