与用户故事无关的检入怎么处理？
这并不是由用户故事驱动的。
产量，我们承诺每月完成7个用户故事
在用户故事层面，我们期望有哪些调整？
What adjustments to our expectations need to be made around user stories?
你还需要写得很好的用户故事。
它可以被分解为多个用户故事。
一个要监测的红色警示是用户故事没有验收标准。
One red flag to monitor is user stories without acceptance criteria.
编写、分解以及精炼这种用户故事是相当容易的。
It's comparatively easy to write, decompose, and refine user stories.
用户故事促使QA创建场景。
在Pascal的你如何评估用户故事的业务价值？
In Pascal's article How do you estimate the Business Value of User Stories?
用户故事是根据小装饰品的类型生产不同的市场标签。
The user story is to produce different marketing labels based on widget type.
用户故事是我们做需求管理时唯一可以使用的工具吗？
Should user stories be our only tool for requirements management?
这种技术适用于较小的或者简单的用户故事。
所谓Journey就是彼此交互的用户故事的分组。
Journeys are groups of user stories interacting with each other.
开发人员平均每人完成38个usp(用户故事点数)。
Average contribution per developer is 38 usp (user story points). One of the members makes only 19 usp - twice less than the others.
特性集促使BA(业务分析师)创建用户故事。
就像它的名字那样，用户故事讲述客户或者用户使用产品的情况。
As its name suggests, a user story tells a story about a customer or user employing the product.
有时，你们有一组用户故事等待开发，并会设法尽快交付给客户。
You develop incrementally and release as often as possible. Sometimes you have a set of user stories you are working on and you are trying to release those to customers quickly.
最近几年，我听到有一些人说只有在开发用户故事的时候才能重构。
In recent years I've heard some folks say that one should only refactor when one is working on a User Story.
业务分析员——负责把产品验收条件以及有关用户故事的对话写成文档。
Business Analyst - Responsible for documenting acceptance criteria and documenting the conversations around the user story.
由于团队会不断提取故事，所以我们只需要生成最基本的一组用户故事。
The team pulls the stories, so we only generate a minimal set of user stories.
总体来说，很多团队都会过高评价同时实现多个用户故事的效果。
On the whole, many teams seem to over-rate the benefits of implementing many stories concurrently.
用户故事是敏捷项目中轻量级需求的表达形式，用来取代传统项目中长长的用例。
A user story is a form of lightweight requirement that Agile projects use instead of long formal use cases.
跟之前的方法一样，这种技术通常非常适用于小的或者简单的用户故事。
Like the previous method, this technique often works best with small or simple stories.
在这个例子中，规划扑克起到了交叉检查的作用，防止对于用户故事范围的错误理解。
In this case, planning poker serves as a cross-check, preventing a gross misunderstanding about the scope of the user story.
列表中的内容可以是类似在极限编程中使用的用户故事，或者就是一行行简单的功能说明。
These can be user stories as used by Extreme Programming or simply one-liner feature descriptions.
在每个活动下方放着相关的用户故事，这里故事是从上到下按照优先级高低排列的。
Below each of these activities, arrange the associated user stories, putting the most important ones higher up than the less important ones.
在处理一个新的用户故事时，你发现针对前一个故事所编写的测试已经不再体现需求。
When proceeding to a new story, you discover that a test you wrote for a previous story no longer reflects the requirements.
不是所有的代码变更都必须与某个用户故事相关的，在例子中，我只是为了描述的清晰才这样做。
Not all code changes have to be related to a user story, I just did that in all my examples for clarity.
其余的story可以晚一些再添加进来，我们可以从这些用户故事中分别得到反馈。
The other stories can each be added later, and we can get feedback separately on those.
应用推荐