Menu
I guess a feature could be something like "credit card authorization", while a user story may be "authorize credit card for paypal".
So, is a user story a subset of a feature?
392
A feature is what everyone else refers to as an epic, A user story is a type of story. Epics can be broken down into capabilities which can be broken down into features which can be broken down into user stories.
What is a feature in Agile methodology? A feature is a service or function of the product that delivers business value and fulfils the customer's need. Each feature is broken down into several user stories, as it is usually too big to be worked on directly.
A user story can be moved to the Completed status when all of its associated tasks are closed. Any team member that is associated with an active team on the product can move a user story to Completed status.
For a team of 7 developers you would have over 20-40 user stories which is likely way too many. It also subtly takes the focus off of swarming and puts attention toward a developer per story. 5 to 15 user stories per sprint is about right. Four stories in a sprint may be okay on the low end from time to time.
Yes, something like a subset. This article is a good read:
Features vs Stories
Excerpt:
I realized today that I hadn't made explicit the difference in my mind between features and stories and it's an important difference. Essentially, a feature is a group of stories that are related and deliver a package of functionality that end users would generally expect to get all at once. For instance, inline table resizing is a feature (note: this is the ability to drag to resize tables, rows and columns – try it in Word). In the first pass, you'd probably have a single story for inline resizing of tables, but it would be too big to estimate. So you break it down into three stories, resize columns, resize rows and resize the table itself.
144
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
