The main thing I'm trying to answer is this: What are the distinguishing features between a "new feature" and a "product enhancement" when it comes to software development? Specifically, when applied to Scrum.
Here are some possible criteria that come to mind:
The other possibility is that I'm thinking about this all wrong and there's better, clearer terminology that should be used.
With respect to defects, a fault raised around the way a function works (e.g. navigation, position of buttons, usability etc) is an enhancement request. A change request is more heavy duty - either changing the way an existing function works or adding a new function.
Software Feature Enhancement means (i) feature enhancements that materially improve functionality or performance of Software and that Supplier markets as a separate commercially available product or (ii) custom developed features for Sprint or another customer of Supplier.
Enhancement is adding some new functionality or feature in existing build. Defect is again bug but "Bug with its favourable conditions" which makes it defect. If bug is removed the defect will automatically vanished.
A user story is a chunk of functionality (some people use the word feature) that is of value to the customer. What you call a feature is usually referred to as theme or epic. Themes and epics are used to group user stories to bigger feature sets, that make sense on their own.
I guess this cannot be answered in a generally accepted way. However this is how I would put it:
A feature is new functionality i.e. a user can do something new with the software. An enhancement makes doing something that was possible before simpler, more powerful or adds somehow to existing functionality.
+1 for Christian's answer. Another way to look at it is:
When the initial "new" feature is delivered to the customer or product owner; do they come back with a bunch of requests to modify the feature? Do they report a number of "defects" against the feature that arose because the initial feature story(s) were not fully documented?
These are enhancement requests to existing functionality and in Scrum would be considered enhancement backlogs or stories. If the request describes new value to the customer that was not captured in the initial feature story(s) it is not tech debt, or a defect; it is an enhancement.
If you are using an enhancement story to address scope change or make a case for additional resources:
High level Agile planning usually results in a product roadmap of sorts with feature level milestones (aka should be feature complete in a given quarter, release, etc); any other stories that modify that feature area after the feature complete date or production release of the feature can be considered enhancement requests.
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