User Stories and Story Splitting

In Scrum and other Agile methods, a common way to manage feature requests is with User Stories.  I’ve been teaching people about User Stories and doing workshops with teams for a long time.  Out of that work, I’ve created a very simple PDF User Stories and Story Splitting reference sheet that might be handy.  Please feel free to download it and share it.  This document is something that I explain in-depth in my Certified Scrum Product Owner training seminars.

There are a number of sites out there that include some details that are left out of the reference.  Please see, for example, “Patterns for Splitting User Stories” by Richard Lawrence.  See also the great foundational article on “INVEST in Good Stories” by Bill Wake.

The format of a user story provided in the attachment was developed in conduction with Michael Hamman and Kara Silva and a number of other Agile coaches at Capital One in the 2004-2005 time frame.

Affiliated Promotions:

Register for a Scrum, Kanban and Agile training sessions for your, your team or your organization -- All Virtual! Satisfaction Guaranteed!

Please share!

2 thoughts on “User Stories and Story Splitting”

  1. Mishkin,

    While I believe that your PDF has a lot of value, I have a couple of improvement suggestions. So many people, when learning about User Stories, forget about the 3 C’s of User Stories. Specifically, they tend to fall into old waterfall habits of written requirements like that suggested by the US template. They also forget about one of the other important components of a User Story — the test confirmations (aka story tests, acceptance tests, etc). I’d love to see your PDF stress those aspects so that people don’t forget. Thanks again for taking the time to put together the PDF.

    For more info on the improvements I suggested, see this article on User Stories on the Agile Atlas:

    [Even though I’m a co-author of the article, I’m not trying to promote myself here. The Co-inventor of User Stories, Ron Jeffries, was our editor for this article.]

    1. Hey Charles! Thanks for the note. I agree that the third “C” is not very well represented on this pdf. It’s something I will think about how to update. Also, thanks to the link on the Agile Atlas.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.