Timeline for Where does documentation like business and software requirement spec docs fit in an agile project?
Current License: CC BY-SA 4.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 11, 2019 at 13:39 | answer | added | Alex Singh | timeline score: 1 | |
| Feb 28, 2019 at 16:23 | vote | accept | Majd Kassem | ||
| Feb 26, 2019 at 14:12 | vote | accept | Majd Kassem | ||
| Feb 26, 2019 at 15:08 | |||||
| Feb 26, 2019 at 14:12 | vote | accept | Majd Kassem | ||
| Feb 26, 2019 at 14:12 | |||||
| Feb 26, 2019 at 14:10 | vote | accept | Majd Kassem | ||
| Feb 26, 2019 at 14:12 | |||||
| Feb 26, 2019 at 14:06 | vote | accept | Majd Kassem | ||
| Feb 26, 2019 at 14:06 | |||||
| Feb 26, 2019 at 14:03 | vote | accept | Majd Kassem | ||
| Feb 26, 2019 at 14:06 | |||||
| Feb 26, 2019 at 0:00 | history | tweeted | twitter.com/StackProjects/status/1100183778390089728 | ||
| Feb 25, 2019 at 21:36 | comment | added | Tiago Cardoso | Hi Mjd - once one of the answers fit your needs, kindly mark it accordingly to help further the community! Happy to see your question flourish with so many good answers. | |
| Feb 25, 2019 at 17:26 | answer | added | Michael Durrant | timeline score: 3 | |
| Feb 25, 2019 at 16:07 | comment | added | Majd Kassem | if we can not collaborative to gathering requirements we are not Agile at all, we try to not tend toward mini-waterfall in each iteration so we are going to use only user stories | |
| Feb 25, 2019 at 15:45 | comment | added | Majd Kassem | good, we are going to implement Agile as scrum,we will try to gathering the requirements as user stories with their acceptance criteria, we all as a team believed in Agile added values, we agreed that user stories will be as a single source of truth for all participaters, we hope to success and sense the Agile powerfullity | |
| Feb 25, 2019 at 14:57 | comment | added | Stephen Byrne | If you can manage to get every single relevant person related to the project implementation (stakeholders, technical leads, testers, end users, etc etc) in one room long enough to get all requirements written down as stories, then yes you can just use those as your requirements. (Sutherland's original Scrum book has a real example of this happening. But these days I'd say it's rare to be able to do that). Otherwise, unfortunately you probably do need some kind of BRS/SRS and you let the BRS be the "source material" for stories, with the SRS as a technical guide for the implementation team | |
| Feb 25, 2019 at 3:15 | comment | added | Pace | If the test team is deeply integrated in the development and participates in the creation of the story and acceptance criteria this can work. If the test team is external to the development team I think this would be trickier. | |
| Feb 25, 2019 at 1:53 | answer | added | JJ Ward | timeline score: 4 | |
| Feb 24, 2019 at 18:41 | history | edited | Tiago Cardoso | CC BY-SA 4.0 |
Rephrased to focus better on key problem
|
| Feb 24, 2019 at 18:30 | comment | added | Majd Kassem | Good i will,based on your experience, as a development team, can we implement the code based on user story bounded with acceptance criteria.In our current model the SRS feed into development team and testing team use the same document to verify the developed feature | |
| Feb 24, 2019 at 18:02 | comment | added | Pace | If your company has an existing workflow that uses BRS and SRS then you should find out how those documents are used. What purposes are they serving? Who reads them and what do they do with them? Talk to the consumers of these documents about what they would need and if they feel your user stories would satisfy these needs. | |
| Feb 24, 2019 at 17:17 | answer | added | Daniel | timeline score: 9 | |
| Feb 24, 2019 at 17:02 | answer | added | Tiago Peres | timeline score: 13 | |
| Feb 24, 2019 at 16:50 | review | First posts | |||
| Feb 24, 2019 at 17:02 | |||||
| Feb 24, 2019 at 16:49 | history | asked | Majd Kassem | CC BY-SA 4.0 |