The most common technology is the role-feature-reason template, which is used by teams and product owners to start writing user stories in three parts: (1) As a (role); (2) I want (feature); So that (reason). (最常见的技术是角色 – 特征 – 理由模板，用于团队和产品所有者开始编写用户故事，分为三个部分：（1）作为 As a（角色）; （2）I What 我想要（特征）; So that（理由）。)
Continue readingAuthor: [email protected]
Scrum中的Burndown图表是什么？
Burndown chart is a graphical representation of the remaining work and time. It is usually used in agile software development methods, such as Scrum. However, burning charts can be applied to any project that contains measurable progress over a period of time. (Burndown chart 是剩余工作与时间的图形表示。它通常用于敏捷软件开发方法，如Scrum。但是，刻录图表可以应用于任何包含一段时间内可衡量进展的项目。)
Continue readingScrum中的Sprint目标是什么？
Sprint goals show the expected results of iterations that provide shared goals for the team, which must be defined before the team starts Sprint in order to focus on achieving this goal. This ensures that everyone is on the same page. After choosing goals, the team must strive to implement them. (Sprint目标显示了为团队提供共享目标的迭代的期望结果，必须在团队启动Sprint之前定义该目标，以便专注于实现此目标。这可确保每个人都在同一页面中。选择目标后，团队必须努力实施目标。)
Continue reading如何使用100点方法确定产品待办事项的优先次序？
Your product backlog items need to be structured, organized and prioritized to identify the most important things for your team. In this article, I will introduce 100-point method for product backlog refining activities. (您的待办事项需要进行结构化，组织和优先排序，以确定您的团队最重要的事情。在本文中，我将介绍100点方法为产品积压细化活动。)
Continue reading如何使用MoSCoW方法确定产品积压的优先次序?
MoSCoW (also known as MoSCoW prioritization or MoSCoW analysis) is a prioritization technology designed to reach a consensus with stakeholders on its importance for the delivery of each requirement. (MoSCoW方法（也称为MoSCoW优先级划分或MoSCoW分析）是一种优先级技术，旨在与利益相关方就其对每项要求的交付的重要性达成共识。)
Continue readingSprint Backlog在Scrum中是什么意义？
Sprint Backlog is a set of product backlog projects selected for the current Sprint and a plan to provide product increments for achieving Sprint goals. (Sprint Backlog是为当前Sprint选择的一组产品Backlog项目，以及为实现Sprint目标而提供产品增量的计划。)
Continue reading什么是Scrum中的产品Backlog？谁负责呢？
Product Backlog is the only source ranking list of all products you need and changes in product requirements. The owner of the product is responsible for content, usability, and prioritizes the backlog product backlog to-do list. (产品Backlog是所有你所需要的产品以及产品需求变化的唯一来源排序列表。该产品拥有者是负责内容，可用性，并要求产品Backlog产品待办事项列表的优先级。)
Continue readingSprint目标 – 如何写？
Sprint goals are a high-level summary of what the product owner wants to achieve during the sprint, usually described in detail through a specific set of product backlog items. (Sprint目标是产品所有者在sprint期间希望实现的目标的高级摘要，通常通过一组特定的产品积压项目进行详细说明。)
Continue readingScrum中Definition of Ready的定义是什么？
The product owner can work with the team to define an artifact called Definition of Ready to ensure that at the top of the backlog projects are ready to move to sprint so that the development team can confidently submit and complete them. The end of the sprint. (产品所有者可以与团队一起定义一个名为“ Definition of Ready的定义”的工件，以确保积压顶部的项目已准备好移动到sprint中，以便开发团队可以在冲刺的结束之前自信地提交并完成它们。)
Continue reading完成 vs. 接受标准的定义
Completion (DoD) is defined as a list of requirements that user stories must comply with in order for the team to complete the PBI. The difference between the two is that DoD is universal to all user stories, and acceptance criteria are applicable to specific user stories. The acceptance criteria for each user story will vary according to the requirements of the user story. (完成（DoD）的定义 是用户故事必须遵守的要求列表，以便团队完成调用。这两者之间的区别在于，DoD对于所有用户故事都是通用的，而接受标准适用于特定的用户故事。每个用户故事的接受标准将根据该用户故事的要求而有所不同。)
Continue reading
English
Arabic
Chinese (Simplified)
Dutch
French
German
Italian
Japanese
Korean
Portuguese
Russian
Spanish