> the business team is constantly changing priorities based on new client requests, so the tech team cannot cope with all the new features and these end up suff

> the business team is constantly changing priorities based on new client requests, so the tech team cannot cope with all the new features and these end up suffering continuous delays. I would recommend... — keeping a list of feature requests sorted by popularity, number of client requests, and impact to your KPI / north star metric — prioritize each milestone / sprint based on this list, this can be for the next week, month, quarter, depending on the complexity of the project, then measure — agree with the management team to not change the priority midway unless there is a very good reason to do so You can use a variety of tools to do this, from the traditional Google Suite of tools to more specialized task management tools like Asana, Trello. We mainly use a combination of GitHub issues and Taskade (our own tool) to do this.