• System requirements are captured as user stories.

    系统需求作为用户案例捕获。

    youdao

  • Journeys are groups of user stories interacting with each other.

    所谓Journey就是彼此交互的用户故事的分组。

    youdao

  • It's comparatively easy to write, decompose, and refine user stories.

    编写、分解以及精炼这种用户故事是相当容易的。

    youdao

  • Extreme Programming requires user stories that fill the role of use cases.

    极限编程需要充当用例角色的用户案例。

    youdao

  • The team pulls the stories, so we only generate a minimal set of user stories.

    由于团队会不断提取故事,所以我们只需要生成最基本的一组用户故事。

    youdao

  • And at some point, we should prioritize the user stories for the iterations as well.

    有时候我们也应当为了迭代的需要对用户的要求进行优先权的排序。

    youdao

  • There may be user stories that the team cannot estimate because there are too many unknowns.

    由于存在太多未知的因素,团队可能无法对某些用户描述作出评估。

    youdao

  • This knowledge may generate new user stories or demonstrate that some stories are less critical.

    这些知识可能会生成新的用户描述,或者证实某些描述并不是特别重要。

    youdao

  • These can be user stories as used by Extreme Programming or simply one-liner feature descriptions.

    列表中的内容可以是类似在极限编程中使用的用户故事,或者就是一行行简单的功能说明。

    youdao

  • While creating the release backlog, break down any high-level user stories into smaller user stories.

    在创建发行版计划安排时,将任何高级用户描述分解为多个更小的用户描述。

    youdao

  • These artifacts can include a requirements document, a draft user interface, user stories, and so forth.

    这些工件可以包含一个需求文件、一个草拟的用户界面、用户事例等等。

    youdao

  • Scrum does not mandate how product backlog items are described, but I prefer to work with user stories (Cohn 2004).

    Scrum不强制规定应该怎么样去描述产品待办事项列表,但我更喜欢使用用户故事来描述(Cohn 2004)。

    youdao

  • In the first stages of service development, consumer-driven contracts look very much like user stories for services.

    在服务开发的第一阶段,消费者驱动的契约很像有关服务的用户故事(user stories for services)。

    youdao

  • 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创建的缺陷。

    youdao

  • The product owner talks with customers to understand their requirements and creates an initial set of high-level user stories.

    产品所有者需要与客户沟通以理解他们的需求,然后创建一组初始的高级用户描述。

    youdao

  • I particularly liked the way they intend to allow you to visually sort user stories into columns based on their Fibonacci size.

    我特别喜欢下面这一点,那就是他们想要让你可以用可视化的方式基于用户故事的Fibonacci大小来排序。

    youdao

  • 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个用户情景。

    youdao

  • 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.

    他们还向我展示了一个很棒的原型,他们计划通过这个原型让你可以按照优先级的顺序来排列用户故事,并且也是用可视化的方式。

    youdao

  • 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中会有更多的故事)。

    youdao

  • 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)中也是重要的。

    youdao

  • Work with them closely to understand the domain, the aspects that tend to vary often, and how these variations are manifested in user stories.

    贴近这些专家和用户,与他们一起工作,你才能更好的了解领域知识、各方面的趋势变化,以及这些变化是如何体现在用户故事中的。

    youdao

  • 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.

    对于每一次迭代,通过分解用户故事识别出任务,并且将其张贴在面板的ToDo区域中。

    youdao

  • If new user stories emerge, such as needing to know the airport's time zone or the elevation in meters, GeoNames offers a compelling alternative.

    如果出现新的用户需求,例如需要知道机场的时区或海拔高度,GeoNames还可以提供另一种令人感兴趣的结果。

    youdao

  • They learn to measure the work they do by the number of user stories completed, and they use this number to predict their work for the next iteration.

    他们学会通过所完成的用户描述的数量来衡量他们的工作成果,并且根据这一数据来预知下一迭代开发阶段所能完成的工作。

    youdao

  • The traditional agile approach to prioritization is that user stories of higher business value should be implemented before ones of lower business value.

    用于优先排序的传统敏捷方法是这样的,业务价值高的用户故事应该在业务价值低的故事之前实现。

    youdao

  • Application requirements are expressed as test cases that reflect high-level requirements and business rules that are possibly extracted from user stories.

    应用程序需求表示为测试用例,反映抽象需求和业务规则(可能是从用户案例中提取的)。

    youdao

  • Fortunately most domain variations are expressed as user stories and you can look for patterns across iterations and releases to get a better understanding.

    幸运的是大部分的领域变化能以用户故事的形式来表述,而且你能从持续的迭代和发布中找到相关模式,更好的了解这些变化。

    youdao

  • The team then engaged the solution leaders in validating the user stories, collaborated to refine them and gain a greater understanding of the requirements.

    然后该团队让解决方案领导者参与验证用户案例,合作改进案例并更好地理解需求。

    youdao

  • 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.

    当团队需要用户故事的时候,我们会采用价值最高的过程,然后针对团队的需要以正确的粒度将其分解为用户故事。

    youdao

  • XP is a quick and effective method of capturing requirements and organizing them into logical iterative builds, assigning priorities, and developing the user stories.

    XP是一种快速高效的方法,用于捕获需求,并将其组织为逻辑迭代版本,分配优先顺序和开发用户案例。

    youdao

$firstVoiceSent
- 来自原声例句
小调查
请问您想要如何调整此模块?

感谢您的反馈,我们会尽快进行适当修改!
进来说说原因吧 确定
小调查
请问您想要如何调整此模块?

感谢您的反馈,我们会尽快进行适当修改!
进来说说原因吧 确定