What would you do if the client changed requirements in the middle of a project?
Understand exactly what changed and why, assess the impact on time, cost and existing work, discuss options with your lead, and make sure the change and new timeline are agreed in writing before starting.
Explain it simply
Requirements change in almost every real project. The mistake freshers make is either refusing ("we already agreed") or quietly doing it and then missing the deadline.
Clarify the change, work out what it affects, and raise it with your lead so the team can agree options with the client: extend time, drop something else, or deliver in phases. Get the final decision recorded in an email or the ticket so everyone has the same understanding.
Example
Situation: In her final-year project for a local NGO, Priyanka's team was asked, two weeks before submission, to add Hindi language support to their app.
Task: Handle the change without missing the college deadline.
Action: She asked the NGO which screens volunteers used most and found it was only the registration and attendance screens. She estimated full Hindi support would take three weeks, but those two screens only four days. She discussed this with her guide and the NGO, and they agreed in an email to do those two screens now and the rest after submission.
Result: The project was submitted on time, and the NGO was happy with the phased plan.
What to say in the interview
"I'd clarify what changed and why, assess the impact on time and other work, discuss options with my lead and the client, and get the agreed change recorded before starting."
Common mistakes
- Refusing all changes.
- Accepting silently and then missing the deadline.
- Not documenting what was agreed.