Timeline for Defining user story in Scrum: how specific must they be?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 23, 2014 at 14:51 | comment | added | pksnj | Thanks David. To add to my post, PO decides 'What' is to be done and the team decides 'How' it will be done. | |
| Dec 19, 2014 at 12:31 | comment | added | David Arno | I agree here. The examples in the question are not good stories. "User insert email and password in the textboxes and click the login button" is a description of how a story will be implemented. "The user will log into the system by supplying their email and password, which will be checked against stored records" would be a better user story. The purpose of stories is to specify requirements, not how it'll be implemented. | |
| Dec 7, 2014 at 5:03 | review | First posts | |||
| Dec 8, 2014 at 9:22 | |||||
| Dec 7, 2014 at 5:00 | history | answered | pksnj | CC BY-SA 3.0 |