Story-o-Types: Patterns Within User Stories

Have you noticed that similar stories appear over and over as you develop a system? According to Dan Rawsthorne, stories-those small chunks of work that make up your backlog and provide demonstrable value to the project-can be categorized by purpose: production, analysis, cleanup, business support, infrastructure/environment, or other. Within each of these categories are different "story-o-types"-patterns that define the commonalities among the stories themselves. Dan defines and describes some of the most common story-o-types, explains why they are useful, and demonstrates the concept with examples including "Alternate Path" and "Clean-Up Interface" for the production category, "Talk to Stakeholders" and "Exploratory Testing" for the analysis category, and others. For each story-o-type, Dan provides sample tasks and canonical "doneness" criteria that make planning and backlog grooming easier and more consistent. By employing story-o-types when developing your stories, your team will produce more consistent, higher quality requirements.