Requirements change. Managing that well is part of the job (BABOK: Requirements Life Cycle Management). A change request records what is asked, by whom and why. The BA then runs an impact analysis:
- Requirements and design: which ones change, which are added, which become obsolete. The traceability matrix finds them.
- Tests: which cases must change or be added.
- Cost and schedule: effort and dates, from the delivery team.
- Risk: what could go wrong if we do it, and if we do not.
- Other stakeholders: who else is affected.
The analysis goes to whoever owns the decision (the sponsor, the product owner or a change board), with options: accept, reject, defer to a later release, or accept a smaller version. The BA does not decide; the BA makes the decision easy to make well.
A change that "looks small" often is not: one new field can touch the form, the database, the migration, three reports and nine test cases.