冲刺计划会_冲刺预计划

冲刺计划会

The main agenda of Sprint Planning is to make sprint execution more effective.

Sprint规划的主要议程是使Sprint执行更有效。

To provide right preconditions, one need to take following actions during the sprint preplanning:

为了提供正确的前提条件,在冲刺预计划中需要采取以下行动:

  • Clarify the Acceptance Criteria. The criteria, that a story must qualify to be marked as "Done".

    明确接受标准。 故事必须符合被标记为“完成”的条件。

  • Provide the estimate of the user stories, to help Product Owner to identify the priorities in the backlog.

    提供用户故事的估计,以帮助产品负责人确定积压工作中的优先级。

  • Break down high priority User Stories into chunks that will fit for a sprint.

    将高优先级的用户案例分为适合冲刺的部分。

  • Consider dependency on the key resources in the team and workload for each team.

    考虑对团队中关键资源的依赖以及每个团队的工作量。

管理依赖关系 (Managing Dependencies)

A good user story is independent, it does not have any dependency.

好的用户故事是独立的,没有任何依赖性。

There are 3 types of dependencies:

依赖关系分为3种:

  • Simple Dependency

    简单依赖

  • External Dependency

    外部依赖

  • Intertwined Dependency

    相互依存的依赖

简单依赖 (Simple Dependency )

Simple dependencies happen when one user story depends on another one. One way to remove this unidirectional dependency is to combine or split the user stories differently. When this is not possible, the alternative is to set a higher priority for the standalone user stories with the greatest number of dependencies than their dependents.

当一个用户故事依赖于另一个用户故事时,就会发生简单的依赖关系。 消除这种单向依赖性的一种方法是以不同方式组合或拆分用户故事。 如果不可能,则替代方法是为具有最大依赖关系的独立用户故事(比其依赖关系)设置更高的优先级。

外部依赖 (External Dependency )

External dependencies occur when a story is dependent on outside teams. In this case, the teams need to negotiate integration and delivery dates and adjust the priorities of the stories. The team working on the dependent story should not commit to completing the dependent story within a Sprint until the other team delivers their user story.

当故事依赖于外部团队时,就会发生外部依赖。 在这种情况下,团队需要协商集成和交付日期并调整故事的优先级。 在依赖故事上工作的团队不应致力于在Sprint中完成依赖故事,直到另一个团队提供其用户故事。

相互依存的依赖 (Intertwined Dependency )

These dependencies are when two or more user stories are co-dependent, and each cannot complete without the other. Ideally, the team should look for ways to break all the connections or look for ways to turn the intertwined dependencies into simple dependencies instead. Dealing with these dependencies across Scrum Teams is a critical responsibility of the PO(Product Owner) working with the Scrum Teams.

这些依赖关系是两个或两个以上用户故事相互依赖的情况,而每个彼此之间无法完成。 理想情况下,团队应该寻找断开所有连接的方法,或者寻找将相互依存的依赖关系转变为简单依赖关系的方法。 处理Scrum团队中的这些依赖关系是与Scrum团队一起工作的PO(产品负责人)的一项重要职责。

Product Owners and the Scrum development team need to focus their attention on the high priority stories for the current release. That's why Sprint Preplanning is an important step for effective Sprint planning.

产品负责人和Scrum开发团队需要将注意力集中在当前版本的高优先级故事上。 这就是为什么Sprint预先计划是有效进行Sprint计划的重要步骤。

翻译自: https://www.studytonight.com/scrum-framework/sprint-preplanning

冲刺计划会

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值