Scrum: 什么是产品Backlog中的DEEP?

Product Backlog projects have described attributes (D appropriate details), Story points (E stimated), order (P rioritized), and they are constantly added, deleted and updated (E merged) in the backlog to reflect the backlog of teams in a timely and appropriate manner. (产品Backlog项目具有描述的属性(D适当的详细说明),Story points(E stimated),order(P rioritized),并且它们在积压中不断被添加,删除和更新(E合并)以反映到对以及时和恰当的方式积压团队的积压。)

Continue reading

如何为用户故事撰写SMART和INVEST目标?

SMART is a set of standards for creating goals such as Sprint goals. While INVEST reminds you of the characteristics of high-quality product backlog (PBI) (or user stories) typically written in user story format. (SMART是一套创建目标(如Sprint目标)的标准。虽然invest会提醒您高质量产品积压工作(PBI)(或用户案例)的特征,通常以用户案例格式编写。)

Continue reading

Sprint Increment (冲刺增量) vs Potential Shippable Product (潜在可发货产品) vs MVP vs MMP

Scrum requires the team to build an incremental function in each sprint, and the increment must be deliverable, because the product owner may decide to release it at the end of the sprint. This article explains and clarify the related key concepts of: sprint increment, potential shippable product MVP and MMP. (Scrum要求团队在每个sprint中构建一个增量的功能,并且增量必须是可以发送的,因为产品负责人可能决定在sprint结束时发布它。 This article explains and clarify the related key concepts of: sprint increment, potential shippable product mvp and mmp。)

Continue reading

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 reading

Scrum中的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

什么是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 reading

Sprint目标 – 如何写?

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 reading

Scrum中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