Close

Sprint Retrospectives

冲刺回顾让您有机会回顾最近的冲刺,并为今后的冲刺做出改进。这些会议至关重要,因为定期评估和改进流程可以提高结果的质量和减少障碍。

在本指南中,我们将讨论什么是冲刺回顾、其重要性以及如何执行成功的冲刺审查以提高团队的效率。

人们在桌子旁一起工作
列表图标
准备时间

15 分钟

跑表图标
持续时间

60 分钟

组图标
人数

4 - 8

5 秒摘要

  • Celebrate what went well during the last sprint.
  • Discuss what didn’t go as well or could have been better.
  • Determine how to make improvements in the next sprint.
您将需要
  • 会议场地或支持屏幕共享的视频会议。
  • 数字协作工具(参见模板)。
  • 可选:实物白板、记号笔、便利贴和计时器。
演练资源
Confluence 模板
4L 回顾

How to run a sprint retrospective

Reflect on past sprints to make improvements for the future.

什么是冲刺回顾?

冲刺回顾是在冲刺之后进行的审查,它在敏捷方法中起着关键作用。冲刺回顾旨在确定哪些方面进展顺利,哪些方面存在问题,并找出可以改进的方面。

定期审查是团队合作的重要组成部分。通过了解哪些有效,哪些无效,您可以改进敏捷流程,简化下一次冲刺。

谁应该参加冲刺回顾会议?

冲刺回顾会议应包括产品负责人、Scrum 团队、Scrum 大师和利益相关者。在冲刺回顾会议上,最好能有各种不同的观点。大家可以一起分析最近的冲刺,并确定在开始项目的下一部分之前需要做出哪些改变。

How often should you do sprint retrospectives?

Retrospectives work best when done at the end of each sprint. However, if your sprints are short (like one week), it may make more sense to do a retrospective after every other sprint.

How long should sprint retrospectives be?

The duration of your sprint retrospective meeting can vary depending on the duration of the sprint. They can be as short as 45 minutes or as long as 3 hours. Give your team enough time and space for a meaningful conversation. Taking a bit of extra time upfront helps save time and improve results in the long run.

What are the main benefits of sprint retrospectives?

Sprint retrospectives help your team learn from the past and improve in the future, leading to streamlined Scrum sprints and a better end result.

Research shows the main benefits of retrospectives are that they help teams:

  1. Achieve continuous improvement

    Building an action plan and following up on it in future meetings is critical for growth.
  2. Improve team reflexivity

    Reflexivity is "the extent to which team members collectively reflect upon the team's objectives, strategies, and processes and adapt them to current or anticipated circumstances.”

    Teams with higher levels of reflexivity are more likely to be better at innovating, identifying problems and opportunities, adapting to change, and implementing new ideas effectively.

Higher reflexivity correlates with:

  • 更好的决策
  • Better problem-solving
  • More effective strategy implementation
  • More team learning
  • More innovation
  • More adaptability to change

Other research reinforces that reflexivity helps teams:

  • Process information more thoroughly
  • Reduce errors and failures
  • Be more agile and flexible when things change

冲刺回顾会议想法

冲刺回顾起初可能会让人不知所措,但其实它是一个非常简单的概念。您可以使用冲刺回顾模板,也可以按照本指南列出的五个步骤进行操作。只要您能收集到反馈,并利用这些反馈得出洞察信息和实施改变,您就做对了。

每个冲刺回顾都始于一次成功的冲刺。Jira 提供了几个关键功能,可以帮助您组织成功的冲刺,包括:

  • 待办事项列表:待办事项列表允许您列出与项目或计划相关的所有工作。您可以将这些工作分解为单个冲刺(通常为 2 周)。
  • 面板:Jira 面板允许您将大型项目分解成更易于管理的部分,这样您就可以规划冲刺阶段,确保交付成果更快地交付。
  • 时间线:时间线可让团队与利益相关者保持同步,通过映射的工作项目、依赖关系和发布,提供项目时间线概览。

Jira 可让敏捷团队轻松实现对冲刺的可视化、跟踪和管理。使用 Jira,您可以简化下一次冲刺,确保及时交付成果。试用 Jira Scrum 板,了解 Jira 如何帮助您优化敏捷团队。

Sprint retrospective FAQs

冲刺回顾有哪些常见挑战?
  

缺乏反馈是冲刺回顾最大的潜在挑战之一。如果人们不透明或难以提供详细的反馈,就很难确定哪些做得好,哪些做得不好。您可以为冲刺回顾提供一个简单的结构,如“悲伤、生气、高兴”(SMG) 方法和 4 Ls 方法,从而鼓励人们提供更好的意见。您还可以尝试收集匿名意见。

您还应避免只关注一次性的错误或成功。冲刺回顾是为了改进下一次冲刺,因此不要关注不会影响项目其余部分的反馈。

How long should a sprint retrospective be?
  

冲刺回顾会议的时间长短取决于冲刺的持续时间。冲刺回顾可以短至 45 分钟,也可以长达 3 小时,这完全取决于冲刺。虽然您希望做任何事都能高效,但重要的是要给团队足够的时间进行有意义的讨论,并在冲刺回顾中取得进展。

在冲刺回顾中应该问哪些问题?
  

在冲刺回顾中激发讨论有几种方法。您可以使用 4 Ls 方法,询问大家在冲刺阶段喜欢什么、讨厌什么、学到了什么和渴望什么。也可以使用“悲伤、生气、高兴”方法深入探讨最近的冲刺。在冲刺回顾中,您可能想问的一些问题包括:

  • 哪些地方做得不错?
  • 出了什么问题?
  • 收获了哪些经验教训?
  • 我们可以做出哪些改变?

1. Set the tone

预估时间: 5 分钟

