Comments on: User Story Writing http://lostechies.com/chrispatterson/2007/11/27/user-story-writing/ Just another LosTechies site Mon, 06 May 2013 07:30:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Jarod Ferguson http://lostechies.com/chrispatterson/2007/11/27/user-story-writing/#comment-12 Jarod Ferguson Tue, 27 Nov 2007 07:59:53 +0000 /blogs/chris_patterson/archive/2007/11/27/user-story-writing.aspx#comment-12 Hey Chris, I asked a similar question about 'stories that arent stories' a while back over at elegantcode.com. I thought David gave a great post: http://elegantcode.com/2007/08/17/backlog-items-tricks-and-tips/ Hey Chris, I asked a similar question about ‘stories that arent stories’ a while back over at elegantcode.com. I thought David gave a great post:

http://elegantcode.com/2007/08/17/backlog-items-tricks-and-tips/

]]> By: Scott Bellware http://lostechies.com/chrispatterson/2007/11/27/user-story-writing/#comment-11 Scott Bellware Tue, 27 Nov 2007 07:12:36 +0000 /blogs/chris_patterson/archive/2007/11/27/user-story-writing.aspx#comment-11 > I didn't really get into acceptance criteria in this post because > that in itself is a series of posts Actually... you did: "When a user is modifying a held claim, changes to the billing code elements should cause those elements to be reverified. If the billing codes are changed to valid codes, the claim hold should be removed." and "When an application administrator uploads a file containing billing codes, the existing billing code table should be cleared and the new codes added" are both examples of acceptance criteria. These describe details of how the solution will behave or how it will look that can be tested or otherwise verified by whichever members of the team can appropriately claim accountability for its completion. Aceptance criteria are the things that convey enough design and test ideas to jumpstart the implementation of the story's solution. You may very well be an acceptance criteria if you describe some aspect of the solution and if you can be verified. > I didn’t really get into acceptance criteria in this post because
> that in itself is a series of posts

Actually… you did:

“When a user is modifying a held claim, changes to the billing code elements should cause those elements to be reverified. If the billing codes are changed to valid codes, the claim hold should be removed.”

and

“When an application administrator uploads a file containing billing codes, the existing billing code table should be cleared and the new codes added”

are both examples of acceptance criteria.

These describe details of how the solution will behave or how it will look that can be tested or otherwise verified by whichever members of the team can appropriately claim accountability for its completion.

Aceptance criteria are the things that convey enough design and test ideas to jumpstart the implementation of the story’s solution.

You may very well be an acceptance criteria if you describe some aspect of the solution and if you can be verified.

]]>