There is no User Story driving this.
这并不是由用户故事驱动的。
用户故事是什么？
What about checkins that aren't related to a user story?
与用户故事无关的检入怎么处理？
Is the test team rigorously testing each user story?
测试团队是否严格测试了每个用户情景？
Student: I thought that WAS a user story for the most part
学生：我认为这是关于最重要的部分的使用者说明
For example, what do the screen mock-ups look like for this user story?
例如，用户事例是如何看屏幕混合的？
How much work must the team still perform to implement each user story?
为实现每个用户情景，团队还必须执行多少工作量？
The user story is to produce different marketing labels based on widget type.
用户故事是根据小装饰品的类型生产不同的市场标签。
A user story can be built out of the customer problem, based on agile principles.
(用户案例能够以客户问题为源，根据敏捷原则而构建)。
The team initially assigns story points for each user story in the release backlog.
团队首先为发行版计划安排中的每个用户描述分配描述点。
Storyboard: Storyboards present a whole user story by frames that are composed of sketches.
记事板：记事板会为由草图组成的框架呈现了整个的用户情况。
In these cases, the team can add a user story to the backlog to do some additional research.
在这种情况下，团队可以在计划安排中新增一个用户描述，进行额外的研究。
The important thing to note here is that the resulting 'User Story Map' is a boundary object.
这里要注意的重点是，产生的“用户故事地图”是一个边界对象（boundary object）。
As its name suggests, a user story tells a story about a customer or user employing the product.
就像它的名字那样，用户故事讲述客户或者用户使用产品的情况。
When we started implementing the second user story, "user changes the user profile," guess what?
当我们开始实现第二个用户经历，“用户改变用户基本资料”时，猜猜情况怎样？
Not all code changes have to be related to a user story, I just did that in all my examples for clarity.
不是所有的代码变更都必须与某个用户故事相关的，在例子中，我只是为了描述的清晰才这样做。
The user story is a small piece of functionality that CAM be described by the customer on an index card.
用户的经历只是功能性需求的一小部分，它被客户写在一张索引卡片上面。
Requirement Status: Helps the team identify gaps in test coverage for each user story or requirement.
要求状态：可帮助团队确定每个用户情景或要求的测试覆盖率的缺口。
A user story is a form of lightweight requirement that Agile projects use instead of long formal use cases.
用户故事是敏捷项目中轻量级需求的表达形式，用来取代传统项目中长长的用例。
In recent years I've heard some folks say that one should only refactor when one is working on a User Story.
最近几年，我听到有一些人说只有在开发用户故事的时候才能重构。
And if you do use stories, you should not feel obligated to describe every single product backlog item as a user story.
如果你在使用用户故事，你不应该觉得自己必须要把每个产品待办事项列表中的待办项都描述成用户故事。
Business Analyst - Responsible for documenting acceptance criteria and documenting the conversations around the user story.
业务分析员——负责把产品验收条件以及有关用户故事的对话写成文档。
In this case, planning poker serves as a cross-check, preventing a gross misunderstanding about the scope of the user story.
在这个例子中，规划扑克起到了交叉检查的作用，防止对于用户故事范围的错误理解。
In the product backlog and release backlogs, the development team estimates and assigns story points to each user story.
在产品计划安排和发行版计划安排中，开发团队将评估每个用户描述并为其分配描述点。
You might want to verify whether tasks to implement the user story are both assigned correctly and linked to the user story.
您可能需要验证用于实现用户情景的任务是否已正确指派并链接到用户情景。
Average contribution per developer is 38 usp (user story points). One of the members makes only 19 usp - twice less than the others.
开发人员平均每人完成38个usp(用户故事点数)。
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.
有了看板，如果来了一个紧急的请求需要实现，或者一个非常重要的用户故事，团队只需把它放在队列的顶端即可。
While every user story clearly highlights the value of the appliance, there is one story that we think is particularly compelling.
尽管每个用户案例都清晰地突出了这个设备的价值，但其中有一个案例我们认为最有代表性。
The good thing about adding a user story to the release backlog for the spike is that it allows the product owner to prioritize it.
向发行版计划安排中为架构研究添加用户描述的优点是允许产品所有者对用户描述指定优先级。
The good thing about adding a user story to the release backlog for the spike is that it allows the product owner to prioritize it.
向发行版计划安排中为架构研究添加用户描述的优点是允许产品所有者对用户描述指定优先级。
应用推荐