Timeline for Techniques to write good acceptance criteria for user stories
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 8, 2015 at 6:51 | comment | added | Pacerier | @TristaanOgre, What's a "steel thread" all about? | |
| May 13, 2011 at 16:54 | comment | added | TristaanOgre | I've found that, when using this methodology of softare development and design, the user story is definitely the key. Get a good handle on that, and everything just falls into place. If the user story is too general, you end up getting bogged down and dragging out development. If it's too specific, then you get bogged down in a lot of little detailed stories. Finding that balance is key. | |
| May 13, 2011 at 16:42 | vote | accept | ale | ||
| May 13, 2011 at 16:42 | comment | added | ale | I like the idea of the "steel thread". I started under the assumption that our user stories were good enough, but maybe we need to start from there. If the user story is good, coming up with the acceptance is easier. Thanks, taking it as an answer, it gives me something to work with. | |
| May 13, 2011 at 15:36 | history | edited | TristaanOgre | CC BY-SA 3.0 |
Added acceptance test 6
|
| May 13, 2011 at 15:15 | history | answered | TristaanOgre | CC BY-SA 3.0 |