By nature of my job, I often see a situation where the team strives to "fix the analytics", for example, by introducing User Stories.
And for some reason, the result rarely meets expectations. The reason for this is often the misconception the analyst has about user stories themselves. It often turns out that it was not the analytics at all but the software development process.
More often than not, the peculiarities of the process prevent the right stories from being used or the stories from being used correctly.
In my talk, I will tell you about the content and context of using user stories in which a team can get the most out of implementing this awesome approach to requirements definition.