In my recent article on telling user stories instead of writing user stories, I mentioned that many Scrum Teams focus way too much on documentation and way too little on good collaborations.
More support for this concept comes from the first chapter in Gojko Adzic’s new User Story book, Fifty Quick Ideas to Improve your User Stories.
User stories imply a completely different model: requirements by collaboration. Hand-overs are replaced by frequent involvement and discussions…. If requirements are just written down and handed over, this discussion does not happen. Even when such documents are called stories, by the time a team receives them, all the important decisions have already been made…. Try telling stories instead of writing down details. Use physical story cards, electronic ticketing systems and backlog management tools just as reminders for conversations…Engage business stakeholders and delivery team members in a discussion, look at a story from different perspectives and explore options. That’s the way to unlock the real benefits of working with user stories.
Gojko has been nice enough to publish the “Tell stories, don’t write them” chapter available completely free here! It is also important to note, that this chapter is tip #1 in his book, as it really sets the stage for the best use of the User Story practice.
The User Story practice was always intended as a very close, verbal collaboration between the Dev Team and the PO/Customer. In modern times, you can achieve this very easily with good Product Backlog Refinement practices.
Anyway, it’s totally worth another five minutes of your time to read Gojko’s free chapter, and be sure to share it with your teams and organizations too!
Filed under: Agile, Extreme Programming, Product Backlog, Product Backlog Grooming, Product Owner Tips, Scrum, Scrum Patterns, Scrum Strategies, ScrumMaster Tips, User Stories | Tagged: acceptance criteria, Agile, Extreme Programming, Scrum, user stories |