Retrospectives are part of the sprint planning process. The goal is to collect a variety of feedback and perspectives to improve processes and results. Use one of our pre-made templates to help facilitate the process.

At the beginning of the meeting, encourage people to respectfully share their open and honest thoughts throughout the session, focusing on improvement instead of blame. (This is key to developing psychological safety and a blameless culture.)

提示:创建安全的空间

Make it clear what will happen with the information discussed during the retrospective. Will it stay within the group? Will it be shared with leadership? Consider adopting the Chatham House Rule to help team members feel safe and comfortable.

2. Gather feedback

预估时间: 15 分钟

Once you’ve set the tone and expectations for the meeting, you can gather team members' feedback on how the last sprint went. There are many ways to do this, including:

  • 💬 Open group discussion about what went well and what didn’t
  • 🗒️ Surveys (anonymous or attributed)
  • ❤️ 4 Ls retrospective: Discuss what everyone loved, loathed, learned, and longed for during the last sprint
  • 🙂 The Sad, Mad, Glad framework: Discuss what made team members feel each of those emotions. What was disappointing? Frustrating? Exciting and encouraging?
Tip: Get people talking

One of the biggest obstacles to a sprint retrospective is when team members don’t share enough feedback. In addition to creating a safe space, try guiding the conversation with a simple structure like the 4Ls or Sad, Mad, Glad. You can also try collecting anonymous submissions.

If someone is dominating the conversation, call on others for their thoughts to make sure everyone gets their voice heard.

3. Turn feedback into insights

预估时间: 20 分钟

As a group, look for patterns and trends in the feedback. What did we learn? What changes could we make to build on the good things and minimize or avoid the bad things? These insights are key to setting goals and making improvements, so encourage everyone to contribute any they may have.

Tip: Be a trendspotter

Sprint retrospectives are about improving your next sprint, so focus more on patterns and trends vs. one-time mistakes or successes that likely won’t happen again.

4. Create action items

预估时间: 15 分钟

Now, it’s time to turn insights into action. This is where you can start setting goals and determine what changes to make for future sprints.

As you document changes and action items, be sure to assign owners and deadlines to kickstart progress.

Tip: Add action items to your task list

Rather than (or in addition to) writing action items on a sticky note or digital document, enter them directly into your sprint planning or project management system, such as Jira or Trello, so they’re already incorporated into your plans.

If any of the action items have corresponding tickets or issues, include those links on the retrospective page and/or tasks so it's easy to see the status.

5. Conclusion

预估时间: 5 分钟

Wrap up your sprint retrospective by thanking everyone for their contributions and sharing a summary of key takeaways and action items. Then, on to the next sprint!

变体

Don’t let your retros become stale, check-the-box, and let’s get outta here exercises that serve no purpose. There are various ways to encourage conversation, so experiment and see what works best for your group. Here are nine of our favorite sprint retrospective exercises.

一组问号

还有问题?

与其他 Atlassian 使用手册用户开始对话、获取支持或提供反馈。

您可能喜欢的其他演练
缩略图
会议

每周团队更新

分享进展情况—无需再安排会议。

书本插图
会议

页面主导型会议

更好的会议首先要有一页纸,概述会议目的、预期成果和关键讨论要点。

书本插图
沟通

用户手册

帮助您的队友了解如何最好地与您合作。

缩略图
文化

团队状况监控

评估团队的健康状况并确定改进计划。

了解最新信息

注册我们的时事通讯,获取最新的演练和 工作生活建议。

Thanks!

成功举行冲刺回顾会议的 5 个步骤

除了使用回顾模板,您还可以按照几个简单的步骤来成功举行冲刺回顾会议。应该欢迎团队中的每个人为会议做出贡献。收集反馈后,您就可以分析该反馈并创建改进操作项。

以下是成功举行冲刺回顾会议的 5 个步骤:

第 1 步:确定会议基调

确定会议基调是进行冲刺回顾的第一步。冲刺规划的目标是从不同角度收集反馈,并利用这些反馈设定目标和改进敏捷流程。每个人都应该觉得自己在冲刺审查中有发言权,因此从会议一开始就要定下这样的基调。

您要鼓励大家在冲刺回顾中分享反馈并提供有价值的洞察信息。专注于改进,而不是将错误归咎于他人,让每个人都能开诚布公地交流。

回顾 Confluence 模板
示例:Confluence

远程运行这个剧本?使用这个免费的回顾模板来指导对话并记录会话的输出。

在 Confluence 中打开

冲刺回顾会议想法

作为敏捷团队的负责人,您的工作不仅仅是了解 Scrum 板的基本知识,还必须主持会议,得出有价值的洞察信息。查看冲刺回顾示例可以帮助您为下一次冲刺回顾会议出谋划策,从而简化流程并收集有价值的反馈。

使用 4 Ls 方法可以鼓励团队成员提供反馈,让您快速了解哪些方面进展顺利,哪些方面需要改进。

您还可以使用“悲伤、生气、高兴”框架,在下一次冲刺回顾会上展开讨论。只需创建三列,就能为团队提供反馈模板:

  • 悲伤:是什么让您失望了?您觉得有什么地方可以改进吗?
  • 生气:是什么让您感到沮丧?是什么阻碍您发挥最佳水平了吗?
  • 高兴:在项目中您最喜欢的时刻是什么?您认为哪些方面进展顺利?

在冲刺回顾中鼓励讨论的方法有很多种,所以不要害怕尝试,以保持会议的活力。请记住,有些团队可能更喜欢匿名反馈,这并没有错。您可以定制冲刺回顾,确定适合您团队的方式。

在 Trello 中突出显示投票 Power-Up
点式投票

如果您需要就出现的想法达成共识,请使用点式投票来指导对话。