On Jan 8, 2018, at 2:04 PM, rexbroo <rexb@starbourne.com> wrote:Seriously crazy-making quicksand quagmire! People tend to tend think in hierarchies and try to impose hierarchies almost whenever they can. Hierarchy in this case is not necessary.
However, I somehow derived a set of definitions that works for me:
A Feature is a function (usually a business function, but not necessarily), such as get customer account information, add item to shopping cart, get credit authorization, get current customer account balance, confirm shopping cart contents, upload as blog article, etc.
A User Story describes using a Feature or set of Features, such as checking account information on a website, making a cash withdrawal, adding a review to an article on a blog, etc.
An Epic is a set or collection of related User Stories, building an online retail store, maintaining an online retail store, merging an online retail store into a whole supply company.
Cheers,
Rex
On 1/3/2018 9:40 AM, Ken Laskey wrote:
https://softwareengineering.stackexchange.com/questions/182158/relationship-between-user-story-feature-and-epic
------------------------------------------------------------------------------
Dr. Kenneth Laskey
MITRE Corporation, M/S H330 phone: 703-983-7934
7515 Colshire Drive fax: 703-983-7996
McLean VA 22102-7508
-- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670