Tell me about a time when the scope of a project you were working on changed unexpectedly. How did you handle it?

Situation

As a BA supporting an e-commerce platform migration, two weeks before go-live the client's CEO requested an additional payment gateway integration that had never been discussed. This was a major feature that would affect the checkout funnel, back-end reconciliation, and the sprint velocity.

Task

I needed to assess the impact of this scope change, communicate the consequences to all stakeholders, and facilitate a decision on whether to include it without derailing the timeline or quality.

Action

First, I logged the request formally in the change control log. I then led a quick impact analysis with the tech lead and QA, estimating an additional 3 weeks of development and testing. I called an emergency change review meeting with the product owner, project manager, and key sponsor, presenting a one-page trade-off matrix: accept the delay, de-scope a lower-priority feature, or add temporary headcount cost. I facilitated a discussion that focused on business value vs. risk.

Result

The stakeholders agreed to de-scope two nice-to-have features of lower priority, freeing up enough capacity to deliver the payment gateway in the original timeline. We launched successfully, and the new gateway contributed to a 15% increase in checkout conversion within the first quarter.