{"id":91,"date":"2012-07-20T18:01:40","date_gmt":"2012-07-20T16:01:40","guid":{"rendered":"http:\/\/proessler.wordpress.com\/?p=91"},"modified":"2012-07-20T18:01:40","modified_gmt":"2012-07-20T16:01:40","slug":"check-in-activity-agile-retrospectives","status":"publish","type":"post","link":"https:\/\/www.peterroessler.de\/blog\/check-in-activity-agile-retrospectives\/","title":{"rendered":"Check-In Activity for Agile Retrospectives"},"content":{"rendered":"<p><strong>Fortunately retrospectives are already a standard at <a href=\"http:\/\/www.chip.de\/\" target=\"_blank\" rel=\"noopener\">our company<\/a> now. Not only our developers teams, but also our sales team, our team assistents and as of late also our management (surprisingly, the last.. :)) have regular retrospectives. Because it has become standard to have retrospectives there is also the chance of falling into a dull routine, both for the team members and the facilitator (mostly myself). To counteract this dull routine we try to do different activities. I tried the following Check-In activity in the last weeks:<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-92\" title=\"Check-In-Agile-Retrospective\" src=\"https:\/\/www.peterroessler.de\/blog\/wp-content\/uploads\/2012\/07\/foto-20-07-12-16-07-09.jpg\" alt=\"\" width=\"250\" height=\"265\" \/>Esther Derby and Diana Larsen suggest in their book <a href=\"http:\/\/www.amazon.com\/gp\/product\/0977616649\/ref=as_li_ss_tl?ie=UTF8&amp;tag=321heinz-20&amp;linkCode=as2&amp;camp=217145&amp;creative=399369&amp;creativeASIN=0977616649\" target=\"_blank\" rel=\"noopener\">&#8220;Agile Retrospectives&#8221;<\/a> as a Check-In activity to ask every participant &#8220;In one or two words: What are your hopes or wishes for this retrospective&#8221;. No post-its, no explanation, just one or two words. This always works great.<\/p>\n<p>This question inspired me to ask participants an even more general question as a Check-In excercise: &#8220;Why are we doing retrospectives anyway?&#8221; I do this as a kind of fast brainstorming and jot everything down on a flipchart. It is surprising what the participants are coming up with. I heard everything from &#8220;I don&#8217;t know.&#8221; (Oops!) and &#8220;Because you told us to.&#8221; (Ooooooops!) to &#8220;Kaizen. Continuous Improvement.&#8221; (Thx.) and &#8220;We don&#8217;t want to do mistakes a second time.&#8221; (!!!)<\/p>\n<p>It is also a good excercise to remind the participants of the <a href=\"http:\/\/agilemanifesto.org\/principles.html\" target=\"_blank\" rel=\"noopener\">principles of the agile manifest<\/a>, one of them is: &#8220;At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.&#8221; (Dare to ask if everyone knows and understands the Agile Manifesto&#8230; and maybe be surprised.)<\/p>\n<p>And, of course, it is a good excercise to jolt the participants from their retrospective routine.<\/p>\n<p>BTW: I recognized only days ago that <a href=\"http:\/\/pragprog.com\/book\/dlret\/agile-retrospectives\" target=\"_blank\" rel=\"noopener\">Esther Derby and Diana Larsen book &#8220;Agile Retrospectives: Making Good Teams Great&#8221; is legally available also as eBook<\/a>! Buy it!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Fortunately retrospectives are already a standard at our company now. Not only our developers teams, but also our sales team, our team assistents and as of late also our management (surprisingly, the last.. :)) have regular retrospectives. Because it has become standard to have retrospectives there is also the chance of falling into a dull [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,7,9,10,11],"tags":[18,26,29,31,33,36,43,47,67,68],"class_list":["post-91","post","type-post","status-publish","format-standard","hentry","category-books","category-good-question","category-meeting-facilitation","category-scrum","category-scrumban","tag-agile-manifesto","tag-check-in","tag-continuous-improvement","tag-diana-larsen","tag-esther-derby","tag-flipchart","tag-inspect-adapt","tag-kaizen","tag-retrospective","tag-scrum"],"_links":{"self":[{"href":"https:\/\/www.peterroessler.de\/blog\/wp-json\/wp\/v2\/posts\/91","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.peterroessler.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.peterroessler.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.peterroessler.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.peterroessler.de\/blog\/wp-json\/wp\/v2\/comments?post=91"}],"version-history":[{"count":0,"href":"https:\/\/www.peterroessler.de\/blog\/wp-json\/wp\/v2\/posts\/91\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.peterroessler.de\/blog\/wp-json\/wp\/v2\/media?parent=91"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.peterroessler.de\/blog\/wp-json\/wp\/v2\/categories?post=91"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.peterroessler.de\/blog\/wp-json\/wp\/v2\/tags?post=91"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}