If someone asks "program will be, will stand daily, a review will only stay in, which you will stay," I will choose the retrospective. Plans and objectives will be daily station is to ensure the progress of the project, will review the target is to improve the team.
Our process features
From the process, the review will be very simple: a regular basis to everyone to come together, or a few words spit some slots, or thrown a pass rushes to the pot, and then find your mom back home. But obviously, the growth of this review will not help the project team.
Rejection pot cool moment ...... but can not solve any real problems
From the process, the review of our project team will have a few differences.
First, the project team held the first thing we will look back, that is the task of landing the follow-examination of the last meeting - sometimes even to check on the results of the last meeting, because of a retrospective of the "resolution" sometimes take several iteration can really bear fruit. After all, the review is to improve, improve must not stay in the meeting room, we can not stay in the minutes of the meeting, and must be able to floor plan, floor plan to have the results. Otherwise, in addition to Tucao sometimes cool outside, the review will also open white open.
This inspection teams with the "look back", "backstroke" is a reason
Secondly, voluntary or speak a different host named speaking, our review will require each person must speak. What is the content of speech, nothing more to say at least three "do better should continue to adhere to the point" and three "doing very good point needs to be changed" This. In fact, everyone must speak for quite upset at this point is just the beginning, because whether it is voluntary or statement named speak, there are people not prepared and just say a few words in question. But after a period of implementation, the project team everyone in their daily work to care what place there is a problem, what things pretty good, should also think about how to improve and enhance in their daily work. Only in this way can only have to look back at the meeting said that was not subject to host "There are no '" on these "" And now you think again, "asked speechless.
有些项目组的回顾会要求参会者把“做得好的地方”和“做得不太好的地方”先写在纸条上，然后逐一翻纸条来讨论。这样做当然无可厚非，不过我还是更倾向于公开发言的形式。第一，写在纸条上的内容通常都很简练，讨论时往往需要作者站出来做详细说明。这样一来，纸条就失去了它的匿名作用，与公开发言没有差别了。第二，公开发言有助于培养团队内开诚布公的交流氛围。就解决问题而言，最好的方式不是在回顾会上去反思、总结、改进，而是在问题发生时就发现、提出和解决它。如果内部都不能开诚布公的交流、而要靠小纸条这种方式来提意见，那这群人还能称作是一个团队吗？第三，公开发言对程序员是个不小的锻炼。程序员们总是有意无意地忽略表达与沟通的技巧——例如提出问题、列举事例、凝练论点、论述证明、总结发言，等等，以至于当在面试、晋升、技术分享、甚至是甩锅或者撩妹时，程序员们往往表现得张口结舌或者语无伦次，导致整个群体都被贴上了“木讷”“不好沟通”的标签。在回顾会上公开陈述自己的观点，无论对个人的表达能力还是对团队的沟通方式来说，都是很好的提高方式。
因为会上必须发言，所以我在回顾会前就会准备好发言提纲。这是我云笔记里记录的一篇提纲。
最后， 与个人发言一样，回顾会一定要有总结。这个总结，不仅是把参会者的发言复述一遍，更要把其中的最核心、最重要的意见和建议转化为可行的流程、举措，并指定负责人、以便于在下一个迭代周期内开始推动落实。这个事情说起来简单做起来难。为什么简单呢？因为办法总比问题多，回顾会上提出来的每个问题都能找出至少10种解决办法来。为什么难呢？因为我们必须从这10多种解决办法中，找到一个能够与项目组现行流程相契合的、在现行流程下最可行的方法来。
为什么强调现行流程呢？如果每一次回顾会都要在现行流程之外增加流程，很显然，日常工作流程会飞速膨胀，管理成本急剧上升，工作效率则会急剧下降。最后的结果一定是工作流程被丢到一边，大家怎么方便怎么来了。这样一来，回顾会的努力就完全成了水中捞月了。当然，有时回顾会也会删减工作流程，但这终归没有跳出对现行流程进行调整的五指山。
但是修改现有流程其实非常困难：不管是否合理、是否高效，现行工作流程一般是项目组成员在长时间的磨合、积累之后自发形成的，也是项目组成员非常熟悉和认可的。要想对它做出改变，就像要挪动一张桌子、在墙上开一扇窗户一样困难。这项工作不仅要求良好的流程设计——既能达到目标，又简便易行，还要求有力的推行、越挫越勇的毅力和长期的耐心。没错，即使简便易行，也要长期的、在挫折和阻力中，耐心地、一点一点地推动改变发生。
流程变更有点像火车并轨
我们的回顾成果
我们项目组就曾用这样的方式把代码评审加入到了敏捷开发的流程中来。
众所周知，代码评审是提高代码质量和编程能力的一个非常好的举措。我们项目组在调研了一些工具之后，也尝试着把它加入到我们的迭代流程中来。
最开始的方式是组织代码评审会，大家坐到会议室中一起看代码。但这样的评审会存在明显的弊端，在之后的回顾会上就被取消了，取而代之的是每个人在日常工作中自己去做评审。但这样也行不通。我们在回顾会上再一次讨论后，决定每个人都要在周二和周四的下午优先对其他成员的代码进行评审。这个法子收到了比较不错的成效，但还有一些不足。我们在又一次的回顾总结后，确定了每周二下午做开放式评审、每周四下午做回归评审的代码评审流程。再后来，我们还对代码评审结果做了量化分析……这样经过了若干次回顾会的讨论总结和若干个迭代周期的尝试推行，我们项目组才找到了适合自己的代码评审的方式。
这是在推行代码评审的过程中，我们的一次回顾会上的讨论记录
回顾会的“软条件”
不过，除了合理的流程之外，要想让回顾会发挥它应用的作用，还需要一些“软条件”。
First, we must establish an atmosphere of communication open and honest. Recalling the goal will be to improve the team work, allow the team more pleasant cooperation, team members work more liking. Recalling Responsibility will never be used, thrown pot, this kind of thing will only make the participants more and more to discord, so that future cooperation by the rejection become goal-oriented pan-oriented, and finally whether to do anything difficult, more efficiency and performance It is out of the question.
Diverge say, Responsibility, thrown pot this situation is relatively rare in the review meeting perhaps, but more common in the re-set at the meeting. After all, usually out of the question will be re-set to open, and thinking in general, a problem always someone to be responsible and scapegoat. But I think, it will review whether it is or will be re-set, should focus on the future rather than the past. In the past has been in the past, tomorrow is another day.
Cooperation, not confrontation, is a prerequisite of teamwork.
Secondly, there must be a meeting meeting minutes. Minutes of the meeting is the soul, the minutes do not record any meeting is a waste of time. Minutes of the meeting will review and no different from other meetings, the core lies the follow-up tasks and mandate holders. With the minutes of this meeting, we can check the previous task has not landed, how landing effect. Here you can make a note to the Word cloud advertising: its meeting minutes templates to very good.
And then branch off to say, how to organize an efficient meeting is actually a sort of knowledge. For example, will be distributed before the meeting materials at record meeting minutes, after follow-up mission will follow up work, sometimes just little things, but it can avoid opening a dozen people will waste time.
This is the proper way cloud notes meeting minutes templates provided
Finally, the moderator will review the need to understand and use some of the tips to guide you opening. Sometimes, participants speak too concise or superficial; sometimes, Moderator know - or think - participants can speak as well as talk about certain things; sometimes, participants can expect to host a the direction of multi-chats. In these cases, the host city, should also push or guide the participants to continue to speak with a little trick. For example, our review will host always kept on asking "And what" "these" "Think again", "forced" to give participants continue to think, continue to say. He's this little tricks, little thought, it would be a little wrap-up of our featured review of the project team.
Organize conferences and chaired the meeting, is a skill