Industry Favorites: Product Backlog Resources

Ahhh, Spring is finally upon us. Temperatures are rising, leaves are popping out, and before we know it the yellow-crush of pollen will be here. In the spirit of “spring cleaning” we’re doing to take this spring to focus on cleaning house when it comes to Product Backlogs.  This month the majority of our content, webinars, newsletters, and resources will focus on Product Backlog Definition & User Story Creation. As we turn the corner for May Showers we’ll take the conversation to the next level and start exploring the real art of backlog management and how to support and elaborate your backlog items.

To kick-off this content mini-series, we thought it would be useful to showcase some of the outstanding resources from across the industry.

  • 7 Product Dimensions from Discover to Deliver
    • This short video introduces the concepts of the 7 product dimensions, and the Discover to Deliver site has a list of resources related to that content. (
  • Uncomfortable Truths About User Stories (YouTube Video)
    • There are so many great things about this video, and it’s worth finding the 80 minutes to watch the whole thing, even if you need to do it in 4 roughly 20 minute chunks. Jeff Patton makes a particularly interesting comparison of developing features to an artist producing a work of art from 59:00 to 1:00:54 that ties in very well to the next link…
  • Splitting User Stories: the hamburger method
    • We find ourselves sharing this link with more and more people because how Gojko Adzic describes and depicts splitting user stories is very clever. Many people struggle with splitting stories because they’re concerned with building every component in the perfect end state, which simply isn’t possible to do in short sprints. Gojko explains how to think of splitting stories to decide how to write stories that iterate to the desired end state. Definitely worth a read…and a bookmark.
  • What Characteristics Make Good Agile Acceptance Criteria?
    • Acceptance Criteria are critical to defining the boundaries and specific needs of a User Story. This blog post is a concise description of what should be included in Acceptance Criteria with some great examples.
  • The Difference Between a Story and a Task
    • Mike Cohn discusses how something that seemed so clear in his head wasn’t so easy to answer, and takes us on the thought process to a simple, clear answer that should help distinguish between what is a Story and what is a Task. (hint: a Task is not just a smaller Story)