Write requirements as user stories.
像用户场景一样记录需求。
Do you want to know more about user stories?
您是否想对用户案例了解更多?
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.
编写、分解以及精炼这种用户故事是相当容易的。
What adjustments to our expectations need to be made around user stories?
在用户故事层面,我们期望有哪些调整?
Extreme Programming requires user stories that fill the role of use cases.
极限编程需要充当用例角色的用户案例。
The team pulls the stories, so we only generate a minimal set of user stories.
由于团队会不断提取故事,所以我们只需要生成最基本的一组用户故事。
You should try taking the building blocks approach when building user stories.
在构建用户描述时,您需要尝试采用构建块方法。
If so, create appropriate user stories and discuss them with your product owner.
如果是的话,创建合适的用户描述并与产品所有者进行讨论。
Tips on creating user stories and understanding the role of the product owner.
有关创建用户描述(user story)以及理解产品所有者角色的建议。
Identify the user stories for these items and discuss them with your product owner.
为这些内容确定用户描述并与产品所有者进行讨论。
And at some point, we should prioritize the user stories for the iterations as well.
有时候我们也应当为了迭代的需要对用户的要求进行优先权的排序。
There may be user stories that the team cannot estimate because there are too many unknowns.
由于存在太多未知的因素,团队可能无法对某些用户描述作出评估。
This knowledge may generate new user stories or demonstrate that some stories are less critical.
这些知识可能会生成新的用户描述,或者证实某些描述并不是特别重要。
These can be user stories as used by Extreme Programming or simply one-liner feature descriptions.
列表中的内容可以是类似在极限编程中使用的用户故事,或者就是一行行简单的功能说明。
While creating the release backlog, break down any high-level user stories into smaller user stories.
在创建发行版计划安排时,将任何高级用户描述分解为多个更小的用户描述。
These artifacts can include a requirements document, a draft user interface, user stories, and so forth.
这些工件可以包含一个需求文件、一个草拟的用户界面、用户事例等等。
Scrum does not mandate how product backlog items are described, but I prefer to work with user stories (Cohn 2004).
Scrum不强制规定应该怎么样去描述产品待办事项列表,但我更喜欢使用用户故事来描述(Cohn 2004)。
In the first stages of service development, consumer-driven contracts look very much like user stories for services.
在服务开发的第一阶段,消费者驱动的契约很像有关服务的用户故事(user stories for services)。
For example, you'll be able to make user stories in ScrumWorks or Rally depend on defects created in ClearQuest or Bugzilla.
比方说,你可以确保ScrumWorks或是Rally中的用户故事依赖于ClearQuest或Bugzilla创建的缺陷。
The product owner talks with customers to understand their requirements and creates an initial set of high-level user stories.
产品所有者需要与客户沟通以理解他们的需求,然后创建一组初始的高级用户描述。
I particularly liked the way they intend to allow you to visually sort user stories into columns based on their Fibonacci size.
我特别喜欢下面这一点,那就是他们想要让你可以用可视化的方式基于用户故事的Fibonacci大小来排序。
Initially, we had four releases, each between six and ten weeks in length, and each typically containing between 15 and 30 user stories.
最初,我们有4个版本,每个发布时间都在6到10周之间,并且每个一般包含15到30个用户情景。
They also showed me a great prototype for how they plan to allow you to sort user stories into priority order, again in a very visual way.
他们还向我展示了一个很棒的原型,他们计划通过这个原型让你可以按照优先级的顺序来排列用户故事,并且也是用可视化的方式。
Let's say they are going to start a sprint now, with two user stories per team (usually there will be more stories than that in a sprint).
假设他们现在要开始一个sprint,每个团队有两个用户故事要开发(通常一个sprint中会有更多的故事)。
We need to explain to those in customer and product owner role that it's important to write user stories that they don't intend to release.
我们应该对客户和产品所有人(productowner)解释说,将那些他们不打算发布的需求写到用户故事(user story)中也是重要的。
应用推荐