This week's book giveaway is in the Clojure forum.
We're giving away four copies of Clojure in Action and have Amit Rathore and Francis Avila on-line!
See this thread for details.
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

User Stories

 
arnel nicolas
Ranch Hand
Posts: 149
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Halloo,

Maybe this is a dumb question for you guys. I want to know if there is a proper way to compose user stories? What should be the content? and how should
I compose the tasks of this story?

TA
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, a user story should represent something about the system being developed that is valuable to the customer.

Some people like to use a formal template for describing their user stories, e.g. As a (role) I want (something) so that (benefit). Using such a template generally helps you think about who (role) a certain feature is built for and why (benefit). Some people don't bother explicitly mentioning the role or the benefit. Some people just write a couple of words down and call it a user story. After all, a user story isn't intended to fully describe the feature but rather serve as a handle.

Have you read Mike Cohn's "User Stories Applied"? If not, I highly recommend it.
 
arnel nicolas
Ranch Hand
Posts: 149
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks. i will check your recommendation
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Also take a look at http://www.xprogramming.com/xpmag/expCardConversationConfirmation.htm
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic