A feature is a collection of requirements that need to be delivered as part of a product.
The requirements that form a feature can generally be broken down into stories that form the scenarios which are used by the feature and/or they can simply be the use cases for which a feature can be handled – both are very similar.
In short, I like to think of it in this way – it’s a big thing we want to give to our customers that cannot be delivered in a single sprint, BUT we want that big thing delivered to our final customer all at once.
Enter the use of stories that break down the delivery into sprints.
In simpler terms, your customer wants a bucket, not a bucket with a bunch of holes in it, how you build the bucket they don’t care, but they want it to have a handle and hold water.