Scrumcrazy_header5.jpg
scrumcrazybtn.jpg

For Training, Coaching, and Consulting engagements, please contact me for details on how I can help your organization.


Ebin Poovathany has written a wonderful article on how we should focus more on the verbal conversation aspects of User Stories rather than focusing too much attention on "writing" User Stories. I myself have written an article about this as well (See Trap #'s 1, 8, 10,and 13). It's great to see that this topic is starting to get more attention in the industry.

As Ebin points out, using so called "User Story Templates" ("As a user, I want..", "In order to...I want...", etc) causes people to backslide into older waterfall habits, and creating the same old kinds of documents that we used to create in waterfall, along with the same old problems. He said this is sad, and as a User Story proponent, I agree. It's a horrible misunderstanding, but it's rampant in our industry. The User Story practice was always intended as a very close, highly 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 your five minutes to read Ebin's article, and be sure to share it with your teams and organizations too!

To learn how to avoid User Story Traps and maximize your User Stories practice, see more info about our User Stories Class.




coaching(4).jpgForScrumMasters.jpgForProductOwners.jpgForScrumDevelopers.jpgPresentations.jpg