Timeline for How do you keep track of a requirements document on an agile team?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 6, 2021 at 9:21 | comment | added | andrew.fox | The process described here may be OK for writing software for your own company. Software Houses can't afford not having the spec. And most of the time User Stories are the spec. | |
| Jan 20, 2021 at 2:29 | comment | added | Matthew Flynn | @DXM In the years since I answered this, I've very much come around to your stance on the subject of requirements. BDD, ATDD, and clean code are by far the best way to capture and maintain knowledge of what software should and actually does do. | |
| May 21, 2016 at 2:48 | comment | added | Didier A. | The Acceptance Tests you talk of, these sound to me like documented test cases? Am I correct, or are they actual runnable tests? | |
| Dec 3, 2012 at 4:01 | history | edited | DXM | CC BY-SA 3.0 | deleted 5 characters in body |
| Dec 3, 2012 at 4:00 | comment | added | DXM | ... my team always kept everything but we didn't even have any detail in our stories, so I still don't understand what value those stories provided, but like many others, my boss was very adamant about not throwing anything out. | |
| Dec 3, 2012 at 3:59 | comment | added | DXM | @SimonWhitehead: since you were not the only one that made that comment, I updated my answer. My team never threw away a single story either. So how often have you had to go back 2 years in the past and dig up those old stories for reference? And what kind of info did you get out of them. How was the detail of your stories compared to what Bob Martin (books.google.com/…) describes (especially 3rd paragraph under User Stories section? Just curious, were your stories talking points or did you actually capture ALL requirements?... | |
| Dec 3, 2012 at 3:50 | history | edited | DXM | CC BY-SA 3.0 | added 1652 characters in body |
| Dec 3, 2012 at 3:20 | comment | added | Simon Whitehead | I just want to add that my team and previous teams havent been story "chuckers". We keep them for reference. | |
| Nov 30, 2012 at 8:42 | history | edited | DXM | CC BY-SA 3.0 | added 137 characters in body |
| Nov 30, 2012 at 6:14 | history | edited | DXM | CC BY-SA 3.0 | added 2 characters in body |
| Nov 30, 2012 at 6:13 | comment | added | Frank | +1 for pointing out the difference between requirements and user stories to the OP. | |
| Nov 30, 2012 at 5:13 | history | answered | DXM | CC BY-SA 3.0 |