By the nature of my job, I often witness how a team strives to "fix the analysis", for example, by adapting User Stories.
And somehow, 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 analysis at all but the software development process.
Even more often, the peculiarities of the process prevent the proper stories from being used or the stories from being used properly.
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.