用户故事和敏捷术语中的功能有什么区别？ [英] What is the difference between a User Story and a Feature in Agile terminology?

问题描述

我想功能可能类似于信用卡授权，而用户故事可能是为Paypal信用卡授权。

I guess a feature could be something like "credit card authorization", while a user story may be "authorize credit card for paypal".

因此，用户故事是功能的子集？

So, is a user story a subset of a feature?

推荐答案

是的，类似于子集。这篇文章很不错：

功能与故事

Yes, something like a subset. This article is a good read:
Features vs Stories

摘录：

我今天意识到，我并没有明确
的功能和故事之间的差异
是一个重要的差异。本质上，
的功能是一组与
相关的故事，并提供了
的功能包，最终用户通常希望
能够一次获得所有功能。
例如，内联表调整大小是
的一个功能（注意：这是
拖动以调整表，行和
列大小的功能–在Word中尝试）。在
的第一阶段中，您可能会对
的表进行内联调整而拥有
的单个故事，但是对于
的估计而言，它太大了。因此，您将其分解为
三个故事，调整列的大小，调整
行的大小，并调整表本身的大小。

I realized today that I hadn't made explicit the difference in my mind between features and stories and it's an important difference. Essentially, a feature is a group of stories that are related and deliver a package of functionality that end users would generally expect to get all at once. For instance, inline table resizing is a feature (note: this is the ability to drag to resize tables, rows and columns – try it in Word). In the first pass, you'd probably have a single story for inline resizing of tables, but it would be too big to estimate. So you break it down into three stories, resize columns, resize rows and resize the table itself.

这篇关于用户故事和敏捷术语中的功能有什么区别？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！