Agile and Beyond 2018

User stories and their big brothers, epics, are a great way to manage requirements for a software system. They act as stakes in the ground to keep track of what the system needs to do, the type of user most interested in each feature, and the reason it provides value to them. As projects reach a significant size, many stories become too large for a team to finish within a single sprint, and must be split into smaller stories that can be completed within a sprint. Many Scrum teams struggle with this process, not knowing how to properly split epics and large stories in an effective manner to keep each split story shippable. Software development expert Dave Todaro will step you through proven techniques to split epics and user stories, making them smaller and more manageable, while sticking with the Scrum rule that each user story must deliver value. During this session you’ll learn: How splitting user stories increases the team’s momentum and throughput. Why tackling 3 to 4 smaller stories in a sprint is less risky than taking on just one or two. When to split stories, and where you should focus your time in the product backlog. Techniques to make each story “shippable,” even if it’s not big enough to ship on its own. A rule of thumb for how big each user story should be.