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

ERP implementations from established vendors typically come with defined implementation methodologies (SAP's ACTIVATE, Oracle's OUM, etc.) — inherently predictive in nature. Well-documented business processes reduce requirements uncertainty. A predictive approach following the vendor methodology with formal change control for customizations is most appropriate. Customizations should be managed as formal scope changes, not ad-hoc adaptive decisions, because ERP customizations often have significant downstream implications.

**Why not B:** Building a custom methodology rather than following the vendor's established implementation framework introduces unnecessary risk. ERP vendors develop their methodologies based on hundreds of implementations, and deviating from them often leads to integration problems and support issues.

**Why not C:** Pure agile Scrum is inappropriate for an ERP implementation with a defined vendor methodology and well-documented processes. ERP customizations have significant downstream implications that require formal change control, not ad-hoc sprint-based decisions. Discovering new requirements does not necessitate abandoning the vendor's structured approach.

**Why not D:** Deferring all ERP configuration decisions to implementation sprints ignores the well-documented business processes and the vendor's defined phases. ERP implementations require structured planning to manage the complex interdependencies between modules, data migration, and integration points.