Re:Manifesto for Half-Arsed Agile Software Development
by UK-AL on Wednesday January 15, 2014 @12:44PM
(#7064728)
Normally a good User Story, with 5 - 20 lines of acceptance criteria are optimal size for change/feature request.
[ Parent
| on HN ]
Re:Manifesto for Half-Arsed Agile Software Development
by wpietri on Wednesday January 15, 2014 @03:07PM
(#7065783)
Personally, I now consider that too long. I have built entire products using index cards with nothing more than 3-8 words on them, plus occasional temporary artifacts (whiteboard sketches, mocks, etc).
In my view, stories are tokens for conversation. Now when I deal with teams who are writing down more than a few words, I look for barriers to conversation. E.g., not all the right people sitting together, or too much work in process.