Timeline for How can agile be applied to applications involving complex processing?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2017 at 1:03 | comment | added | evanmcdonnal | @RobertHarvey I agree the technical details are irrelevant to the user but my point is that the artifacts containing user stories have a broader purpose than just communicating how things work for the user (or they should at least). How does one enforce requirements related to architecture, extensibility, performance and so on if they write purely user stories? Taking a pure 'user story' approach incentivizes developers to write poor quality code. And it's not users reading the 'user stories' it's devs and qa, it's foolish to deliberately exclude relevant information because it's technical. | |
| Aug 16, 2017 at 0:17 | comment | added | Robert Harvey | I'm all for being flexible, but frankly the user doesn't particularly care about the technical details, so long as their stories get satisfied. You don't have to be "strictly agile" to have good requirements; and by good requirements, I mean requirements that are each accompanied by an acceptance test that unambiguously proves the requirement is satisfied. The folks that are "engaging in very silly exercises" are obviously doing it wrong, but that doesn't mean they're following some notion of "strict scrum." | |
| Aug 15, 2017 at 23:59 | history | answered | evanmcdonnal | CC BY-SA 3.0 |