User Story Splitting: how and why to add details to user stories

In the Scrum process (as well as in other Agile methodologies) there is an inconspicuous ritual - sprint planning meeting. It is usually described as a simple prioritization of stories from the product backlog and selection of those that the team takes to work on this sprint. In fact, this is where the magic happens: user stories from the product backlog turn into sprint tasks. It's not often you hear exactly how they turn, with not every story fitting into the sprint without losing value.

The speaker wants to close this default. He'll break down more than ten techniques for breaking down stories into more detail, so that they fit into the sprint framework while still being meaningful and bringing value to users. And at the end, you'll get to practice breaking them down yourself. The session is aimed at analysts, product organizers, and the teams themselves - in general, anyone who works in short iterations and strives to deliver comprehensible value in each of them.