What you do next matters.

Is there a hierarchy to stories in agile projects

In my projects I often have a story (some work that can be done in an iteration) and an epic (something that will take more than an iteration).

I then break my stories into

  • User story (As a user I want to do something so I gain some benefit)
  • Performance cards (the system will be able to do something by iteration sometime) and
  • Experiments (we want to know something so we will do something and measure something).

But I think I am out of step with the rest of the agile world.  I am told there is now more of a hierarchy that goes like this …

IMG_20150522_102611

Does that look right to people?

One response to “Is there a hierarchy to stories in agile projects”

  1. A skills backlog with a capability table – James King Avatar
    A skills backlog with a capability table – James King

    […] able to do in order to deliver value to customers. Some people include a capability in their “story hierarchy” as kind of a big epic or, I guess, “saga.” Others, often process engineers, use […]

    Like

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.