CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

For legacy system replacement, understanding the current system's capabilities, workarounds, and pain points is essential. Many replacements fail because they replicate problems of the old system or miss undocumented functionality that users depend on.

**Why not A:** Selecting technology before understanding business requirements puts the cart before the horse. Technology selection should be driven by clearly defined business needs, not the other way around. Choosing a platform first risks investing in a solution that does not address the actual pain points of the current system.

**Why not C:** Interviewing only the IT team provides a narrow, technical perspective. While IT maintains the system, business users, process owners, and other stakeholders understand the day-to-day pain points and business capabilities the system supports. A comprehensive understanding requires input from all relevant stakeholder groups.

**Why not D:** Jumping straight into documenting requirements for the new system without first understanding the current state risks missing critical context. Requirements gathered without understanding existing business capabilities and pain points may replicate existing problems or overlook important functionality that users depend on in the legacy system.