Timeline for How much detail about a user story can a developer expect?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 4, 2014 at 22:24 | comment | added | sleske | @Wolfgang: About "decisions the customer will revert": This will happen, not matter what methodology you use. Only in Agile, it happens sooner, so less effort is wasted. | |
| Apr 8, 2013 at 5:12 | comment | added | Ashkan Kh. Nazary | +1 for the point on the "bare- bones". Some vague points though ... | |
| May 10, 2012 at 20:08 | vote | accept | Wolfgang | ||
| May 10, 2012 at 19:49 | comment | added | Wolfgang | I like the idea of dividing stories up. It might make them a little too small (like 2 hours instead of 2 days) but think that's okay. Actually, I'd love that because it improves the software structure (decoupling) because developers are forced to separate features out and commit them separately. What I'm still concerned about is that I might be forced to make uninformed decisions that the customer will revert, so it might become inefficient. But your point about the "minimum needed" totally hits the mark! | |
| May 9, 2012 at 19:31 | history | answered | Karl Bielefeldt | CC BY-SA 3.0 |