There's a movement in software development to replace large requirements documents with short user stories. That's a good thing because stories eliminate hand offs and add a dash of fun.
User stories can also be used by marketing, event planners and other groups to define their product or experience.
There are three terms you should become familiar with to understand user stories — Stories, Epic and Themes.
Epics are large user stories that are too big to implement. So you break down Epics into stories your team can execute and implement. The smaller stories replace the Epic.
Read Mike Cohn's blog post for an explanation of Stories, Epics and Themes.
Comments