Using Job Stories Instead of User Stories

User stories and their format defined by Mike Cohn “As a , I want so that .” are a classical way to record requirements in Scrum project. In his blog post, Alan Klement discusses a new format that he called “Job Stories” with the format “When … , I want to … , so I can … .”

For Alan Klement, the problem with the user stories format is that it is too much based on assumptions and doesn’t take into account the context. He thinks that the persona (user) concept is a bad idea because they lack reality. The job stories format deals with the situation, the motivation and the expected outcome of the requirements. He gives some examples when rewriting requirements from user stories to job stories makes them better.

In a following post, Alan Klement give five tips for writing job stories. These are:

  1. Refine A Situation By Adding Contextual Information
  2. Job Stories Come From Real People Not Personas
  3. Design Modular Job Stories Which Features (Solutions) Can Plug Into
  4. Add Forces To Motivations
  5. Job Stories Don’t Have To Be From A Specific Point Of View

This second post explains these tips in detail.

Read the two blog posts about job stories on http://alanklement.blogspot.de/2013/09/replacing-user-story-with-job-story.html and http://alanklement.blogspot.ch/2013/09/5-tips-for-writing-job-story.html

Related Content:

Be the first to comment

Leave a Reply

Your email address will not be published.


*