与用户故事无关的检入怎么处理？
编写、分解以及精炼这种用户故事是相当容易的。
It's comparatively easy to write, decompose, and refine user stories.
用户故事是根据小装饰品的类型生产不同的市场标签。
The user story is to produce different marketing labels based on widget type.
所谓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.
在这个例子中，规划扑克起到了交叉检查的作用，防止对于用户故事范围的错误理解。
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.
对于每一次迭代，通过分解用户故事识别出任务，并且将其张贴在面板的ToDo区域中。
For each iteration, tasks are newly identified by breaking down user stories into tasks and it is these tasks that are posted onto the ToDo area.
在每个活动下方放着相关的用户故事，这里故事是从上到下按照优先级高低排列的。
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.
这里要注意的重点是，产生的“用户故事地图”是一个边界对象（boundary object）。
The important thing to note here is that the resulting 'User Story Map' is a boundary object.
产品backlog是一维的东西，在产品backlog中，用户故事按照优先级从高到低上下排列。
The product backlog is essentially one-dimensional. User stories are organized from highest to lowest priority.
Pascal建议，好的做法是首先回答这个问题：“我们如何才能找到传递了业务价值的用户故事？”
Pascal proposes that a better starting point is with the question: "How do we find the User Stories that deliver the Business Values?" He goes on to suggest this approach
用于优先排序的传统敏捷方法是这样的，业务价值高的用户故事应该在业务价值低的故事之前实现。
The traditional agile approach to prioritization is that user stories of higher business value should be implemented before ones of lower business value.
第二点包括能够实行相关的实践，例如准确填写和修改产品的backlog，或以用户故事的形式描述需求。
The latter includes being able to implement relevant practices such as filling and refining the product backlog effectively, or describing requirements in the form of user stories.
更明确地说，团队什么时候才可以把一个用户故事移入到任务版上的“完成”一栏之中？ 这又到底意味着什么？
More specifically, when your team moves one particular user story into the "done" column on their taskboard, what does that actually mean?
一个具体的迭代可能有3或4个用户故事点要开发，而在开发这些故事点时，关键要谨记整体总是大于局部之和。
A specific iteration may have 3 or 4 user stories to be developed, but while developing these stories, it is critical to keep in mind that the whole is always greater than the sum of the parts.
用同样的方法，我们努力减少那些没有添加到可工作的特性集和愿景上的用户故事、场景、示例和代码。
In the same way, we try to minimise the backlog of stories, scenarios, examples and code which haven't yet been added to a working feature and thence to the vision.
有了看板，如果来了一个紧急的请求需要实现，或者一个非常重要的用户故事，团队只需把它放在队列的顶端即可。
In Kanban, if there is an urgent request to implement or a really important user story, the team can just put it on top of the queue.
当团队需要用户故事的时候，我们会采用价值最高的过程，然后针对团队的需要以正确的粒度将其分解为用户故事。
When the team needs user stories, we take the highest value processes and break them down into user stories at the right level of granularity for the team's needs.
应用推荐