一个优良用户故事的6个特性 - INVEST 模式

一个优良用户故事的6个特性 - INVEST 模式（翻译）

Six Features of a Good User Story - INVEST Model
一个优良用户故事的6个特性 - INVEST 模式（翻译）
Tue, 2007-10-16 08:00 — Vaibhav

What is a User Story?
用户故事是什么？
A user story describes desired functionality from the customer(user) perspective. A good user story describes the desired functionality, who wants it, and how and why the functionality will be used. The basic components of a User Story are sometimes dubbed as the three C's:
用户故事其实描述的是客户角度渴望的功能，一个好的用户故事描述了迫切的功能，谁想要它，这个功能如何被使用，这个功能为何被使用。用个用户故事的基本成分通常使用3个C开头的字母来描述：
Card - the written description of the story, serves as and identification, reminder, and also helps in planning.
卡片 - 包括故事的描述，为谁服务，唯一标识，提示信息，对迭代计划编制有所帮助
Conversation - this is the meat of the story; the dialogue that is carried out with the users; recorded notes; mockups; documents exchanged.
讨论 - 这是股市的具体内容,和用户一起进行面对面的沟通，记录笔记，模型，文档交流
Confirmation - the acceptance test criteria that the user will utilize to confirm that the story is completed.
确认 - 确立验收测试的标准，这个标准是让用户来如何来确认这个故事已近完成的
A user story is not technical.
用户故事不是一个技术术语

A well-written user story follows the INVEST model
一个良好的用户股市应该遵循INVEST模式

Independent, Negotiable, Valuable, Estimable, Small, Testable. Let's see what each one means:
独立的，便于沟通的，有价值的，可估计的，短小，可测试的。让我们来看看每一个的意思
Independent - One user story should be independent of another (as much as possible). Dependencies between stories make planning, prioritization, and estimation much more difficult. Often enough, dependencies can be reduced by either combining stories into one or by splitting the stories differently.
独立的 - 一个用户故事对于另一个用户故事应该是独立的（尽可能的）。故事之间的依赖性使得增加了计划编制，确立有限级，故事估计这些工作非常困难。通常，可以通过组合用户故事或者分割用户故事来减少依赖性。
Negotiable - A user story is negotiable. The "Card" of the story is just a short description of the story which do not include details. The details are worked out during the "Conversation" phase. A "Card" with too much detail on it actually limits conversation with the customer.
便于沟通的 - 一个用户故事是便于沟通的。一个故事的卡片是包含故事详情的简短描述。这些详情是通过讨论阶段来完成的。一张还有很多详情的卡片实际上减少了和客户的会谈。
Valuable - Each story has to be of value to the customer (either the user or the purchaser). One very good way of making stories valuable is to get the customer to write them. Once a customer realizes that a user story is not a contract and is negotiable, they will be much more comfortable writing stories.
有价值的 - 每个故事必须对客户具有价值（无论是用户还是购买方）。一个让用户故事有价值的好方法是让客户来写下它们。一旦一个客户意识到一个用户故事并不是一个契约而且可以进行协商的时候，他们将非常乐意写下故事。
Estimable - The developers need to be able to estimate (at a ballpark even) a user story to allow prioritization and planning of the story. Problems that can keep developers from estimating a story are: lack of domain knowledge (in which case there is a need for more Negotiation/Conversation); or if the story is too big (in which case the story needs to be broken down into smaller stories).
可估计得 - 开发者需要去估计一个用户故事以便确定有限级并对故事进行规划。但是让开发者难以估计股市的问题来自：对于领域知识的缺乏（这种情况下需要更多的沟通），或者故事太大了（这时需要把故事切分成小些的）。
Small - A good story should be small in effort, typically representing no more than 2-3 person weeks of effort. A story which is more than that in effort can have more errors associated with scoping and estimation.
短小 - 一个好的故事应该在工作量上短小，描述具有代表性，而且不超过2-3人周的工作量。超过这个范围的用户故事，讲会在划分范围和估计时出现很多错误。
Testable - A story needs to be testable for the "Confirmation" to take place. Remember, we do not develop what we cannot test. If you can't test it then you will never know when you are done. An example of non-testable story: "software should be easy to use".
可测试的 - 一个用户故事是可测试的来用于确认完成，记住，我们不开发不能测试的故事。如果你不能测试那么你永远不知道你什么时候是完成了。一个不可测试的用户故事例子：软件应该是易于使用的。
Summary
总结
Well-written User Stories are cornerstones for Agile Development. They should be independent of each other; the details should be negotiated between the users and the developers; the stories should be of value to the users; they should be clear enough for developers to be able to estimate them; they should be small; and they should be testable through the use of pre-defined test cases.
一个编写良好的用户故事是敏捷开发的基础。它们应该相互独立，详情应该便于开发者和用户进行沟通，应该对用户有价值，应该对于开发者来说尽可能的清晰以便进行估计，应该短小，通过预定义的测试用例是可以对其进行测试的。

原文http://agilesoftwaredevelopment.com/blog/vaibhav/good-user-story-invest