|
Posts: 135 / Nickname: fsommers / Registered: January 19, 2002 7:24 AM
Defining "Done" in User Stories
January 6, 2010 5:00 PM
|
|
In this article, I discuss a common mistake with the popular "user story" requirements format: poorly defined done criteria:
http://www.artima.com/articles/defining_done.html How do you define done when implementing user stories? |
|
Posts: 3 / Nickname: mangelguy / Registered: June 1, 2010 4:42 PM
Re: Defining "Done" in User Stories
July 1, 2010 7:45 PM
|
|
I agree with your article. A good use case saves a great deal of time and is what good scrums are made of.
I think though that your example is wanting. The only way to ensure that the user is the true controller of the email address is to send him/her an email. In other words, the problem has already been solved. When the problem has already been solved, scrum is very fast and effective as well - no need to re-create the wheel - unless of course it's shaped like a hexagon. |
|
Posts: 1 / Nickname: pmahoney / Registered: December 26, 2012 1:02 AM
Re: Defining "Done" in User Stories
December 26, 2012 7:09 AM
|
|
I agree all teams should have a shared definition of done that is used as a template for determining if a story is complete or "Done". IMO the examples listed are more aligned with the concept of what are acceptance criteria. My thoughts of Done would include: testing completed and passed, code review completed, code standards followed and alike, these things should be true for all code related user stories.
Just a thought Paul |