Is Scrum User Story the same as function

Question

In his Whats in Dan North post, the founder of BDD seems to use the word Story instead of Feature, and this is not the only place I've seen before. Why does this especially bother me is that I'm working on a team that uses Jira / Greenhopper, so we do Kanban with Scrum. Scrum has its own terminology, and User Stories is among this set of terms.

So my question is: Is Feature / UserStory Dan north tied to the same as UserStory in Scrum?

If it is not then (rhetorically) "why use it as such"?

Answer 1

I think this is debatable if the user's history (or should be) is always closely related to the function and vice versa.

But, by definition, the user's story is not . These are different things.

User History :

In software development and product management, a user story is one or more sentences in the everyday or business language of the end user or system user, which captures what the user does or must perform as part of his work.

Software function :

"A distinctive feature of a software item (such as performance, portability, or functionality).

---

This is a truly open and vague description of the function of the software, but not for the history of the user. The user story must respect a specific format for a specific purpose: you can answer the question of when, where, who and / or why in the user's history (depending on what format you intended).

IMO, if you already use user stories, you should not worry about this relationship, just make sure your user stories are well written.

Answer 2

This is probably for discussion, but I believe that a function is a way of grouping one or more stories. For example, you might have the “Image Upload” feature, which consists of two steps:

• Customer can upload image
• Administrator can approve or reject and depict

I generally think of a “tag” as how a business / client would initially describe the behavior. As you get closer to creating it, you then divide it into stories to set priorities and evaluate.

Answer 3

If you look at the Scaled Agile Framework , the guys there have put together a large separation of different types of artifacts, including Epics, features and stories. It also displays at different levels of scale within the organization, which is pretty cool.

In my use, Feature is something more than a standalone Story, something that is tracked at a higher level of the organization, and is usually involved in a release plan to dictate what will happen in this version.

A Story is what we use to describe the scenarios in which this feature will be used so that we can create functionality to support all Feature-related Stories.