Timeline for Is an user story totally a requirement from the user?
Current License: CC BY-SA 4.0
6 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Oct 24 at 8:21 | comment | added | Phill W. | +1 for the "ask the User Why? ... 19 times". What they initially say they /want/ is all too often nothing like what they actually /need/! | |
Oct 23 at 23:33 | history | edited | Greg Burghardt | CC BY-SA 4.0 |
added 80 characters in body
|
Oct 23 at 23:31 | comment | added | Greg Burghardt | @DJay I wish there was one true way to get requirements from users. The closest I've found is to talk to your users. Know that software is about people first, solving problems second, and technology third (with security woven throughout all three). You might be interested in the Agile Manifesto and Human-Centered Design. Volumes of books have been written on the topic as well. | |
Oct 23 at 21:40 | comment | added | D Jay | would you have some reference that would help me to ask some questions to extract requirements from the user, I am working to automate a current manual administrative process | |
Oct 23 at 21:20 | vote | accept | D Jay | ||
Oct 23 at 21:14 | history | answered | Greg Burghardt | CC BY-SA 4.0 |