Loading ...
Sorry, an error occurred while loading the content.

Re: [XP] Re: Level of detail in User Stories

Expand Messages
  • yahoogroups@jhrothjr.com
    From: Thomas Eyde To: extremeprogramming@yahoogroups.com
    Message 1 of 2 , Feb 20, 2006
    • 0 Attachment
      From: "Thomas Eyde" <thomas.eyde.at.gmail.com@...>
      To: "extremeprogramming@yahoogroups.com"
      Sent: Monday, February 20, 2006 8:03 AM
      Subject: Re: [XP] Re: Level of detail in User Stories

      > Hi.
      > Isn't it better to focus on user goals, then deduce the necessary
      > actions from there? In that case, the pattern would be more like:
      > "As a <role> I need to accomplish <goal> by doing <actions>"

      The "canonical" pattern is " <role> needs to accomplish <goal>
      [to achieve <business objective>]

      See "Effective User Stories" by Mike Cohn.

      John Roth

      > --
      > Thomas
      > On 2/20/06, Anthony Williams <anthony_w.geo@...> wrote:
      >> It strikes me that this is the user stories are at the wrong level. It
      >> may be
      >> that they really do need to modify all 70 options, but you are also right
      >> that
      >> most users will only change 10. The best format for user stories I've
      >> seen
      >> goes along the lines of "as XXX, I want to do YYY, so as to accomplish
      >> ZZZ". e.g. as a standard user, I want to change option FooBar, so I can
      >> flomulgate the wibble. As an advanced user, I want to change option Baz,
      >> so I
      >> can flomulgate the wibble without also goofering the wombat.
      > To Post a message, send it to: extremeprogramming@...
      > To Unsubscribe, send a blank message to:
      > extremeprogramming-unsubscribe@...
      > ad-free courtesy of objectmentor.com
      > Yahoo! Groups Links
    Your message has been successfully submitted and would be delivered to recipients shortly.