You need user stories for that?
你需要使用者关于这个问题的说明？
Write requirements as user stories.
像用户场景一样记录需求。
User stories can have a hierarchy as well.
用户描述也可以使用一个分层架构。
Do you want to know more about user stories?
您是否想对用户案例了解更多？
This is why I advocate employing user stories.
这就是为什么我要提倡使用用户场景。
We define requirements in terms of user stories.
我们根据用户经历确定需求。
User stories are typically written on 4x6 cards.
用户需求典型地是写在4x6的卡片上。
System requirements are captured as user stories.
系统需求作为用户案例捕获。
throughput we committed to 7 user stories done a month
产量，我们承诺每月完成7个用户故事
Journeys are groups of user stories interacting with each other.
所谓Journey就是彼此交互的用户故事的分组。
Should user stories be our only tool for requirements management?
用户故事是我们做需求管理时唯一可以使用的工具吗？
One red flag to monitor is user stories without acceptance criteria.
一个要监测的红色警示是用户故事没有验收标准。
It's comparatively easy to write, decompose, and refine user stories.
编写、分解以及精炼这种用户故事是相当容易的。
The development team also incorporated user stories into their planning.
开发团队还在计划中采用了用户。
What adjustments to our expectations need to be made around user stories?
在用户故事层面，我们期望有哪些调整？
We approached the implementation of the User Stories with a blank page.
我们用从零开始实现用户情景。
The team pulls the stories, so we only generate a minimal set of user stories.
由于团队会不断提取故事，所以我们只需要生成最基本的一组用户故事。
Extreme Programming requires user stories that fill the role of use cases.
极限编程需要充当用例角色的用户案例。
Review the User stories (customer requirements) for the Go-ForIt application.
重温Go-ForIt应用的用户情景（客户要求）。
We will not be publishing many clueless user stories about them in the future.
将来我们不再能出版很多《无知用户的故事》了。
You should try taking the building blocks approach when building user stories.
在构建用户描述时，您需要尝试采用构建块方法。
And at some point, we should prioritize the user stories for the iterations as well.
有时候我们也应当为了迭代的需要对用户的要求进行优先权的排序。
If so, create appropriate user stories and discuss them with your product owner.
如果是的话，创建合适的用户描述并与产品所有者进行讨论。
User stories are small descriptions written on index CARDS, as shown in Figure 2.
用户情景是写在索引卡上的简短描述，如图2所示。
Identify the user stories for these items and discuss them with your product owner.
为这些内容确定用户描述并与产品所有者进行讨论。
You can iterate over these, break them down, and generate new user stories and epics.
可以查看这些内容，分解它们，并生成新的用户描述和综述。
Like writing use cases, writing user stories is a skill that must be learned and practiced.
像编写用例，编写用户经历都是一种需要学习和实践的能力。
There may be user stories that the team cannot estimate because there are too many unknowns.
由于存在太多未知的因素，团队可能无法对某些用户描述作出评估。
User stories focus on what the customer needs; they do not spell out implementation details.
用户描述关注的是用户的需求；并没有涉及到实现细节。
These can be user stories as used by Extreme Programming or simply one-liner feature descriptions.
列表中的内容可以是类似在极限编程中使用的用户故事，或者就是一行行简单的功能说明。
应用推荐