
No company-specific verbatim questions are publicly documented for IBM Philippines BA interviews; this question aligns with confirmed topics on handling scope changes. IBM looks for BAs who can uphold project discipline while remaining adaptable, crucial in global delivery engagements with evolving client needs.
Use a specific example that highlights your role in the change management process: identifying the change, assessing impact, communicating options, and reaching a consensus. Convey that you value both business agility and project governance.
Start by grounding your story in the change itself, not in your reaction to it. Say plainly what shifted, whether it was a new regulatory requirement, a client request that arrived mid-sprint, or a stakeholder who redefined a deliverable after sign-off. Then walk through your process in the order you actually did it. Explain that you first documented the change and its trigger, because in a BPO or global delivery setting, an undocumented change is a dispute waiting to happen. Next, describe how you assessed the impact on timeline, resources, and the original business objective, and be honest that you did not just accept the new scope at face value. You quantified what it would cost in hours or milestones. From there, say that you presented two or three options to the decision makers, each with a trade-off, and you recommended one. That is the assertive part. Frame it as protecting the project's integrity, not as refusing the client. Finally, mention that you updated the traceability matrix or change log and communicated the new baseline to the team, so everyone worked from the same version of reality. Keep your tone measured and your language professional, but you can shift into a slightly more conversational Taglish register when describing how you aligned with local stakeholders, as long as you keep the core of the answer structured and confident.
Filipino candidates, especially in BPO/IT settings, sometimes say, 'Sinabi ko na lang pong gagawin namin, wala nang reklamo' (I just said we would do it without complaint). This comes across as lacking assertiveness. Instead, show how you used a formal process to manage expectations and negotiate priorities professionally.
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.
Scope changes are inevitable; structured impact analysis and transparent options always lead to the best compromise.
Write your own answer, then get instant AI feedback graded against:
Get AI feedback on your answer — free.
3 free AI-graded answers + 1 free mock interview, no card needed.
Sign Up FreeAlready have an account? Log in
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.