User stories are the cornerstone of agile requirements. Teams use them to plan and deliver solutions that meet their users’ needs. Beyond just solution requirements, user stories focus on value delivery from the perspective of the user.

However, user stories can be tricky to write in a way that they are understood by our stakeholders and the delivery team. It’s easy to think everyone is on the same page and we’re in agreement on what is expected, but then find we’re wrong. All too often, stories are not delivered in a sprint due to them being too big, not scoped correctly, or missing detail.

This session will explore how to write effective user stories using the 3 “S’s”: Simple, Single and Specific. These three simple guides can help us to assess our stories to ensure they are sized appropriately and well understood.