Timeline for How can agile be applied to applications involving complex processing?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 4, 2017 at 20:18 | vote | accept | Frank Puffer | ||
| Aug 18, 2017 at 6:56 | history | edited | code_dredd | CC BY-SA 3.0 | Clarified statements |
| Jul 25, 2017 at 11:54 | comment | added | code_dredd | @FrankPuffer Yeah, that's expected whenever a paradigm shift takes place b/c it means replacing fundamental assumptions. | |
| Jul 25, 2017 at 9:55 | comment | added | Frank Puffer | Ok, I misread the "wouldn't" as "would". And yes, I find your answer very helpful and will probably accept it. I probably just need some time to get accustomed to the idea of not considering user stories as requirements. | |
| Jul 25, 2017 at 8:46 | comment | added | code_dredd | @FrankPuffer Yeah, that's why I said I wouldn't be surprised. That said, I'm wondering my answer has clarified anything for you. Was the SVN vs Git analogy helpful? (It assumes you're familiar with both systems, which seemed reasonable in a software development context.) | |
| Jul 25, 2017 at 6:59 | comment | added | Frank Puffer | Requirements management systems like PTC Integrity treat requirements as a hierarchy. This can be an advantage when mapping requirements to a specification document. | |
| Jul 25, 2017 at 0:29 | comment | added | code_dredd | @FrankPuffer I think viewing user stories as if they're a different level in a hierarchy of requirements is basically mixing different concepts. On the Agile side, a hierarchy looks more like: Themes >> Epics >> Features >> User Stories >> Tasks. Requirements are usually divided into functional and non-functional requirements in the more traditional Waterfall approach, but I've not come across an actual hierarchy; that said, I wouldn't be surprised if someone were to recursively break down a requirement into smaller "sub"-requirements. In any case, you're mixing different concepts. | |
| Jul 24, 2017 at 11:21 | comment | added | Frank Puffer | "User Stories != Requirements": I didn't mean to say that the two are synonyms. Not every requirement is a user story. But I do think that all user stories are requirements. I view requirements as a hierarchical structure where user stories are one specific level of detail. Would you agree? | |
| Jul 24, 2017 at 10:01 | history | edited | code_dredd | CC BY-SA 3.0 | Reformatted sub-titles due to typos |
| Jul 24, 2017 at 5:54 | history | answered | code_dredd | CC BY-SA 3.0 |