Sticking with the movie analogy above, in my DVD rack I have filed the James Bond movies together. Sometimes it’s helpful to think about a group of stories, so we have a term for that. We could put a rubber band around that group of stories about monthly reporting and we’d call that a theme. The team that invented user stories used the word theme to mean a collection of user stories. Remember that the Scrum framework doesn't say anything about epics, stories, and themes. “Yes,” I reply, “but they are mostly epics.” That tells you that while I did write them, most are still pretty big chunks of work, too big in fact to be brought directly into a sprint or iteration. Suppose you ask me if I had time yesterday to create user stories about the monthly reporting part of the system. ![]() While epic is just a label we apply to a large story, calling a story an epic can sometimes tell us how refined they are in the backlog. The term I used tells you this even though there is no universal definition that we’ve agreed to follow no one claims an action-adventure movie must contain at least three car chases, at least 45 bullets must be shot, and so on. There’s probably some car chases, probably some shooting, and so on. If I tell you a particular movie was an “action-adventure movie” that tells you something about the movie. I like to think of this in relation to movies. For our purposes in agile and Scrum, epic just means big user story. There’s no magic threshold at which we call a particular story an epic. Even within the format, though, we’re free to customize user stories.Īs defined by the XP teams that invented user stories, an epic is a large user story. ” Check out the advantages of that user story format. Many teams have learned the benefits of writing user stories in the form of: “As a I so that. During sprint or iteration planning, user stories are moved from the product backlog to the sprint backlog. User stories are the most common form of product backlog item for agile teams. For our purposes here, we can think of a user story as a bit of text saying something like, “Paginate the monthly sales report” or, “Change tax calculations on invoices.” There is more to user stories than just text written on an index card or typed into a tool, but let’s keep it simple here. When it comes to understanding the difference between epics and user stories it helps to understand what each is.Ī user story is simply something a user wants. I’ll start with industry-standard definitions, and I’ll comment on the changes as well. Some of these terms date back to the days of Extreme Programming (XP) teams, but the terms are used in newer ways now. ![]() ![]() Stories, themes, epics, and features are merely terms agile teams use to help simplify some discussions. So in this article, let’s cover some basic-but very helpful-territory by explaining some user story–related language. "Epics? User Stories? What's the Difference?" I’ve been getting more and more emails lately from people asking, “What is an epic, a feature and a user story in agile?” “Can you give me some epic, feature, and user story examples?” “Can you tell me how to write epics, features and user stories?”. We hate spam and promise to keep your email address safe. Enter your email address below to get over 200 user stories from three complete product backlogs created by Mike Cohn.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |