The stakeholder of a new product that is in early adaptive development has requested a change to an approved feature. How should the business analyst (BA) handle this change?

Switching the business analysis approach to predictive because of a single change request contradicts the adaptive methodology and eliminates its core benefits of flexibility.

A formal change request approval process is a predictive (waterfall) control mechanism, not aligned with adaptive development practices.

Including the requirement in the next iteration bypasses proper backlog prioritization and may displace higher-priority work without team and stakeholder agreement.

Adaptive approaches use the product backlog as the central mechanism for managing and prioritizing all requested changes and features. Adding the change to the backlog ensures it is visible, can be estimated, and will be prioritized by the product owner against other items before being scheduled into a future iteration.