Scrum promises teams will produce a usable product increment at the end of each sprint. This means designing, coding, testing, and having the product owner accept the work of the team, typically in two short weeks.

Most teams struggle with this process. Stories can quickly turn into layers–one for the back end and one for the front end–or product owners may get caught up in debates around what is truly "usable."

In this session, software development expert and agile author Dave Todaro will leverage a real-life example to explain how to leverage a variety of techniques to learn the art of thin slicing.

Key takeaways:
* Why it's so important to build the product in thin, vertical slices to avoid "building 100% of nothing"
* When epics and user stories are too large and need to be split
* The right time to perform the splitting process and who should be involved
* Two models you can lever for splitting stories
* Using the INVEST mnemonic to ensure the quality of your split stories