Abstract:
Agilists employ user stories as a way to capture user requirements and drive the planning process for iterative and incremental delivery of software. Traditionalists with experience in “big requirements up front” often struggle with the brevity of user stories and how to best communicate requirements. In this presentation, we will look at common anti-patterns and mistakes that teams unknowingly employ when writing user stories. Come learn how to identify and avoid these mistakes. Understand what size is the right size for a user story and how to properly split a user story. Discover different boundaries for prioritizing stories. Learn how to decompose a story until it is ready for development. Leave with new insights on how to write effective user stories.
Learning Outcomes:

• Spotting user story smells and anti-patterns
• Understanding that not everything is a user story
• Properly sizing user stories
• Understanding when and how to split user stories
• Importance of Definition of Ready
• Progressive Story elaboration

Attachments:

• User_Story_-_Smell___Anti-patterns_cover.pdf