Six Features of a Good User Story - INVEST Model
一個(gè)優(yōu)良用戶故事的6個(gè)特性 - 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:
用戶故事其實(shí)描述的是客戶角度渴望的功能，一個(gè)好的用戶故事描述了迫切的功能，誰(shuí)想要它，這個(gè)功能如何被使用，這個(gè)功能為何被使用。用個(gè)用戶故事的基本成分通常使用3個(gè)C開(kāi)頭的字母來(lái)描述：
Card - the written description of the story, serves as and identification, reminder, and also helps in planning.
卡片 - 包括故事的描述，為誰(shuí)服務(wù)，唯一標(biāo)識(shí)，提示信息，對(duì)迭代計(jì)劃編制有所幫助
Conversation - this is the meat of the story; the dialogue that is carried out with the users; recorded notes; mockups; documents exchanged.
討論 - 這是股市的具體內(nèi)容,和用戶一起進(jìn)行面對(duì)面的溝通，記錄筆記，模型，文檔交流
Confirmation - the acceptance test criteria that the user will utilize to confirm that the story is completed.
確認(rèn) - 確立驗(yàn)收測(cè)試的標(biāo)準(zhǔn)，這個(gè)標(biāo)準(zhǔn)是讓用戶來(lái)如何來(lái)確認(rèn)這個(gè)故事已近完成的
A user story is not technical.
用戶故事不是一個(gè)技術(shù)術(shù)語(yǔ)

A well-written user story follows the INVEST model
一個(gè)良好的用戶股市應(yīng)該遵循INVEST模式

Independent, Negotiable, Valuable, Estimable, Small, Testable. Let's see what each one means:
獨(dú)立的，便于溝通的，有價(jià)值的，可估計(jì)的，短小，可測(cè)試的。讓我們來(lái)看看每一個(gè)的意思
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.
獨(dú)立的 - 一個(gè)用戶故事對(duì)于另一個(gè)用戶故事應(yīng)該是獨(dú)立的（盡可能的）。故事之間的依賴性使得增加了計(jì)劃編制，確立有限級(jí)，故事估計(jì)這些工作非常困難。通常，可以通過(guò)組合用戶故事或者分割用戶故事來(lái)減少依賴性。
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.
便于溝通的 - 一個(gè)用戶故事是便于溝通的。一個(gè)故事的卡片是包含故事詳情的簡(jiǎn)短描述。這些詳情是通過(guò)討論階段來(lái)完成的。一張還有很多詳情的卡片實(shí)際上減少了和客戶的會(huì)談。
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.
有價(jià)值的 - 每個(gè)故事必須對(duì)客戶具有價(jià)值（無(wú)論是用戶還是購(gòu)買(mǎi)方）。一個(gè)讓用戶故事有價(jià)值的好方法是讓客戶來(lái)寫(xiě)下它們。一旦一個(gè)客戶意識(shí)到一個(gè)用戶故事并不是一個(gè)契約而且可以進(jìn)行協(xié)商的時(shí)候，他們將非常樂(lè)意寫(xiě)下故事。
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).
可估計(jì)得 - 開(kāi)發(fā)者需要去估計(jì)一個(gè)用戶故事以便確定有限級(jí)并對(duì)故事進(jìn)行規(guī)劃。但是讓開(kāi)發(fā)者難以估計(jì)股市的問(wèn)題來(lái)自：對(duì)于領(lǐng)域知識(shí)的缺乏（這種情況下需要更多的溝通），或者故事太大了（這時(shí)需要把故事切分成小些的）。
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.
短小 - 一個(gè)好的故事應(yīng)該在工作量上短小，描述具有代表性，而且不超過(guò)2-3人周的工作量。超過(guò)這個(gè)范圍的用戶故事，講會(huì)在劃分范圍和估計(jì)時(shí)出現(xiàn)很多錯(cuò)誤。
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".
可測(cè)試的 - 一個(gè)用戶故事是可測(cè)試的來(lái)用于確認(rèn)完成，記住，我們不開(kāi)發(fā)不能測(cè)試的故事。如果你不能測(cè)試那么你永遠(yuǎn)不知道你什么時(shí)候是完成了。一個(gè)不可測(cè)試的用戶故事例子：軟件應(yīng)該是易于使用的。
Summary
總結(jié)
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.
一個(gè)編寫(xiě)良好的用戶故事是敏捷開(kāi)發(fā)的基礎(chǔ)。它們應(yīng)該相互獨(dú)立，詳情應(yīng)該便于開(kāi)發(fā)者和用戶進(jìn)行溝通，應(yīng)該對(duì)用戶有價(jià)值，應(yīng)該對(duì)于開(kāi)發(fā)者來(lái)說(shuō)盡可能的清晰以便進(jìn)行估計(jì)，應(yīng)該短小，通過(guò)預(yù)定義的測(cè)試用例是可以對(duì)其進(jìn)行測(cè)試的。

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