Putting the “Story” Back into the User Story
If you're using user stories for your agile requirements, you're not alone. They seem to have become the ubiquitous vehicle for communicating customer requirements to agile teams. And they work incredibly well in this regard. However, many teams are experiencing problems with them. Bob Galen does not believe it’s the story’s fault. Bob says we often forget the “conversation” part of the story—and more importantly, the storytelling part. When Kent Beck first described the idea of the user story, his original intent was to initiate or inspire a story-level conversation between a stakeholder or customer and the team implementing it. User stories were to be face-to-face and interactive. They were intended to not only inform but also to inspire. It was to be an ongoing process. Bob brings our focus back to the original intent of the user story—that is, the story part. Explore how you can tell better stories to enhance your agile teams’ collaboration, understanding, and ultimately their results.