CAPM Practice: Determine how to gather requirements

Legacy replacement is requirements-intensive: BAs must discover undocumented legacy functionality (shadow IT, workarounds), capture data migration requirements, define integration specifications for remaining systems, and manage the transition period where old and new systems may coexist.

**Why not A:** Claiming that legacy systems have already been replaced and present no challenges is unrealistic. Most organizations carry significant legacy systems, and replacing them involves substantial complexity including data migration, business rule preservation, integration dependencies, and user transition planning.

**Why not C:** Dismissing legacy requirements as not worth capturing is a dangerous assumption. Legacy systems often encode critical business rules and institutional knowledge that may not be documented elsewhere. Failing to capture these requirements can lead to gaps in the replacement system that disrupt business operations.

**Why not D:** Legacy system replacement is not simpler because existing systems define all requirements. While legacy systems provide a reference point, they often contain outdated processes, workarounds, and undocumented behaviors. The replacement effort must also account for new business needs, modern architectural patterns, and the elimination of obsolete functionality.