In the noble business of analysis, we use different tools and methods to describe processes and functions. But in the end, the analyst is expected to work out the requirements, describe the functions and clearly formulate the development task.
In my talk, I would like to share the practice of writing a development task formulation.
How to systematize all the knowledge about the described task and fit them into a single document, without getting confused and not to confuse your colleagues.
I will give you a specific example of a template for the problem statement, tested on more than one development team. I will tell the story of its appearance, describe its composition and areas of application.