（可翻譯為產品更新的“迭代(反覆運算)“）中。
Scrum Master（敏捷專家，就是管理這個sprint的人）
會在sprint快結束或者結束的當天開一個小會，
叫做Retrospective，主要是讓大家總結一些這個sprint中：
1我們做了什麼
2達成或者沒有達成什麼目標
3什麼地方做的好，如何可以做的更好
4什麼地方沒做好，遇到了什麼困難，如何改進
Retrospectives
Agile software teams made retrospective meetings popular, but they're great for all teams. Here's how to run basic retrospectives, and how to adapt them to suit your team. Don't miss the real-life example retrospective notes below step 4!
USE THIS PLAY TO...
- Provide a safe space for the team to reflect on and discuss what works well (and what doesn't!) so you can improve.
- If you're struggling with velocity, team cohesiveness, or tools and process on your Health Monitor, running this play might help.
AND I NEED THIS... WHY?
Ever have one of those dreams where you're running and running, but don't seem to be moving forward? It's all too easy for teams to have the same experience: making the same mistakes, doing things the way they've always done them, and working hard... but not really getting anywhere.
Executing on projects and providing services have a cyclical nature. And the teams who really excel are the teams who step outside that loop once in a while to reflect on what they've done lately and how it worked out. Armed with a lesson-learned or two, they can iterate on their processes and improve.
Retrospectives are a chance for the whole team to reflect on a project or period of work. The spirit should be of continuous improvement: a blame-free look back to capture actionable items that help everyone improve their work, their team, and the working environment.
WHO SHOULD BE INVOLVED?
Include the core project or service team, and perhaps a facilitator. Stakeholders and other peripheral folks should sit these out.