I presented on The Art of Storytelling - User Stories Smells and Anti-patterns at the Agile2016 conference held in Atlanta, GA. I'd previously presented variations of this talk at 2015…
1. Thinking that everything is a user story Many mistakenly believe that if you are Agile or using Scrum, then you must use user stories and no other format is…
Looking at the user story template, which part of the user story is the most important part? Is it the Who, What, Why, How, or Acceptance Criteria? Let’s first look…
When splitting user stories, we should always split them vertically as if we are slicing a piece of cake. The whole cake is a cake and each vertical slice is…
Product Backlog Items (PBIs) or user stories should be small. Small stories provide focus for the team and gives members the flexibility to adjust and adapt to changes. The larger…
Here are the top 3 reasons to split a user story: Size – Large user stories need further refinement to break them down into more manageable pieces. Key indicators that…
Bill Wake came up with the INVEST acronym to help us remember guidelines for writing effective user stories: Independent, Negotiable, Valuable, Estimatable, Small, and Testable. Independent: As much as possible,…
Before we look at why use user stories, let’s first start by looking at other common requirement gathering techniques. 1st, there is the IEEE 830 with “The system shall… “,…
A user story is one way of representing requirements in a Product Backlog. Mike Cohn defines a user story as a simple, clear and short description of customer valued functionality.…
At AgileDC2015, I presented on Lean Discovery, Agile Delivery and a DevOps mindset. Below is the abstract of the talk, along with links to the Digital Service Delivery blog series…