epic,user story,theme之间的不同

转载 2013年12月06日 10:53:18

I've been getting more and more emails lately from people confused about the difference between “user stories”, “epics” and “themes.” So I thought this month we'd return and cover some basic–but very helpful–territory by explaining those terms. First, the terms don't matter that much. These are not terms with important specific meanings like “pointer” to a programmer or “collateralized debt obligation” to whomever it is that's important. Story, epic and theme are merely terms we use to help simplify some discussions Scrum teams have. The terms do have standard meanings that date back to some of the earliest Extreme Programming (XP) teams. And it's nice to use terms in industry-standard ways. But, if these terms didn't exist, you'd make up your own.

So let's see what each means.

A user story is simply something a user wants. User stories are more than just text written on an index card but for our purposes here, just think of user story as a bit of text saying something like, “Paginate the monthly sales report” or, “Change tax calculations on invoices.” Many teams have learned the benefits of writing user stories in the form of: “As a <type of user> I <want/can/am able to/need to/etc.> so that <some reason>.” But it is not necessary that a user story be written that way. Check out theadvantages of that user story format.

A Scrum epic is a large user story. There's no magic threshold at which we call a particular story an epic. It just means “big user story.” I like to think of this in relation to movies. If I tell you a particular movie was an “action-adventure movie” that tells you something about the movie. There's probably some car chases, probably some shooting, and so on. It tells you this even though there is no universal definition that we've agreed to follow, and that an action-adventure movie must contain at least three car chases, at least 45 bullets must be shot, and ….

So, “epic” is just a label we apply to a large story. Calling a story an epic can sometimes convey additional meaning. Suppose you ask me if I had time yesterday to write the user stories about the monthly reporting part of the system. “Yes,” I reply, “but they are mostly epics.” That tells you that while I did write them, I didn't get the chance to break most of them down into stories that are probably small enough to implement directly.

Finally, “theme” is a collection of user stories. We could put a rubber band around that group of stories I wrote about monthly reporting and we'd call that a “theme.” Sometimes it's helpful to think about a group of stories so we have a term for that. Sticking with the movie analogy above, in my DVD rack I have filed the James Bond movies together. They are a theme or grouping.

Hopefully you've found this short explanation helpful. I look forward to your thoughts.

The Hierarchy of Agile Requirement Formats - Themes, Epics, User Stories, Tasks

简单的说,user story的概念比较小,是站在用户角度所体现的描述,而epic是比较大的user story,两者之间并没有非常明显的界限,可以理解为large user story。

theme,是user story的集合,也就是说中间包含user story也包含epic,或者可以直接简单点理解为epic的集合


作者:陈勇       出处:blog.csdn.net/cheny_com       用户故事的颗粒度一直是一个谈论已久的话题,但参加了很多研讨会,搜索了很多网络资源后发现一直没有定论,只好在这里...


敏捷开发知识体系整体框架敏捷开发工程实践项目管理 迭代开发 风险价值生命周期 多级项目规划 完整团队 每日站立会议 任务板 燃尽图 需求管理 需求订单 业务流程草图 用例驱动开发 用户故事 架构 演进...

敏捷开发中,Product Backlog 是否足以实现需求管理?

敏捷方法指导团队将产品需求置于Product Backlog中管理,并按照优先级对每个产品需求进行必要的排列。在计划会(Planning Meeting)之前,由Product Owner从Produ...


前言 上一篇文章谈的是知识管理工具 —— Confluence,它来自澳大利亚 Atlassian 公司。很凑巧的是,今天要介绍的 JIRA 也是来自 Atlassian 公司的。但他不再是知识管...

JIRA 一些学习资料

安装使用什么的就不用说了,用过RTC,clearcase的人对这些基本概念都应该熟悉了,个人觉得JIRA和IBM Rational team concern 的项目管理和追踪这一块非常类似。所以这方面...


在敏捷开发过程中是通过用户故事来将需求具体化成可以进行迭代开发的一个个现实的可见的开发任务。因此在敏捷软件的开发过程中,用户故事的划分对于迭代和开发起着举足轻重的作用。 用户故事从其名字来看是站在用...
  • rxr1st
  • rxr1st
  • 2012年05月02日 21:53
  • 13623


1) 在  Scrum  方法中,Scrum  会议非常重要,整个会议可能会比较混乱粗略,但推进进度的目标却非常清晰明确,并促使团队齐心协力朝共同目标迈进。  2) 团队应召开每日  Scrum ...


前言 上一篇文章谈的是知识管理工具 —— Confluence,它来自澳大利亚 Atlassian 公司。很凑巧的是,今天要介绍的 JIRA 也是来自 Atlassian 公司的。但他不再是知识管...


最近再做一个功能,需求是: 当用户账号在异地登录,不管用户在哪个页面,都要去打开登录界面,要求登录成功或者返回不登录,都要回到MainActivity,其余的页面全部再后台关闭. 实现步骤...
您举报文章:epic,user story,theme之间的不同