Usually, the analyst writes the requirements for the task in advance. However, sometimes the analyst gets caught within the framework of existing processes in the team, where analytics goes in parallel with development. In this situation, his or her work may turn into fixing changes and creating documentation for the sake of documentation.
But is it possible to find a plus in this approach as well? How to get out of this situation and provide quality analytics?
I have tried to do it by combining this approach with the classical one to develop the best solution.