Epic vs Feature vs Story
Kevin
"Theme") and Story?
1) An Epic consists of many features and 1 feature of many stories?
Or
2) A Feature consists of 1 or many Epics and one Epic can be split
into many stories?
In the following link, Feature ("Theme") appears to be the uppermost
item in the hierarchy, formed by 1 or more Epics which at the same
time consists of 1 or more stories:
http://agile101.net/wp-content/uploads/2009/08/the-difference-between-themes-epics-user-stories-and-tasks1.jpg
This other post suggests the same thing:
http://agilesoftwaredevelopment.com/blog/artem/epics-and-themes
The Agile Project Mgmt tool "Mingle" suggests something like 1)
above: Epic > Theme > Story
Mike Cohn, on the other hand, seems to state the opposite, although it
is not completely clear to me (a Theme "is a collection of related
stories", an Epic "is a large user story" -- page 19):
http://www.mountaingoatsoftware.com/system/presentation/file/119/Cohn-ADP09-Introduction-to-User-Stories.pdf
I am confused, what's the correct answer?
Chet Hendrickson
I have yet to see an issue in a real project where the answer was to segregate the user stories by size and give each group a name.
I suggest you don't worry about it. Call them all stories and realize that the bigger ones will need to be broken down before we can work on them in a sprint.
chet
Best regards,
Chet Hendrickson mailto:li...@hendricksonxp.com
Check out our upcoming CSM Plus courses @
http://hendricksonxp.com/index.php?option=com_eventlist&Itemid=28
Gustavo Cebrian Garcia
My rule is that at the very very very maximum, a feature does not have to be bigger than 10 days. Some people say 2 days ( I think it is very little)
Gustavo.
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To post to this group, send email to scruma...@googlegroups.com.
To unsubscribe from this group, send email to scrumallianc...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scrumalliance?hl=en.
Chet Hendrickson
I recommend that stories be no more than 3 days work for a developer pair.
chet
Alan Dayley
hierarchy of these terms. Or the don't have hierarchy at all.
Most teams I've worked with have stories with any story that needs to
be split called an epic. A theme is a group of stories that apply to
a area of the product. A theme may have three stories or 42, it just
depends. Themes in these cases are a way to classify or group
stories, not bigger epics that are then split.
Having said all that, the definition of these terms is not that
important. An organization usually will organically figure out what
these terms mean. If such definitions are a problem, spend five
minutes of a backlog grooming session to define them and move on with
the work.
Call them what you will, it's far more important that your Product
Backlog Items be discussed, trimmed and fairly small when the go into
development during a Sprint.
Alan
Aquarius
See: http://agilesoftwaredevelopment.com/blog/artem/epics-and-themes
for detailed explanation.
> > This other post suggests the same thing:
> >http://agilesoftwaredevelopment.com/blog/artem/epics-and-themes
>
> > The Agile Project Mgmt tool "Mingle" suggests something like 1)
> > above: Epic > Theme > Story
>
> > Mike Cohn, on the other hand, seems to state the opposite, although it
> > is not completely clear to me (a Theme "is a collection of related
> > stories", an Epic "is a large user story" -- page 19):
George Dinwiddie
> and how much do you break them down, that is the thing.
I've found that's really easy to answer /if you really know what's in
the story/. Concrete examples make this simple. See
http://blog.gdinwiddie.com/2011/05/01/splitting-user-stories/
- George
--
----------------------------------------------------------------------
* George Dinwiddie * http://blog.gdinwiddie.com
Software Development http://www.idiacomputing.com
Consultant and Coach http://www.agilemaryland.org
----------------------------------------------------------------------
andrej...@gmail.com
All you must know is size of each item and velocity of the team.
Br,
Andrej
www.agilemindstorm.com
On Jun 9, 6:32 pm, Kevin <kkra...@gmail.com> wrote:
> What is the hierarchy between Epic, Feature (in some places called
> "Theme") and Story?
>
> 1) An Epic consists of many features and 1 feature of many stories?
> Or
> 2) A Feature consists of 1 or many Epics and one Epic can be split
> into many stories?
>
> In the following link, Feature ("Theme") appears to be the uppermost
> item in the hierarchy, formed by 1 or more Epics which at the same
> This other post suggests the same thing:http://agilesoftwaredevelopment.com/blog/artem/epics-and-themes
>
> The Agile Project Mgmt tool "Mingle" suggests something like 1)
> above: Epic > Theme > Story
>
> Mike Cohn, on the other hand, seems to state the opposite, although it
> is not completely clear to me (a Theme "is a collection of related