Timeline for What is the difference between user stories and features?
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2012 at 8:35 | comment | added | sleske | I guess ultimately it's just a matter of definition. It's useful to have some way to group multiple user stories, and you can either call that grouping "epic" (and consider "feature"=="user story"), or you can call the grouping "feature" (implying "feature">="user story"). I think some people even use epic >= feature >= story. The important thing is to be aware that the term is used differently by different people. | |
| Jan 5, 2012 at 8:32 | comment | added | sleske | BTW, related question & answer: stackoverflow.com/questions/1714557/… | |
| Jan 5, 2012 at 8:19 | comment | added | sleske | @AaronMcIver: Yes, that is true. However, sometimes the miminum amount of functionality that is truly useful to the user (=feature) is too much for a user story (or even for an iteration). In that case you must break down the feature into several stories. | |
| Jan 4, 2012 at 13:56 | comment | added | Aaron McIver | @sleske A user story in a pure Scrum approach should be value add to the user and thus a feature. If we are going to catalog features as overarching Epics that is fine but the end result is user stories which deliver value. | |
| Jan 3, 2012 at 13:38 | comment | added | sleske | I don't think you can say they are the same, even if they are related terms. What about features that span several user stories? | |
| Mar 16, 2011 at 17:18 | history | migrated | from stackoverflow.com (revisions) | ||
| Mar 15, 2011 at 16:11 | comment | added | murrekatt | +1, this explains it well. I would not necessarily say feature == user story, except when you talk about business value or client value. In other cases, respective term might not have a meaning. | |
| Mar 15, 2011 at 14:38 | history | answered | Aaron McIver | CC BY-SA 2.5 |