Being in the audit field for so many years now, I often come with such situations where the client ask us to perform extra task which was not the part of original scope. In such situations, i normally discuss with the client about the additinal efforts and time required to complete the additional tasks. This helps us to determine the additional fees for the extra tasks to avoid confussion at the later stage. The best way to handle such situation is to have a open discussion with the client as well as the team members. This will ensure we are alligned with respect to fees, nature and timing for additional tasks. However, we should be realistic while giving the deadline to the client as well as to the team members.

When clients request new features mid-project, it’s crucial to remain flexible while safeguarding project goals. Begin by employing a MoSCoW prioritization technique to classify the request into must-haves, should-haves, could-haves, or won't-haves, ensuring clarity on urgency and feasibility. Use an impact mapping tool to visualize dependencies and assess changes on scope, timeline, and resources. Engage the Scrum team for collaborative evaluation during a sprint review or backlog grooming session. Update the project roadmap and communicate adjustments transparently to stakeholders to maintain alignment and deliver value effectively.

When a client requests changes mid-project, it is important to pause, evaluate and understand the root of the request. Consider whether the change request is the best course of action to address the root concern and support the client to come to the best resolution. Listen and be flexible but safeguard the project goals in the first instance. Assess the impact of the change and clearly communicate how the change will affect the project scope, schedule and cost. Map the impact to show the dependencies of the project. Prioritise must-haves and suggest including the wants as add-ons at the end of the project. Striking a balance between client needs and project constraints is important. Maintain transparency of the changes to all stakeholders.

When clients request new features mid-project, I pause and evaluate. First, I clarify their needs—sometimes it’s more about tweaking what’s already planned. Then, I explain the impact: timeline, budget, or trade-offs. If it’s a must-have, I prioritize it and adjust the scope, keeping the team looped in. For nice-to-haves, I suggest adding them post-launch or in a later phase. The key is balancing flexibility with focus—showing you’re listening while protecting the project’s core goals. Staying calm and solution-focused keeps everyone on track.