回顾2017，展望2018_回顾展回顾

回顾2017，展望2018

If you are using Scrum Framework or another agile process, a retrospective may be part of it. Does your team perform retrospectives? Are you getting value from your retrospectives?

如果您正在使用Scrum Framework或其他敏捷过程，则回顾可能是其中的一部分。 您的团队会进行回顾吗？ 您从回顾中获得价值吗？

I see a common anti-pattern when people conduct a retrospective for a sprint or write a root cause analysis for a defect. First they will point out the sequence of events that led to some code executing which caused the wrong thing to occur. Then to prevent that kind of problem from happening in the future they will basically conclude "we will try harder" or "we won't do that next time."

当人们对冲刺进行回顾或对缺陷进行根本原因分析时，我会看到一种常见的反模式。 首先，他们将指出导致某些代码执行并导致错误发生的事件序列。 然后，为防止将来发生此类问题，他们基本上会得出以下结论：“我们将更加努力”或“我们下次将不再这样做”。

The purpose of a retrospective is to improve your process continuously. First identify something that didn't go well; perhaps it's a defect. Next your team must examine each step of the process which resulted in the defect. For each step think about whether the defect got created in that step and whether the defect escaped detection in that step. Finally, decide what actions to take to improve your process.

回顾的目的是不断改进您的流程。 首先找出不顺利的地方； 也许这是一个缺陷。 接下来，您的团队必须检查导致缺陷的过程的每个步骤。 对于每个步骤，请考虑是否在该步骤中创建了缺陷，以及在该步骤中缺陷是否逃脱了检测。 最后，决定采取什么措施来改善您的流程。

For the scrum framework process, you might think about the following.

对于Scrum框架过程，您可能会考虑以下内容。

1. Did you groom the story in the backlog before adding it to the sprint?
   在将其添加到sprint之前，您是否整理了待办事项中的故事？
2. Was the story too big?
   这个故事太大了吗？
3. Did you rush to finish the story to make the sprint deadline?
   您是否急于完成故事以规定冲刺期限？
4. Were the acceptance criteria sufficient?
   接受标准是否足够？
5. Were the acceptance criteria specific?
   接受标准是否具体？
6. Did you write the acceptance criteria together or review them?
   您是一起编写接受标准还是对其进行审查？
7. Did you add acceptance criteria during the sprint instead of putting them on the backlog?
   您是否在冲刺期间添加了接受标准，而不是将其放入积压中？
8. Did you do Test Driven Development?
   您是否进行了测试驱动开发？
9. Were there sufficient automated unit, integration, and acceptance tests?
   是否有足够的自动化单元，集成和验收测试？
10. If you refactored, did you have sufficient automated tests in place before refactoring the code?
    如果您进行了重构，那么在重构代码之前，您是否已经进行了足够的自动化测试？
11. Did you demo the story with all of the acceptance criteria?
    您是否以所有接受标准来演示故事？

• Do you need to add backlog items to fix usability, performance or functional issues?
  您是否需要添加待办事项以解决可用性，性能或功能问题？
• Did the rollout go smoothly?
  部署顺利吗？
• Did you have a user story for the rollout?
  您是否有关于推广的用户故事？
• Were you able to measure or demonstrate the business value of the project?
  您是否能够衡量或证明项目的商业价值？

翻译自: https://www.experts-exchange.com/articles/17511/A-Retrospective-on-Retrospectives.html

回顾2017，展望2018