The first question to ask is why the team members are expanding the scope. Scope expansions should be requested by the customer and the PM with the help of the tech team (Architects and/or Consultants), this scope should be validated. This looks to me like a situation in which the provider has no control over the project, probably due to a lack of processes, control, governance, communication, definition of roles and responsibilities and methodology. This is very basic stuff, to be honest... If I were the customer and my vendor did this... it would raise a serious red flag, big enough to think about cancelling the contract.

To ensure the project stays within scope, start with a clear and detailed project scope document and a comprehensive plan outlining tasks aligned with the agreed scope. Conduct weekly meetings to review progress and ensure alignment with the defined scope. Highlight any scope changes as early as possible to address them proactively. Use reliable project management tools to maintain a complete and easy view of project tracking and progress. Regularly remind the team about the project's scope and its importance. For any change requests, ensure thorough discussions to evaluate their impact on timelines and costs, making sure they don’t jeopardize the project’s success.

Managing scope creep in IT consulting requires clear communication and disciplined project management. I start by defining and documenting detailed project boundaries, ensuring all team members understand and agree on the objectives. Regular check-ins help monitor progress and quickly address any deviations. Utilizing project management tools allows me to track tasks, manage resources, and flag unauthorized changes early. By fostering a culture of accountability and focusing on client-approved deliverables, I ensure the team remains aligned with the project’s original scope.