…dumbfounding mess in Mississippi, which we know about because of one stubbornly honest engineer: http://www.nytimes.com/2016/07/05/science/kemper-coal-missis... [2] A good book is Larsen and Derby's Agile Retrospectives: https://www.amazon.com/Agile-Retrospectives-Making-Teams-Gre... [3] Also handy is the Retromat: http://plans-for-retrospectives.com/
Six hours is longer than I would use for a regular retrospective, but 30 min is very short. The format you’ve described is fairly shallow. Check and Derby and Larsen’s Agile Retrospectives for ideas about what you might be missing.
……不平等并威胁民主。《做酷客：让用户变得强大》（Badass: Making Users Awesome）。《IT安全中的社会工程学：工具、战术与技术》。《把乱摊子理清楚：人人都能懂的信息架构》（How to Make Sense of Any Mess）。《敏捷回顾：让优秀团队更卓越》（Agile Retrospectives: Making Good Teams Great）。《黑天鹅：如何应对不可预测的未来》（The Black Swan）。《互联网治理的全球博弈》（The Global War for Internet Governance）。《编码自由：黑客的伦理与美学》（Coding Freedom）。《网络空间中的仇恨犯罪》。《高……
…Inequality and Threatens Democracy. Badass: Making Users Awesome. Social Engineering in IT Security: Tools, Tactics, and Techniques. How to Make Sense of Any Mess: Information Architecture for Everybody. Agile Retrospectives: Making Good Teams Great. The Black Swan: The Impact of the Highly Improbable. The Global War for Internet Governance. Coding Freedom: The Ethics and Aesthetics of Hacking. Hate Crimes in Cyberspace. High…
…hierarchies [who] internally decide who does what, when, and how?" You aren't doing Scrum right. (Scrum Guide) Does your retrospective not include "Decide what to do?" You aren't doing retrospectives right. (Agile Retrospectives book.) In fairness hardly anybody does these things right, so it's tempting to lob No True Scotsman criticisms. But that's just as fallacious. A more accurate criticism might be to say that Agile & co.…
……提问、用一个词说出你的感受、5 个为什么（根因分析 Root Causes）或追问原因、聚焦解决方案/优势，以及对回顾会议的回顾。@BenLinders 《从敏捷回顾中获取价值》（Getting Value out of Agile Retrospectives）合著者
…asking questions, state your feelings with 1 word, 5 times why (Root Causes) or asking why, solution focused/strengths and retrospective of retrospectives. @BenLinders Co-author Getting Value out of Agile Retrospectives
……专注确实帮团队改善了我们的流程。我们一直在用 http://plans-for-retrospectives.com/ 来寻找活动灵感。我们的好几位敏捷教练（Agile Coach）都推荐过《敏捷回顾：让优秀团队更卓越》（Agile Retrospectives: Making Good Teams Great）这本书（不过我自己还没读过）。
…focus has helped the team actually improve things with our process. We've been using http://plans-for-retrospectives.com/ for ideas of the activities. A number of our Agile Coaches have recommended the "Agile Retrospectives: Making Good Teams Great" book (but I haven't read it myself).
……密西西比州那个让人目瞪口呆的烂摊子，多亏了一位执拗正直的工程师我们才得以知晓：http://www.nytimes.com/2016/07/05/science/kemper-coal-missis... [2] 一本好书是 Larsen 和 Derby 写的《敏捷回顾》（Agile Retrospectives）：https://www.amazon.com/Agile-Retrospectives-Making-Teams-Gre... [3] Retromat 这个网站也挺好用的：http://plans-for-retrospectives.com/
…dumbfounding mess in Mississippi, which we know about because of one stubbornly honest engineer: http://www.nytimes.com/2016/07/05/science/kemper-coal-missis... [2] A good book is Larsen and Derby's Agile Retrospectives: https://www.amazon.com/Agile-Retrospectives-Making-Teams-Gre... [3] Also handy is the Retromat: http://plans-for-retrospectives.com/
六个小时对于日常的回顾会议（retrospective）来说确实太长了，但 30 分钟又太短。你描述的这种形式相当流于表面。去翻翻 Derby 和 Larsen 写的《敏捷回顾》（Agile Retrospectives），找找你可能遗漏了哪些要点的思路吧。
Six hours is longer than I would use for a regular retrospective, but 30 min is very short. The format you’ve described is fairly shallow. Check and Derby and Larsen’s Agile Retrospectives for ideas about what you might be missing.
……不平等并威胁民主。《做酷客：让用户变得强大》（Badass: Making Users Awesome）。《IT安全中的社会工程学：工具、战术与技术》。《把乱摊子理清楚：人人都能懂的信息架构》（How to Make Sense of Any Mess）。《敏捷回顾：让优秀团队更卓越》（Agile Retrospectives: Making Good Teams Great）。《黑天鹅：如何应对不可预测的未来》（The Black Swan）。《互联网治理的全球博弈》（The Global War for Internet Governance）。《编码自由：黑客的伦理与美学》（Coding Freedom）。《网络空间中的仇恨犯罪》。《高……
…Inequality and Threatens Democracy. Badass: Making Users Awesome. Social Engineering in IT Security: Tools, Tactics, and Techniques. How to Make Sense of Any Mess: Information Architecture for Everybody. Agile Retrospectives: Making Good Teams Great. The Black Swan: The Impact of the Highly Improbable. The Global War for Internet Governance. Coding Freedom: The Ethics and Aesthetics of Hacking. Hate Crimes in Cyberspace. High…
……等级制度[由他们]在内部决定谁在何时以何种方式做什么事情？”那说明你们的 Scrum 姿势不对。（《Scrum 指南》）你们的回顾会议里没有“决定该做什么”吗？那说明你们的回顾姿势不对。（《敏捷回顾》Agile Retrospectives 一书。）说句公道话，几乎没人能把这些事做对，所以大家总忍不住掏出“没有真正的苏格兰人”（No True Scotsman）这套说辞来批判。但这同样是谬误。更准确的批评或许是说 Agile 及其同类……
…hierarchies [who] internally decide who does what, when, and how?" You aren't doing Scrum right. (Scrum Guide) Does your retrospective not include "Decide what to do?" You aren't doing retrospectives right. (Agile Retrospectives book.) In fairness hardly anybody does these things right, so it's tempting to lob No True Scotsman criticisms. But that's just as fallacious. A more accurate criticism might be to say that Agile & co.…
……提问、用一个词说出你的感受、5 个为什么（根因分析 Root Causes）或追问原因、聚焦解决方案/优势，以及对回顾会议的回顾。@BenLinders 《从敏捷回顾中获取价值》（Getting Value out of Agile Retrospectives）合著者
…asking questions, state your feelings with 1 word, 5 times why (Root Causes) or asking why, solution focused/strengths and retrospective of retrospectives. @BenLinders Co-author Getting Value out of Agile Retrospectives
……专注确实帮团队改善了我们的流程。我们一直在用 http://plans-for-retrospectives.com/ 来寻找活动灵感。我们的好几位敏捷教练（Agile Coach）都推荐过《敏捷回顾：让优秀团队更卓越》（Agile Retrospectives: Making Good Teams Great）这本书（不过我自己还没读过）。
…focus has helped the team actually improve things with our process. We've been using http://plans-for-retrospectives.com/ for ideas of the activities. A number of our Agile Coaches have recommended the "Agile Retrospectives: Making Good Teams Great" book (but I haven't read it myself).