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.
您将需要
- 会议场地或支持屏幕共享的视频会议。
- 数字协作工具（参见模板）。
- 可选：实物白板、记号笔、便利贴和计时器。
How to run a sprint retrospective
Reflect on past sprints to make improvements for the future.
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:
- Achieve continuous improvement
Building an action plan and following up on it in future meetings is critical for growth. - 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
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 使用手册用户开始对话、获取支持或提供反馈。
您可能喜欢的其他演练
会议
每周团队更新
分享进展情况—无需再安排会议。
会议
页面主导型会议
更好的会议首先要有一页纸，概述会议目的、预期成果和关键讨论要点。
沟通
用户手册
帮助您的队友了解如何最好地与您合作。
文化
团队状况监控
评估团队的健康状况并确定改进计划。
了解最新信息
注册我们的时事通讯，获取最新的演练和 工作生活建议。
团队在现场冲刺回顾中使用的便利贴
该团队使用 Confluence 指导他们的回顾性对话
分布式团队使用 Trello 设定基本规则、添加反馈、创建操作项和指导讨论
