From Red Hat Agile Day, Oct. 20, 2015. Session 1 Core Track:
If you’re using User Stories for your agile requirements, you’re not alone. It seems to have become the ubiquitous vehicle for communicating customer requirements to agile teams. And it works incredibly well in this regard. However, many teams are experiencing problems
with it. And I don’t believe it’s the story’s fault.
You see we often forget the “conversation” part of the story, and more importantly, the story-telling part. When Kent Beck originated the idea of the User Story, this was his original intent. It was to initiate or inspire a story-level conversation between a stakeholder or customer and the team implementing something to meet their needs. It was face-to-face and interactive. It was intended to inform, but also inspire. It was also ongoing.
Join Bob Galen in this talk that brings our focus back to the original intent of the User Story; that is the story-part. We’ll explore how to tell better stories to enhance the results of your agile teams’ collaboration, understanding, and ultimately their results.