A business stakeholder contacts you to makes some changes in the requirements for a project on which you have already put in a lot of effort and time. How do you handle situations like this?
This is a hybrid operational and behavioral question. It creates a scenario and asks you how you would react to it. Your answer can be based on either a real experience you had with a similar incident in the past or by describing what you would do if you encountered this situation after you start in this position.
"In business, change is a constant, especially in the role of an IT business analyst. I spend time with stakeholders to discuss the project and understand it completely before I begin working on it, but change invariably occurs. If the stakeholders change the requirements for the project after I have begun working on it, I would meet with them to discuss the new parameters to both understand the new parameters and appraise the team of how the changes impact the project. I would then summarize the meeting in writing to ensure we were in agreement and that everybody is on the same page."
Community answers are written by other candidates practicing this set. Reading how others frame the same question is one of the fastest ways to sharpen your own.
Anonymous Answer
In business, change is always constant, I would meet with them to discuss the new requirements to both understand the new requirements and update the team on how the changes impact the project.
Marcie's Feedback
So it sounds like you're accepting of change and don't let it bother you, which is great. The steps you mention - meeting with the client to discuss the new requirements and then updating your team so they understand the impact of these changes on the project - are logical and reasonable. Consider adding more details about how you'd proactively control scope creep from the start of the project as well (e.g., clearly defining the scope of the project at the beginning, communicating with the client throughout the entire project, being transparent, providing development/testing time estimations). Taking these initial steps might help to avoid client changes further into the project.
Anonymous Answer
First, I listen to the stakeholder and asses two main factors is the requirements addressing the organization's strategic goal (yes or no), and two, is this going to increase my scope (addition or removal). If it is a pet project requirement that does not make the solution substantially better I politely declined, if the request comes from someone above my rank I cordially loop my supervisor in. In the case that it does indeed is oriented towards the organization's goal and is useful then I consider the request. It is important to carefully consider all requirements changes, since not doing this may lead to scope creep and project delays.
Amanda's Feedback
Your response is diplomatic and balanced. It also illustrates that you are a competent communicator and insightful team player, able to distinguish between business needs and non-essential changes or projects.
Unlock all 29 IT Business Analyst questions
Master questions that bridge technical complexity and business needs in IT interviews.
Get Started