OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [soa-rm] Relationship between user story, feature, and epic?


As evidenced by the recent move from SAFe 4.0 to 4.5, the methodology is still evolving, and anyone who has taken one of the courses can tell you where they saw holes.

Ken
------------------------------------------------------------------------------
Dr. Kenneth Laskey
MITRE Corporation, M/S H330          phone: 703-983-7934
7515 Colshire Drive                           fax: 703-983-7996
McLean VA 22102-7508

On Jan 8, 2018, at 3:37 PM, Natale, Bob <RNATALE@mitre.org> wrote:

I too can live with any self-consistent set of definitions.
 
I do believe, however, that the Agile community – and especially a variant as dense as SAFe – should have a quasi-standard set of self-consistent definitions for them (and several other associated terms) … me and Don Quixote! 😊
 
Avanti,
BobN
 
From: soa-rm@lists.oasis-open.org [mailto:soa-rm@lists.oasis-open.org] On Behalf Of Martin F Smith, BFC Consulting
Sent: Monday, January 08, 2018 3:27 PM
To: Laskey, Ken <klaskey@mitre.org>; Rex Brooks <rexb@starbourne.com>
Cc: soa-rm@lists.oasis-open.org
Subject: Re: [soa-rm] Relationship between user story, feature, and epic?
 

Guys-- that works OK for me, but I had in mind a slightly different idea--

A Feature is the implementation of a function needed to fulfill a Story (i.e., a set of functional requirements expressed as a scenario or use-case.)

A Story is a set of functional requirements expressed as a scenario or use-case.

An Epic is a description of the overall performance of an application (perhaps limited to the perspective of one type of stakeholder, e.g., a customer, a business end-user, or an administrator.)

But like I say--I can live perfectly well with Rex' version. 

Martin

On 1/8/2018 2:45 PM, Ken Laskey wrote:
I’ll buy these. 
 

Ken

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:
------------------------------------------------------------------------------
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 
 
 
-- 
Martin F Smith
BFC Consulting, LLC
McLean, VA
703 389-3224 mobile 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]