https://retrospectivewiki.org/api.php?action=feedcontributions&user=Robbowley&feedformat=atomAgile Retrospective Resource Wiki - User contributions [en-gb]2024-03-28T10:54:04ZUser contributionsMediaWiki 1.35.1https://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1190Agile Retrospective Resource Wiki2023-12-05T18:23:34Z<p>Robbowley: /* Contact */</p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
'''What is a retrospective?'''<br/><br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective plan]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will need to [[Special:RequestAccount| request an account]] to do so, which will need to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools & Exercises]]====<br />
Smaller exercises and tools which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Books,_Articles,_Videos | Books, Articles, Videos]]====<br />
Lots of resources where you can learn more about retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's Guide to Effective Retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
A collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
<br />
<br />
<br />
====Contact====<br />
This wiki is maintained by [https://twitter.com/robbowley Rob Bowley]. Please get in touch if you have any questions or issues.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1189Rob's Guide to Effective Retrospectives2023-04-26T08:37:33Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring meetings are not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional retrospectives which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working:<br />
<br />
'''''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the work in your team in your favourite work tracking tool<br />
<br />
===Rotate the facilitator role===<br />
It's common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn't) mean they have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour. This has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Books,_Articles,_Videos&diff=1188Books, Articles, Videos2023-02-14T07:47:00Z<p>Robbowley: </p>
<hr />
<div><br />
'''Books'''<br />
*[http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] by Derby and Larson<br />
*[http://www.dorsethouse.com/books/pr.html Project Retrospectives: a Handbook for team reviews] by Norman L Kerth<br />
*[https://leanpub.com/the-retrospective-handbook The Retrospective Handbook] by Patrick Kua<br />
*[http://innovationgames.com/ Innovation Games] by Luke Hohmann (and his [http://www.amazon.com/Innovation-Games-Creating-Breakthrough-Collaborative/dp/0321437292 book] of the same name)<br />
*[http://www.benlinders.com/getting-value-out-of-agile-retrospectives/ Getting Value out of Agile Retrospectives] by Luis Gonçalves and Ben Linders: download from [http://www.infoq.com/minibooks/agile-retrospectives-value InfoQ] or [https://leanpub.com/gettingvalueoutofagileretrospectives LeanPub], [http://www.amazon.com/Getting-Value-Agile-Retrospectives-Retrospective/dp/1304789624/ Paperback Edition]<br />
*[http://www.plans-for-retrospectives.com/print/index.html Retromat Print Edition] Fun printed version of the online [http://www.plans-for-retrospectives.com/ "Retr-O-Mat"]<br />
*[https://leanpub.com/b/agileretrospectives Leanpub bundle with six ebooks on Agile Retrospectives]<br />
*[https://www.retrium.com/ebook/become-a-retrospective-rockstar Become a Retrospective Rockstar], 21 agile experts share their best tips<br />
*[https://www.amazon.com/Agile-Retrospectives-Retrospective-improvement-retrospectives-ebook/dp/B01E98WTU2 Agile Retrospectives: 29 tips for continuous improvement with Scrum] by Paul VII<br />
*[https://www.amazon.com/dp/B07NKSDHPX Retrospectives. A Scrum Master's Guide] by Daria Bagina<br />
*[https://www.amazon.com/Improving-Agile-Retrospectives-Efficient-Addison-Wesley-ebook/dp/B0785W7PM6/ Improving Agile Retrospectives: Helping Teams Become More Efficient] by Marc Loeffler<br />
*[https://www.amazon.com/Obteniendo-valor-las-Retrospectivas-Agiles/dp/9492119048/ Obteniendo valor de las Retrospectivas Agiles (Spanish)] by Ben Linders <br />
<br />
'''Articles'''<br />
*[http://www.methodsandtools.com/archive/archive.php?id=63 Refactoring Your Development Process with Retrospectives] ([http://www.agilexp.com/agile-coach-rachel-davies.php Rachel Davies])<br />
*[http://www.infoq.com/retrospectives News, articles and presentations on retrospectives] from InfoQ<br />
*[http://www.projecttimes.com/articles/seven-steps-to-remarkable-retrospectives.html Seven Steps to Remarkable Retrospectives]<br />
*[https://www.linkedin.com/today/post/article/20140403210808-738843-agile-retrospectives-why-you-would-do-them Agile Retrospectives: Why You Would Do Them?]<br />
*[https://www.scrumalliance.org/community/articles/2014/june/agile-retrospectives-more-than-just-facts! Agile Retrospectives - More than just facts]<br />
*[https://www.linkedin.com/pulse/20141008072748-738843-sustainable-continuous-improvement-using-agile-retrospectives Sustainable Continuous Improvement Using Agile Retrospectives]<br />
*[https://luis-goncalves.com/agile-retrospectives-antipatterns/ A series of Agile Retrospectives Anti Patterns]<br />
*[http://www.sitepoint.com/making-agile-retrospectives-productive/ Making Agile Retrospective Productive]<br />
*[https://dzone.com/articles/facilitating-effective-agile-retrospectives Facilitating Effective Agile Retrospectives]<br />
*[https://www.benlinders.com/2017/state-of-practice-in-agile-retrospectives/ State of Practice in Agile Retrospectives]<br />
*[https://age-of-product.com/sprint-retrospective-anti-patterns/ 21 Sprint Retrospective Anti-Patterns Impeding Scrum Teams]<br />
*[https://luis-goncalves.com/agile-retrospectives/ Long Blog Post Explaining Agile Retrospectives] by Luis Goncalves<br />
*[https://agilestrides.com/blog/40-ideas-to-spice-up-your-retrospective/ 40 ideas to spice up your retrospective] by Ralph van Roosmalen<br />
*[https://play14.org/games/ Games] from Play14<br />
<br />
'''Blogs / Websites'''<br />
*[https://retrocadence.com/ Free Retrospective Tool]<br />
*[https://www.jmroxas.com/2018/03/15/a-smashing-retrospective/ A Smashing Retrospective! A guide on how to use a board game to run a retrospective]<br />
*[http://www.plans-for-retrospectives.com/ "Retr-O-Mat"] - Planning your next retrospective? Get started with a random plan, tweak it, print it and share the URL. Or just browse around for new ideas! » plans-for-retrospectives.com<br />
*[http://www.benlinders.com/exercises/ Retrospective Exercises Toolbox] - Use this toolbox with retrospective exercises to design your own valuable agile retrospectives!<br />
*[https://luis-goncalves.com/agile-retrospectives-ideas-exercises/ Ideas for Agile Retrospectives] by Luis Goncalves<br />
*[http://retrofibel.de/ Blog für Retrospektivenliebhaber by Marc Löffler (in German)] and the book (to be published) "Retrospectiven in der Praxis"<br />
*[http://www.benlinders.com/2011/getting-business-value-out-of-agile-retrospectives/ Getting business value out of Agile Retrospectives]<br />
*[http://idiacomputing.com/moin/IntrospectionAndRetrospectives Introspection And Retrospectives] and [http://idiacomputing.com/moin/RetrospectiveTechniques Restrospective Techniques]<br />
*[https://www.funretrospectives.com/ Fun Retrospectives: Activities and ideas for making agile retrospectives more engaging]<br />
*[https://sites.google.com/a/scrumplop.org/published-patterns/retrospective-pattern-language Scrum Patterns for Process Improvement]<br />
*[http://xp123.com/xplor/xp0509/index.shtml Some Patterns for Iteration Retrospectives]<br />
*[http://skycoach.be/2011/05/16/agile-retrospectives-anti-patterns/ Agile Retrospective Anti Patterns]<br />
*[https://www.scrumalliance.org/community/articles/2014/july/dos-and-don-ts-of-agile-retrospectives Do's and Don'ts of Agile Retrospectives]<br />
*[http://www.benlinders.com/2014/retrospectives-in-remote-teams/ Retrospectives in Remote Teams]<br />
*[https://www.mountaingoatsoftware.com/blog/does-a-scrum-team-need-a-retrospective-every-sprint#comments Does a Scrum Team Need a Retrospective Every Sprint?]<br />
*[http://www.benlinders.com/2016/doing-a-retrospective-when-you-cant-get-the-team-to-meet/ Doing a retrospective when you can’t get the team to meet]<br />
*[http://mwickman.com/how-to-fix-your-agile-scrum-retrospective-meetings/ How to Fix Your Agile Scrum Retrospective Meetings]<br />
*[https://medium.com/@benlinders/non-verbal-exercises-for-agile-retrospectives-ade5ca32ade#.bp42lqn9e Non-verbal Exercises for Agile Retrospectives]<br />
<br />
'''Video and Presentations'''<br />
*[http://www.tvagile.com/2010/08/30/retrospectives/ Video: Retrospectives Presentation at San Francisco Agile User Group]<br />
*[http://www.tvagile.com/2009/02/25/agile-retrospectives-making-good-teams-great/ Video: Agile Retrospectives - Making Good Teams Great!]<br />
*[http://www.slideshare.net/BenLinders/sustainable-improvement-through-retrospectives-sepg-europe-2013-ben-linders Sustainable Improvement through Retrospectives]<br />
*[http://www.slideshare.net/jchyip/a-guide-forpreparingandfacilitatingretrospectives A guide for Preparing and Facilitating Retrospectives]<br />
*[https://www.infoq.com/presentations/agile-retrospectives Spicing up Agile Retrospectives] [https://www.slideshare.net/BenLinders/spicing-up-agile-retrospectives-agile-tour-london-2015-ben-linders slides]<br />
*[https://www.slideshare.net/BenLinders/talk-improving-software-quality-with-retrospectives-testcon-moscow-2019-ben-linders Improving software quality with retrospectives]<br />
<br />
'''Online Training'''<br />
*[http://mwickman.com/effective-agile-meetings/ Effective Agile Retrospectives] by Martin Wickman<br />
*[https://www.benlinders.com/workshop-valuable-agile-retrospectives/ Valuable Agile Retrospectives for Teams] by Ben Linders</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1185Agile Retrospective Resource Wiki2022-09-09T12:13:33Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
'''What is a retrospective?'''<br/><br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective plan]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will need to [[Special:RequestAccount| request an account]] to do so, which will need to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools & Exercises]]====<br />
Smaller exercises and tools which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Books,_Articles,_Videos | Books, Articles, Videos]]====<br />
Lots of resources where you can learn more about retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's Guide to Effective Retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
A collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
<br />
<br />
<br />
====Contact====<br />
This wiki is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or issues.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Books,_Articles,_Videos&diff=1184Books, Articles, Videos2022-09-09T12:12:57Z<p>Robbowley: </p>
<hr />
<div><br />
'''Books'''<br />
*[http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] by Derby and Larson<br />
*[http://www.dorsethouse.com/books/pr.html Project Retrospectives: a Handbook for team reviews] by Norman L Kerth<br />
*[https://leanpub.com/the-retrospective-handbook The Retrospective Handbook] by Patrick Kua<br />
*[http://innovationgames.com/ Innovation Games] by Luke Hohmann (and his [http://www.amazon.com/Innovation-Games-Creating-Breakthrough-Collaborative/dp/0321437292 book] of the same name)<br />
*[http://www.benlinders.com/getting-value-out-of-agile-retrospectives/ Getting Value out of Agile Retrospectives] by Luis Gonçalves and Ben Linders: download from [http://www.infoq.com/minibooks/agile-retrospectives-value InfoQ] or [https://leanpub.com/gettingvalueoutofagileretrospectives LeanPub], [http://www.amazon.com/Getting-Value-Agile-Retrospectives-Retrospective/dp/1304789624/ Paperback Edition]<br />
*[http://www.plans-for-retrospectives.com/print/index.html Retromat Print Edition] Fun printed version of the online [http://www.plans-for-retrospectives.com/ "Retr-O-Mat"]<br />
*[https://leanpub.com/b/agileretrospectives Leanpub bundle with six ebooks on Agile Retrospectives]<br />
*[https://www.retrium.com/ebook/become-a-retrospective-rockstar Become a Retrospective Rockstar], 21 agile experts share their best tips<br />
*[https://www.amazon.com/Agile-Retrospectives-Retrospective-improvement-retrospectives-ebook/dp/B01E98WTU2 Agile Retrospectives: 29 tips for continuous improvement with Scrum] by Paul VII<br />
*[https://www.amazon.com/dp/B07NKSDHPX Retrospectives. A Scrum Master's Guide] by Daria Bagina<br />
*[https://www.amazon.com/Improving-Agile-Retrospectives-Efficient-Addison-Wesley-ebook/dp/B0785W7PM6/ Improving Agile Retrospectives: Helping Teams Become More Efficient] by Marc Loeffler<br />
*[https://www.amazon.com/Obteniendo-valor-las-Retrospectivas-Agiles/dp/9492119048/ Obteniendo valor de las Retrospectivas Agiles (Spanish)] by Ben Linders <br />
<br />
'''Articles'''<br />
*[http://www.methodsandtools.com/archive/archive.php?id=63 Refactoring Your Development Process with Retrospectives] ([http://www.agilexp.com/agile-coach-rachel-davies.php Rachel Davies])<br />
*[http://www.infoq.com/retrospectives News, articles and presentations on retrospectives] from InfoQ<br />
*[http://www.projecttimes.com/articles/seven-steps-to-remarkable-retrospectives.html Seven Steps to Remarkable Retrospectives]<br />
*[https://www.linkedin.com/today/post/article/20140403210808-738843-agile-retrospectives-why-you-would-do-them Agile Retrospectives: Why You Would Do Them?]<br />
*[https://www.scrumalliance.org/community/articles/2014/june/agile-retrospectives-more-than-just-facts! Agile Retrospectives - More than just facts]<br />
*[https://www.linkedin.com/pulse/20141008072748-738843-sustainable-continuous-improvement-using-agile-retrospectives Sustainable Continuous Improvement Using Agile Retrospectives]<br />
*[https://luis-goncalves.com/agile-retrospectives-antipatterns/ A series of Agile Retrospectives Anti Patterns]<br />
*[http://www.sitepoint.com/making-agile-retrospectives-productive/ Making Agile Retrospective Productive]<br />
*[https://dzone.com/articles/facilitating-effective-agile-retrospectives Facilitating Effective Agile Retrospectives]<br />
*[https://www.benlinders.com/2017/state-of-practice-in-agile-retrospectives/ State of Practice in Agile Retrospectives]<br />
*[https://age-of-product.com/sprint-retrospective-anti-patterns/ 21 Sprint Retrospective Anti-Patterns Impeding Scrum Teams]<br />
*[https://luis-goncalves.com/agile-retrospectives/ Long Blog Post Explaining Agile Retrospectives] by Luis Goncalves<br />
*[https://agilestrides.com/blog/40-ideas-to-spice-up-your-retrospective/ 40 ideas to spice up your retrospective] by Ralph van Roosmalen<br />
*[https://play14.org/games/ Games] from Play14<br />
<br />
'''Blogs / Websites'''<br />
*[https://retrocadence.com/ Free Retrospective Tool]<br />
*[https://www.jmroxas.com/2018/03/15/a-smashing-retrospective/ A Smashing Retrospective! A guide on how to use a board game to run a retrospective]<br />
*[http://www.plans-for-retrospectives.com/ "Retr-O-Mat"] - Planning your next retrospective? Get started with a random plan, tweak it, print it and share the URL. Or just browse around for new ideas! » plans-for-retrospectives.com<br />
*[http://www.benlinders.com/exercises/ Retrospective Exercises Toolbox] - Use this toolbox with retrospective exercises to design your own valuable agile retrospectives!<br />
*[https://luis-goncalves.com/agile-retrospectives-ideas-exercises/ Ideas for Agile Retrospectives] by Luis Goncalves<br />
*[http://retrofibel.de/ Blog für Retrospektivenliebhaber by Marc Löffler (in German)] and the book (to be published) "Retrospectiven in der Praxis"<br />
*[http://www.benlinders.com/2011/getting-business-value-out-of-agile-retrospectives/ Getting business value out of Agile Retrospectives]<br />
*[http://idiacomputing.com/moin/IntrospectionAndRetrospectives Introspection And Retrospectives] and [http://idiacomputing.com/moin/RetrospectiveTechniques Restrospective Techniques]<br />
*[https://www.funretrospectives.com/ Fun Retrospectives: Activities and ideas for making agile retrospectives more engaging]<br />
*[http://www.retrospectives.eu retrospectives.eu]<br />
*[http://blogs.msdn.com/b/jmeier/archive/2013/02/25/the-art-of-the-agile-retrospective.aspx The Art of the Agile Retrospective] by J.D. Meier<br />
*[https://sites.google.com/a/scrumplop.org/published-patterns/retrospective-pattern-language Scrum Patterns for Process Improvement]<br />
*[http://xp123.com/xplor/xp0509/index.shtml Some Patterns for Iteration Retrospectives]<br />
*[http://skycoach.be/2011/05/16/agile-retrospectives-anti-patterns/ Agile Retrospective Anti Patterns]<br />
*[https://www.scrumalliance.org/community/articles/2014/july/dos-and-don-ts-of-agile-retrospectives Do's and Don'ts of Agile Retrospectives]<br />
*[http://www.benlinders.com/2014/retrospectives-in-remote-teams/ Retrospectives in Remote Teams]<br />
*[https://www.mountaingoatsoftware.com/blog/does-a-scrum-team-need-a-retrospective-every-sprint#comments Does a Scrum Team Need a Retrospective Every Sprint?]<br />
*[http://www.benlinders.com/2016/doing-a-retrospective-when-you-cant-get-the-team-to-meet/ Doing a retrospective when you can’t get the team to meet]<br />
*[http://mwickman.com/how-to-fix-your-agile-scrum-retrospective-meetings/ How to Fix Your Agile Scrum Retrospective Meetings]<br />
*[https://medium.com/@benlinders/non-verbal-exercises-for-agile-retrospectives-ade5ca32ade#.bp42lqn9e Non-verbal Exercises for Agile Retrospectives]<br />
<br />
'''Video and Presentations'''<br />
*[http://www.tvagile.com/2010/08/30/retrospectives/ Video: Retrospectives Presentation at San Francisco Agile User Group]<br />
*[http://www.tvagile.com/2009/02/25/agile-retrospectives-making-good-teams-great/ Video: Agile Retrospectives - Making Good Teams Great!]<br />
*[http://www.slideshare.net/BenLinders/sustainable-improvement-through-retrospectives-sepg-europe-2013-ben-linders Sustainable Improvement through Retrospectives]<br />
*[http://www.slideshare.net/jchyip/a-guide-forpreparingandfacilitatingretrospectives A guide for Preparing and Facilitating Retrospectives]<br />
*[https://www.infoq.com/presentations/agile-retrospectives Spicing up Agile Retrospectives] [https://www.slideshare.net/BenLinders/spicing-up-agile-retrospectives-agile-tour-london-2015-ben-linders slides]<br />
*[https://www.slideshare.net/BenLinders/talk-improving-software-quality-with-retrospectives-testcon-moscow-2019-ben-linders Improving software quality with retrospectives]<br />
<br />
'''Online Training'''<br />
*[http://mwickman.com/effective-agile-meetings/ Effective Agile Retrospectives] by Martin Wickman<br />
*[https://www.benlinders.com/workshop-valuable-agile-retrospectives/ Valuable Agile Retrospectives for Teams] by Ben Linders</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=MediaWiki:Sidebar&diff=1183MediaWiki:Sidebar2022-09-09T12:09:51Z<p>Robbowley: </p>
<hr />
<div><br />
** Agile_Retrospective_Resource_Wiki| Home<br />
** Retrospective_Plans|Retrospective Plans<br />
** Tools & Exercises|Tools & Exercises<br />
** Books,_Articles,_Videos|Books, Articles, Videos<br />
** The_Prime_Directive|The Prime Directive<br />
** Tips_&_tricks|Tips & Tricks<br />
** Common_ailments_&_cures|Common Ailments & Cures<br />
** Rob's Guide to Effective Retrospectives|Rob's Guide to Effective Retrospectives<br />
** recentchanges-url|recentchanges<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=MediaWiki:Sidebar&diff=1182MediaWiki:Sidebar2022-09-09T12:08:19Z<p>Robbowley: </p>
<hr />
<div><br />
** Agile_Retrospective_Resource_Wiki| Home<br />
** Retrospective_Plans|Retrospective Plans<br />
** Tools & Exercises|Tools & Exercises<br />
** Tips_&_tricks|Tips & Tricks<br />
** Common_ailments_&_cures|Common Ailments & Cures<br />
** Retrospective_Surgery|Retrospective Surgery<br />
** The_Prime_Directive|The Prime Directive<br />
** Books,_Articles,_Videos|Books, Articles, Videos<br />
** Rob's Guide to Effective Retrospectives|Rob's Guide to Effective Retrospectives<br />
** recentchanges-url|recentchanges<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Books,_Articles,_Videos&diff=1181Books, Articles, Videos2022-09-09T12:06:55Z<p>Robbowley: Created page with " '''Books''' *[http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] by Derby and Larson *[http://www.dorsethouse.com/books/pr.htm..."</p>
<hr />
<div><br />
'''Books'''<br />
*[http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] by Derby and Larson<br />
*[http://www.dorsethouse.com/books/pr.html Project Retrospectives: a Handbook for team reviews] by Norman L Kerth<br />
*[https://leanpub.com/the-retrospective-handbook The Retrospective Handbook] by Patrick Kua<br />
*[http://innovationgames.com/ Innovation Games] by Luke Hohmann (and his [http://www.amazon.com/Innovation-Games-Creating-Breakthrough-Collaborative/dp/0321437292 book] of the same name)<br />
*[http://www.benlinders.com/getting-value-out-of-agile-retrospectives/ Getting Value out of Agile Retrospectives] by Luis Gonçalves and Ben Linders: download from [http://www.infoq.com/minibooks/agile-retrospectives-value InfoQ] or [https://leanpub.com/gettingvalueoutofagileretrospectives LeanPub], [http://www.amazon.com/Getting-Value-Agile-Retrospectives-Retrospective/dp/1304789624/ Paperback Edition]<br />
*[http://www.plans-for-retrospectives.com/print/index.html Retromat Print Edition] Fun printed version of the online [http://www.plans-for-retrospectives.com/ "Retr-O-Mat"]<br />
*[https://leanpub.com/b/agileretrospectives Leanpub bundle with six ebooks on Agile Retrospectives]<br />
*[https://www.retrium.com/ebook/become-a-retrospective-rockstar Become a Retrospective Rockstar], 21 agile experts share their best tips<br />
*[https://www.amazon.com/Agile-Retrospectives-Retrospective-improvement-retrospectives-ebook/dp/B01E98WTU2 Agile Retrospectives: 29 tips for continuous improvement with Scrum] by Paul VII<br />
*[https://www.benlinders.com/book/tag/retrospectives/ More books on Agile Retrospectives]<br />
*[https://www.amazon.com/dp/B07NKSDHPX Retrospectives. A Scrum Master's Guide] by Daria Bagina<br />
*[https://www.amazon.com/Improving-Agile-Retrospectives-Efficient-Addison-Wesley-ebook/dp/B0785W7PM6/ Improving Agile Retrospectives: Helping Teams Become More Efficient] by Marc Loeffler<br />
*[https://www.amazon.com/Obteniendo-valor-las-Retrospectivas-Agiles/dp/9492119048/ Obteniendo valor de las Retrospectivas Agiles (Spanish)] by Ben Linders <br />
<br />
'''Articles'''<br />
*[http://www.methodsandtools.com/archive/archive.php?id=63 Refactoring Your Development Process with Retrospectives] ([http://www.agilexp.com/agile-coach-rachel-davies.php Rachel Davies])<br />
*[http://www.infoq.com/retrospectives News, articles and presentations on retrospectives] from InfoQ<br />
*[http://www.projecttimes.com/articles/seven-steps-to-remarkable-retrospectives.html Seven Steps to Remarkable Retrospectives]<br />
*[https://www.linkedin.com/today/post/article/20140403210808-738843-agile-retrospectives-why-you-would-do-them Agile Retrospectives: Why You Would Do Them?]<br />
*[https://www.scrumalliance.org/community/articles/2014/june/agile-retrospectives-more-than-just-facts! Agile Retrospectives - More than just facts]<br />
*[https://www.linkedin.com/pulse/20141008072748-738843-sustainable-continuous-improvement-using-agile-retrospectives Sustainable Continuous Improvement Using Agile Retrospectives]<br />
*[https://luis-goncalves.com/agile-retrospectives-antipatterns/ A series of Agile Retrospectives Anti Patterns]<br />
*[http://www.sitepoint.com/making-agile-retrospectives-productive/ Making Agile Retrospective Productive]<br />
*[https://dzone.com/articles/facilitating-effective-agile-retrospectives Facilitating Effective Agile Retrospectives]<br />
*[https://www.benlinders.com/2017/state-of-practice-in-agile-retrospectives/ State of Practice in Agile Retrospectives]<br />
*[https://age-of-product.com/sprint-retrospective-anti-patterns/ 21 Sprint Retrospective Anti-Patterns Impeding Scrum Teams]<br />
*[https://luis-goncalves.com/agile-retrospectives/ Long Blog Post Explaining Agile Retrospectives] by Luis Goncalves<br />
*[https://agilestrides.com/blog/40-ideas-to-spice-up-your-retrospective/ 40 ideas to spice up your retrospective] by Ralph van Roosmalen<br />
*[https://play14.org/games/ Games] from Play14<br />
<br />
'''Blogs / Websites'''<br />
*[https://retrocadence.com/ Free Retrospective Tool]<br />
*[https://www.jmroxas.com/2018/03/15/a-smashing-retrospective/ A Smashing Retrospective! A guide on how to use a board game to run a retrospective]<br />
*[http://www.plans-for-retrospectives.com/ "Retr-O-Mat"] - Planning your next retrospective? Get started with a random plan, tweak it, print it and share the URL. Or just browse around for new ideas! » plans-for-retrospectives.com<br />
*[http://www.benlinders.com/exercises/ Retrospective Exercises Toolbox] - Use this toolbox with retrospective exercises to design your own valuable agile retrospectives!<br />
*[https://luis-goncalves.com/agile-retrospectives-ideas-exercises/ Ideas for Agile Retrospectives] by Luis Goncalves<br />
*[http://retrofibel.de/ Blog für Retrospektivenliebhaber by Marc Löffler (in German)] and the book (to be published) "Retrospectiven in der Praxis"<br />
*[http://www.benlinders.com/2011/getting-business-value-out-of-agile-retrospectives/ Getting business value out of Agile Retrospectives]<br />
*[http://idiacomputing.com/moin/IntrospectionAndRetrospectives Introspection And Retrospectives] and [http://idiacomputing.com/moin/RetrospectiveTechniques Restrospective Techniques]<br />
*[https://www.funretrospectives.com/ Fun Retrospectives: Activities and ideas for making agile retrospectives more engaging]<br />
*[http://www.retrospectives.eu retrospectives.eu]<br />
*[http://blogs.msdn.com/b/jmeier/archive/2013/02/25/the-art-of-the-agile-retrospective.aspx The Art of the Agile Retrospective] by J.D. Meier<br />
*[https://sites.google.com/a/scrumplop.org/published-patterns/retrospective-pattern-language Scrum Patterns for Process Improvement]<br />
*[http://xp123.com/xplor/xp0509/index.shtml Some Patterns for Iteration Retrospectives]<br />
*[http://skycoach.be/2011/05/16/agile-retrospectives-anti-patterns/ Agile Retrospective Anti Patterns]<br />
*[https://www.scrumalliance.org/community/articles/2014/july/dos-and-don-ts-of-agile-retrospectives Do's and Don'ts of Agile Retrospectives]<br />
*[http://www.benlinders.com/2014/retrospectives-in-remote-teams/ Retrospectives in Remote Teams]<br />
*[https://www.mountaingoatsoftware.com/blog/does-a-scrum-team-need-a-retrospective-every-sprint#comments Does a Scrum Team Need a Retrospective Every Sprint?]<br />
*[http://www.benlinders.com/2016/doing-a-retrospective-when-you-cant-get-the-team-to-meet/ Doing a retrospective when you can’t get the team to meet]<br />
*[http://mwickman.com/how-to-fix-your-agile-scrum-retrospective-meetings/ How to Fix Your Agile Scrum Retrospective Meetings]<br />
*[https://medium.com/@benlinders/non-verbal-exercises-for-agile-retrospectives-ade5ca32ade#.bp42lqn9e Non-verbal Exercises for Agile Retrospectives]<br />
<br />
'''Video and Presentations'''<br />
*[http://www.tvagile.com/2010/08/30/retrospectives/ Video: Retrospectives Presentation at San Francisco Agile User Group]<br />
*[http://www.tvagile.com/2009/02/25/agile-retrospectives-making-good-teams-great/ Video: Agile Retrospectives - Making Good Teams Great!]<br />
*[http://www.slideshare.net/BenLinders/sustainable-improvement-through-retrospectives-sepg-europe-2013-ben-linders Sustainable Improvement through Retrospectives]<br />
*[http://www.slideshare.net/jchyip/a-guide-forpreparingandfacilitatingretrospectives A guide for Preparing and Facilitating Retrospectives]<br />
*[https://www.infoq.com/presentations/agile-retrospectives Spicing up Agile Retrospectives] [https://www.slideshare.net/BenLinders/spicing-up-agile-retrospectives-agile-tour-london-2015-ben-linders slides]<br />
*[https://www.slideshare.net/BenLinders/talk-improving-software-quality-with-retrospectives-testcon-moscow-2019-ben-linders Improving software quality with retrospectives]<br />
<br />
'''Online Training'''<br />
*[http://mwickman.com/effective-agile-meetings/ Effective Agile Retrospectives] by Martin Wickman<br />
*[https://www.benlinders.com/workshop-valuable-agile-retrospectives/ Valuable Agile Retrospectives for Teams] by Ben Linders</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Tools_%26_Exercises&diff=1180Tools & Exercises2022-09-09T12:05:08Z<p>Robbowley: </p>
<hr />
<div>Not full retrospectives plans but exercises that can be used as a part of retrospectives, to gauge the mood or expose issues.<br />
<br />
*[https://retrocadence.com/ Agile Retrospective Tool With Built In Retrospective Templates]<br />
*[https://nomad8.com/articles/chart-your-happiness Happiness Histogram]<br />
*[[Warm Up Exercise - Sprint Draw & Guess]]<br />
*[http://xp123.com/articles/xp-radar-chart/ XP Radar]<br />
*[http://www.benlinders.com/2014/retrospective-exercise-vital-few-actions/ Vital Few Actions]<br />
*[http://www.google.co.uk/search?rlz=1C1GGLS_enGB319GB319&sourceid=chrome&ie=UTF-8&q=six+action+shoes+de+bono Six Action Shoes] by De Bono<br />
*[http://en.wikipedia.org/wiki/Six_Thinking_Hats Six Hats Thinking] by De Bono<br />
*[http://www.benlinders.com/2013/which-questions-do-you-ask-in-retrospectives/ Retrospective Questions]<br />
*[http://en.wikipedia.org/wiki/5_Whys 5 Whys] and the [http://www.benlinders.com/2013/getting-to-the-root-causes-of-problems-in-a-retrospective/ 5 Why's retrospective]<br />
*[http://www.benlinders.com/2013/feelings-matter-in-agile-retrospectives/ 1 Word Retrospective]<br />
*[[Retrospective Dialogue Sheets]]<br />
*[http://www.benlinders.com/2013/improving-collaboration-in-agile-projects-with-the-retrospective-of-retrospectives/ Retrospective of Retrospectives]<br />
*[https://www.benlinders.com/news/agile-retrospectives-bingo-released/ Agile Retrospective Bingo]<br />
*[http://www.benlinders.com/2014/getting-feedback-with-the-perfection-game/ Perfection Game]<br />
*[http://practiceagile.com/the-power-of-anonymous-retrospectives/ Anonymous Retrospectives]<br />
*[http://blog.crisp.se/2013/01/22/henrikkniberg/how-to-run-a-big-retrospectives Big Retrospectives]<br />
*[http://www.benlinders.com/2014/retrospectives-for-teams-with-multiple-customers/ Multiple Customers]<br />
*[http://www.funretrospectives.com/fishbowl-conversation/ Fishbowl Conversation]<br />
*[https://www.benlinders.com/game/ Agile Self-assessment Game]<br />
*[https://age-of-product.com/retrospective-exercises/ Retrospective Exercises Repository]</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1177Agile Retrospective Resource Wiki2022-03-10T14:16:14Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
'''What is a retrospective?'''<br/><br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective plan]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will need to [[Special:RequestAccount| request an account]] to do so, which will need to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools & Exercises]]====<br />
Smaller exercises and tools which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's Guide to Effective Retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
A collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or issues.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1176Agile Retrospective Resource Wiki2022-03-10T14:12:56Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
'''What are retrospectives?'''<br/><br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective plan]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will need to [[Special:RequestAccount| request an account]] to do so, which will need to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools & Exercises]]====<br />
Smaller exercises and tools which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's Guide to Effective Retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
A collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or issues.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1175Agile Retrospective Resource Wiki2022-03-10T14:12:43Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
'''What are retrospectives?'''<br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective plan]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will need to [[Special:RequestAccount| request an account]] to do so, which will need to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools & Exercises]]====<br />
Smaller exercises and tools which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's Guide to Effective Retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
A collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or issues.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1174Agile Retrospective Resource Wiki2022-03-10T12:11:35Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective plan]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will need to [[Special:RequestAccount| request an account]] to do so, which will need to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools & Exercises]]====<br />
Smaller exercises and tools which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's Guide to Effective Retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
A collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or issues.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1173Agile Retrospective Resource Wiki2022-03-10T12:06:22Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective plan]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will need to [[Special:RequestAccount| request an account]] to do so, which will need to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools & Exercises]]====<br />
Smaller exercises and tools which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
Currently a random collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's Guide to Effective Retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or issues.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1172Agile Retrospective Resource Wiki2022-03-10T12:01:18Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective plan]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will need to [[Special:RequestAccount| request an account]] to do so, which will need to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools]]====<br />
Smaller exercises which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
Currently a random collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's Guide to Effective Retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or issues.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=MediaWiki:Sidebar&diff=1171MediaWiki:Sidebar2022-03-10T12:00:16Z<p>Robbowley: </p>
<hr />
<div><br />
** Agile_Retrospective_Resource_Wiki| Home<br />
** Retrospective_Plans|Retrospective Plans<br />
** Tools & Exercises|Tools & Exercises<br />
** Tips_&_tricks|Tips & Tricks<br />
** Common_ailments_&_cures|Common Ailments & Cures<br />
** Retrospective_Surgery|Retrospective Surgery<br />
** The_Prime_Directive|The Prime Directive<br />
** External_Resources|External Resources<br />
** Rob's Guide to Effective Retrospectives|Rob's Guide to Effective Retrospectives<br />
** recentchanges-url|recentchanges<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Tools&diff=1170Tools2022-03-10T11:57:36Z<p>Robbowley: Robbowley moved page Tools to Tools & Exercises</p>
<hr />
<div>#REDIRECT [[Tools & Exercises]]</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Tools_%26_Exercises&diff=1169Tools & Exercises2022-03-10T11:57:36Z<p>Robbowley: Robbowley moved page Tools to Tools & Exercises</p>
<hr />
<div>Not full retrospectives plans but exercises that can be used as a part of retrospectives, to gauge the mood or expose issues.<br />
<br />
*[https://retrocadence.com/ Agile Retrospective Tool With Built In Retrospective Templates]<br />
*[https://nomad8.com/articles/chart-your-happiness Happiness Histogram]<br />
*[[Warm Up Exercise - Sprint Draw & Guess]]<br />
*[http://xp123.com/articles/xp-radar-chart/ XP Radar]<br />
*[http://www.scrum-toolkit.com/ Scrum Toolkit]<br />
*[http://www.benlinders.com/2014/retrospective-exercise-vital-few-actions/ Vital Few Actions]<br />
*[http://www.google.co.uk/search?rlz=1C1GGLS_enGB319GB319&sourceid=chrome&ie=UTF-8&q=six+action+shoes+de+bono Six Action Shoes] by De Bono<br />
*[http://en.wikipedia.org/wiki/Six_Thinking_Hats Six Hats Thinking] by De Bono<br />
*[http://www.benlinders.com/2013/which-questions-do-you-ask-in-retrospectives/ Retrospective Questions]<br />
*[http://en.wikipedia.org/wiki/5_Whys 5 Whys] and the [http://www.benlinders.com/2013/getting-to-the-root-causes-of-problems-in-a-retrospective/ 5 Why's retrospective]<br />
*[http://accel-team.com/techniques/force_field_analysis.html Force Field Analysis]<br />
*[http://www.benlinders.com/2013/feelings-matter-in-agile-retrospectives/ 1 Word Retrospective]<br />
*[[Retrospective Dialogue Sheets]]<br />
*[http://www.benlinders.com/2013/improving-collaboration-in-agile-projects-with-the-retrospective-of-retrospectives/ Retrospective of Retrospectives]<br />
*[http://skycoach.be/2013/09/17/boring-retrospectives-10-walk-the-board/ Walk the Board]<br />
*[https://www.benlinders.com/news/agile-retrospectives-bingo-released/ Agile Retrospective Bingo]<br />
*[http://agilethings.nl/lego-goes-retro/ Retrospectives with Lego]<br />
*[http://www.benlinders.com/2014/getting-feedback-with-the-perfection-game/ Perfection Game]<br />
*[http://practiceagile.com/the-power-of-anonymous-retrospectives/ Anonymous Retrospectives]<br />
*[http://blog.crisp.se/2013/01/22/henrikkniberg/how-to-run-a-big-retrospectives Big Retrospectives]<br />
*[http://www.benlinders.com/2014/retrospectives-for-teams-with-multiple-customers/ Multiple Customers]<br />
*[http://www.funretrospectives.com/fishbowl-conversation/ Fishbowl Conversation]<br />
*[https://www.benlinders.com/game/ Agile Self-assessment Game]<br />
*[https://age-of-product.com/retrospective-exercises/ Retrospective Exercises Repository]<br />
*[https://skycoach.be/2010/06/17/12-retrospective-exercises/ 12 retrospective exercises]</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Tools_%26_Exercises&diff=1168Tools & Exercises2022-03-10T11:56:01Z<p>Robbowley: </p>
<hr />
<div>Not full retrospectives plans but exercises that can be used as a part of retrospectives, to gauge the mood or expose issues.<br />
<br />
*[https://retrocadence.com/ Agile Retrospective Tool With Built In Retrospective Templates]<br />
*[https://nomad8.com/articles/chart-your-happiness Happiness Histogram]<br />
*[[Warm Up Exercise - Sprint Draw & Guess]]<br />
*[http://xp123.com/articles/xp-radar-chart/ XP Radar]<br />
*[http://www.scrum-toolkit.com/ Scrum Toolkit]<br />
*[http://www.benlinders.com/2014/retrospective-exercise-vital-few-actions/ Vital Few Actions]<br />
*[http://www.google.co.uk/search?rlz=1C1GGLS_enGB319GB319&sourceid=chrome&ie=UTF-8&q=six+action+shoes+de+bono Six Action Shoes] by De Bono<br />
*[http://en.wikipedia.org/wiki/Six_Thinking_Hats Six Hats Thinking] by De Bono<br />
*[http://www.benlinders.com/2013/which-questions-do-you-ask-in-retrospectives/ Retrospective Questions]<br />
*[http://en.wikipedia.org/wiki/5_Whys 5 Whys] and the [http://www.benlinders.com/2013/getting-to-the-root-causes-of-problems-in-a-retrospective/ 5 Why's retrospective]<br />
*[http://accel-team.com/techniques/force_field_analysis.html Force Field Analysis]<br />
*[http://www.benlinders.com/2013/feelings-matter-in-agile-retrospectives/ 1 Word Retrospective]<br />
*[[Retrospective Dialogue Sheets]]<br />
*[http://www.benlinders.com/2013/improving-collaboration-in-agile-projects-with-the-retrospective-of-retrospectives/ Retrospective of Retrospectives]<br />
*[http://skycoach.be/2013/09/17/boring-retrospectives-10-walk-the-board/ Walk the Board]<br />
*[https://www.benlinders.com/news/agile-retrospectives-bingo-released/ Agile Retrospective Bingo]<br />
*[http://agilethings.nl/lego-goes-retro/ Retrospectives with Lego]<br />
*[http://www.benlinders.com/2014/getting-feedback-with-the-perfection-game/ Perfection Game]<br />
*[http://practiceagile.com/the-power-of-anonymous-retrospectives/ Anonymous Retrospectives]<br />
*[http://blog.crisp.se/2013/01/22/henrikkniberg/how-to-run-a-big-retrospectives Big Retrospectives]<br />
*[http://www.benlinders.com/2014/retrospectives-for-teams-with-multiple-customers/ Multiple Customers]<br />
*[http://www.funretrospectives.com/fishbowl-conversation/ Fishbowl Conversation]<br />
*[https://www.benlinders.com/game/ Agile Self-assessment Game]<br />
*[https://age-of-product.com/retrospective-exercises/ Retrospective Exercises Repository]<br />
*[https://skycoach.be/2010/06/17/12-retrospective-exercises/ 12 retrospective exercises]</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1167Agile Retrospective Resource Wiki2022-03-10T11:54:04Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective plan]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will need to [[Special:RequestAccount| request an account]] to do so, which will need to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools]]====<br />
Smaller exercises which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
Currently a random collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's guide to effective retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or issues.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1166Agile Retrospective Resource Wiki2022-03-10T11:52:35Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective plan]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will need to [[Special:RequestAccount| request an account]] to do so, which will need to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools]]====<br />
Smaller exercises which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
Currently a random collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's guide to effective retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki was set up and is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or thoughts on how to improve the wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1165Agile Retrospective Resource Wiki2022-03-10T11:51:32Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
''"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects."'' - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will have to [[Special:RequestAccount| request an account]] to do so, which will have to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools]]====<br />
Smaller exercises which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
Currently a random collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's guide to effective retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki was set up and is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or thoughts on how to improve the wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1164Agile Retrospective Resource Wiki2022-03-10T11:50:49Z<p>Robbowley: /* Welcome! */</p>
<hr />
<div>__NOTOC__<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects." - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will have to [[Special:RequestAccount| request an account]] to do so, which will have to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools]]====<br />
Smaller exercises which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
Currently a random collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's guide to effective retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki was set up and is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or thoughts on how to improve the wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1163Agile Retrospective Resource Wiki2022-03-09T14:15:33Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
=Welcome!=<br />
<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects." - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will have to [[Special:RequestAccount| request an account]] to do so, which will have to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools]]====<br />
Smaller exercises which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
Currently a random collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's guide to effective retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki was set up and is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or thoughts on how to improve the wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=External_Resources&diff=1162External Resources2022-03-09T14:10:44Z<p>Robbowley: </p>
<hr />
<div><br />
'''Books'''<br />
*[http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] by Derby and Larson<br />
*[http://www.dorsethouse.com/books/pr.html Project Retrospectives: a Handbook for team reviews] by Norman L Kerth<br />
*[https://leanpub.com/the-retrospective-handbook The Retrospective Handbook] by Patrick Kua<br />
*[http://innovationgames.com/ Innovation Games] by Luke Hohmann (and his [http://www.amazon.com/Innovation-Games-Creating-Breakthrough-Collaborative/dp/0321437292 book] of the same name)<br />
*[http://www.benlinders.com/getting-value-out-of-agile-retrospectives/ Getting Value out of Agile Retrospectives] by Luis Gonçalves and Ben Linders: download from [http://www.infoq.com/minibooks/agile-retrospectives-value InfoQ] or [https://leanpub.com/gettingvalueoutofagileretrospectives LeanPub], [http://www.amazon.com/Getting-Value-Agile-Retrospectives-Retrospective/dp/1304789624/ Paperback Edition]<br />
*[http://www.plans-for-retrospectives.com/print/index.html Retromat Print Edition] Fun printed version of the online [http://www.plans-for-retrospectives.com/ "Retr-O-Mat"]<br />
*[https://leanpub.com/b/agileretrospectives Leanpub bundle with six ebooks on Agile Retrospectives]<br />
*[https://www.retrium.com/ebook/become-a-retrospective-rockstar Become a Retrospective Rockstar], 21 agile experts share their best tips<br />
*[https://www.amazon.com/Agile-Retrospectives-Retrospective-improvement-retrospectives-ebook/dp/B01E98WTU2 Agile Retrospectives: 29 tips for continuous improvement with Scrum] by Paul VII<br />
*[https://www.benlinders.com/book/tag/retrospectives/ More books on Agile Retrospectives]<br />
*[https://www.amazon.com/dp/B07NKSDHPX Retrospectives. A Scrum Master's Guide] by Daria Bagina<br />
*[https://www.amazon.com/Improving-Agile-Retrospectives-Efficient-Addison-Wesley-ebook/dp/B0785W7PM6/ Improving Agile Retrospectives: Helping Teams Become More Efficient] by Marc Loeffler<br />
*[https://www.amazon.com/Obteniendo-valor-las-Retrospectivas-Agiles/dp/9492119048/ Obteniendo valor de las Retrospectivas Agiles (Spanish)] by Ben Linders <br />
<br />
'''Articles'''<br />
*[http://www.methodsandtools.com/archive/archive.php?id=63 Refactoring Your Development Process with Retrospectives] ([http://www.agilexp.com/agile-coach-rachel-davies.php Rachel Davies])<br />
*[http://www.infoq.com/retrospectives News, articles and presentations on retrospectives] from InfoQ<br />
*[http://www.projecttimes.com/articles/seven-steps-to-remarkable-retrospectives.html Seven Steps to Remarkable Retrospectives]<br />
*[https://www.linkedin.com/today/post/article/20140403210808-738843-agile-retrospectives-why-you-would-do-them Agile Retrospectives: Why You Would Do Them?]<br />
*[https://www.scrumalliance.org/community/articles/2014/june/agile-retrospectives-more-than-just-facts! Agile Retrospectives - More than just facts]<br />
*[https://www.linkedin.com/pulse/20141008072748-738843-sustainable-continuous-improvement-using-agile-retrospectives Sustainable Continuous Improvement Using Agile Retrospectives]<br />
*[https://luis-goncalves.com/agile-retrospectives-antipatterns/ A series of Agile Retrospectives Anti Patterns]<br />
*[http://www.sitepoint.com/making-agile-retrospectives-productive/ Making Agile Retrospective Productive]<br />
*[https://dzone.com/articles/facilitating-effective-agile-retrospectives Facilitating Effective Agile Retrospectives]<br />
*[https://www.benlinders.com/2017/state-of-practice-in-agile-retrospectives/ State of Practice in Agile Retrospectives]<br />
*[https://age-of-product.com/sprint-retrospective-anti-patterns/ 21 Sprint Retrospective Anti-Patterns Impeding Scrum Teams]<br />
*[https://luis-goncalves.com/agile-retrospectives/ Long Blog Post Explaining Agile Retrospectives] by Luis Goncalves<br />
*[https://agilestrides.com/blog/40-ideas-to-spice-up-your-retrospective/ 40 ideas to spice up your retrospective] by Ralph van Roosmalen<br />
*[https://play14.org/games/ Games] from Play14<br />
<br />
'''Blogs / Websites'''<br />
*[https://retrocadence.com/ Free Retrospective Tool]<br />
*[https://www.jmroxas.com/2018/03/15/a-smashing-retrospective/ A Smashing Retrospective! A guide on how to use a board game to run a retrospective]<br />
*[http://www.plans-for-retrospectives.com/ "Retr-O-Mat"] - Planning your next retrospective? Get started with a random plan, tweak it, print it and share the URL. Or just browse around for new ideas! » plans-for-retrospectives.com<br />
*[http://www.benlinders.com/exercises/ Retrospective Exercises Toolbox] - Use this toolbox with retrospective exercises to design your own valuable agile retrospectives!<br />
*[https://luis-goncalves.com/agile-retrospectives-ideas-exercises/ Ideas for Agile Retrospectives] by Luis Goncalves<br />
*[http://retrofibel.de/ Blog für Retrospektivenliebhaber by Marc Löffler (in German)] and the book (to be published) "Retrospectiven in der Praxis"<br />
*[http://www.benlinders.com/2011/getting-business-value-out-of-agile-retrospectives/ Getting business value out of Agile Retrospectives]<br />
*[http://idiacomputing.com/moin/IntrospectionAndRetrospectives Introspection And Retrospectives] and [http://idiacomputing.com/moin/RetrospectiveTechniques Restrospective Techniques]<br />
*[https://www.funretrospectives.com/ Fun Retrospectives: Activities and ideas for making agile retrospectives more engaging]<br />
*[http://www.retrospectives.eu retrospectives.eu]<br />
*[http://blogs.msdn.com/b/jmeier/archive/2013/02/25/the-art-of-the-agile-retrospective.aspx The Art of the Agile Retrospective] by J.D. Meier<br />
*[https://sites.google.com/a/scrumplop.org/published-patterns/retrospective-pattern-language Scrum Patterns for Process Improvement]<br />
*[http://xp123.com/xplor/xp0509/index.shtml Some Patterns for Iteration Retrospectives]<br />
*[http://skycoach.be/2011/05/16/agile-retrospectives-anti-patterns/ Agile Retrospective Anti Patterns]<br />
*[https://www.scrumalliance.org/community/articles/2014/july/dos-and-don-ts-of-agile-retrospectives Do's and Don'ts of Agile Retrospectives]<br />
*[http://www.benlinders.com/2014/retrospectives-in-remote-teams/ Retrospectives in Remote Teams]<br />
*[https://www.mountaingoatsoftware.com/blog/does-a-scrum-team-need-a-retrospective-every-sprint#comments Does a Scrum Team Need a Retrospective Every Sprint?]<br />
*[http://www.benlinders.com/2016/doing-a-retrospective-when-you-cant-get-the-team-to-meet/ Doing a retrospective when you can’t get the team to meet]<br />
*[http://mwickman.com/how-to-fix-your-agile-scrum-retrospective-meetings/ How to Fix Your Agile Scrum Retrospective Meetings]<br />
*[https://medium.com/@benlinders/non-verbal-exercises-for-agile-retrospectives-ade5ca32ade#.bp42lqn9e Non-verbal Exercises for Agile Retrospectives]<br />
<br />
'''Video and Presentations'''<br />
*[http://www.tvagile.com/2010/08/30/retrospectives/ Video: Retrospectives Presentation at San Francisco Agile User Group]<br />
*[http://www.tvagile.com/2009/02/25/agile-retrospectives-making-good-teams-great/ Video: Agile Retrospectives - Making Good Teams Great!]<br />
*[http://www.slideshare.net/BenLinders/sustainable-improvement-through-retrospectives-sepg-europe-2013-ben-linders Sustainable Improvement through Retrospectives]<br />
*[http://www.slideshare.net/jchyip/a-guide-forpreparingandfacilitatingretrospectives A guide for Preparing and Facilitating Retrospectives]<br />
*[https://www.infoq.com/presentations/agile-retrospectives Spicing up Agile Retrospectives] [https://www.slideshare.net/BenLinders/spicing-up-agile-retrospectives-agile-tour-london-2015-ben-linders slides]<br />
*[https://www.slideshare.net/BenLinders/talk-improving-software-quality-with-retrospectives-testcon-moscow-2019-ben-linders Improving software quality with retrospectives]<br />
<br />
'''Online Training'''<br />
*[http://mwickman.com/effective-agile-meetings/ Effective Agile Retrospectives] by Martin Wickman<br />
*[https://www.benlinders.com/workshop-valuable-agile-retrospectives/ Valuable Agile Retrospectives for Teams] by Ben Linders</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Common_ailments_%26_cures&diff=1161Common ailments & cures2022-03-09T14:08:57Z<p>Robbowley: </p>
<hr />
<div>A collection of common problems which occur with retrospectives and suggestions how to resolve them. Generated by running a [[Retrospective Surgery]].<br />
<br />
If you have an ailment that is not covered please add it at the bottom and hopefully someone will have an answer for you.<br />
<br />
----<br />
<br />
'''Ailment: Actions not captured / No obvious record or review of previous retrospective findings'''<br />
<br />
'''Cures:'''<br />
<br />
*Review the actions from the previous retrospectives at the beginning of each retrospective.<br />
*Capture/Document actions & follow up by Scrum Master<br />
*Maintain backlog and have it visible for everybody in the team (e.g. on the Task Board)<br />
*Focus on last sprint only<br />
*Make someone responsible and accountable for each action.<br />
*Put the actions somewhere visible in the team space for example to create team building spirit<br />
*Recognize and deal with [https://www.benlinders.com/2018/retrospective-smells-recurring-actions/ recurring actions]<br />
*Reduce actions to a manageable number<br />
*More suggestions in [http://www.infoq.com/news/2014/02/retrospective-actions-done Having Actions Done from Retrospectives]<br />
<br />
----<br />
'''Ailment: Too many actions'''<br />
<br />
'''Cures:'''<br />
*Apply velocity to actions, track progress and only take on what velocity dictates<br />
*Try [[Plan of Action]] Retrospective Plan<br />
*Focus on the [https://www.benlinders.com/2014/retrospective-exercise-vital-few-actions/ vital few actions], only choose one action<br />
<br />
----<br />
'''Ailment: Unjustified actions'''<br />
<br />
'''Cures:'''<br />
*Use [https://www.benlinders.com/2013/getting-to-the-root-causes-of-problems-in-a-retrospective/ root cause analysis]<br />
*Ensure actions are suggestions from the team and prioritised by them.<br />
*Suggests Biased chair - see cures for that symptom<br />
<br />
----<br />
'''Ailment: Not having the right people in the retrospective'''<br />
<br />
'''Cures:'''<br />
*Invite people early<br />
*Pick a time that suits everyone<br />
*Have separate retrospectives for tech team & wider team<br />
<br />
----<br />
'''Ailment: Biased chair / Agenda hijacking'''<br />
<br />
'''Cures:'''<br />
*Feedback to chair and escalate if necessary<br />
*Rotate chair<br />
*Coach chair on “Agile” principles<br />
*Let team choose an un-biased chair<br />
*Recognize and deal with [https://www.benlinders.com/2018/retrospective-smells-blaming/ blaming]<br />
<br />
----<br />
'''Ailment: Lack of preparation / Forgetting what’s happened'''<br />
<br />
'''Cures:'''<br />
*Compensate in the meeting by having a good time line (Ed. help everyone remember what happened?)<br />
*Prepare - personal/team log<br />
*Remind participants to think of good and bad points<br />
*Reminder before the meeting<br />
*Use Retrospective Exercises from [https://www.benlinders.com/exercises/ Retrospective Exercises Toolbox] or [http://www.plans-for-retrospectives.com/ Retr-O-Mat]<br />
<br />
----<br />
'''Ailment: People not speaking up/shy'''<br />
<br />
'''Cures:'''<br />
*Chair/facilitator needs to create the right environment<br />
*Suggest box/amnesty<br />
*Try different games which are more suited to retiring types<br />
*Start the retrospective with a [https://www.benlinders.com/2016/warm-up-exercises-for-agile-retrospectives/ warm-up exercise] to create an atmosphere where team members can be open and honest about what has happened<br />
<br />
----<br />
'''Ailment: Retrospective actions and tips not shared with other teams'''<br />
<br />
'''Cures:'''<br />
*Rotating facilitators<br />
*Shared retrospective blog<br />
*Retrospective “lurking”<br />
*Cross team collaboration needed<br />
*Do a [http://www.benlinders.com/2013/improving-collaboration-in-agile-projects-with-the-retrospective-of-retrospectives/ Retrospective of Retrospectives]<br />
<br />
<br />
----<br />
'''Ailment: People taking things personally'''<br />
<br />
'''Cures:'''<br />
*Refer to [[The Prime Directive]]<br />
<br />
----<br />
'''Ailment: Voting system may result in valid issues not being addressed'''<br />
<br />
'''Cures:'''<br />
*Non-addressed issues get rolled over (& keep votes?)<br />
*Themed retrospectives<br />
*Encourage team to get on well so they empathise more with issues affecting minority<br />
*Vary the retro format (e.g. no voting)<br />
<br />
----<br />
'''Ailment: Suffering from 'Group Think''''<br />
<br />
'''Cures:'''<br />
*Have a [https://www.benlinders.com/2011/devils-or-angels-advocate-which-role-do-you-prefer/ Devil's Advocate or Angel's Advocate]<br />
*Try De Bono's [[6 Thinking Hats Retrospective]]<br />
*Recognize and deal with [https://www.benlinders.com/2018/retrospective-smell-passiveness/ passiveness]<br />
<br />
----<br />
'''Ailment: Lack of engagement'''<br />
<br />
'''Cures:'''<br />
*Try new plans or tips such as the ones on this wiki!<br />
<br />
----<br />
'''Ailment: Too much focus on negatives'''<br />
<br />
'''Cures:'''<br />
* Try the [[Appreciative Retrospective]] Plan or a [https://www.benlinders.com/2013/using-solution-focused-in-a-strengths-based-retrospective/ Strenghts based Retrospective]<br />
<br />
----</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Retrospective_Plans&diff=1160Retrospective Plans2022-03-09T14:03:06Z<p>Robbowley: </p>
<hr />
<div>A collection of detailed retrospective plans you can run or take inspiration from. If you've been in or ran a retrospective you really liked please add it. <br />
<br />
If you have a plan you'd like to add, [[Retrospective plan template | please read this first]]. <br />
<br />
'''If you are not the originating author of the retrospective please ensure you have permission to reproduce it and credit them as the source.'''<br />
<br />
{| class="wikitable"<br />
! align="left"| Name<br />
!Summary<br />
!Use<br />
!Approx. Duration (mins)<br />
|-<br />
|'''[[6 Thinking Hats Retrospective]]'''<br />
|Uses De Bono's 6 Thinking Hats to investigate process improvement<br />
|Quite a different approach intended to provoke different ways of thinking. A good alternative to the usual post-it note/card type retrospectives<br />
|60<br />
|-<br />
|'''[[Pillars Of Agile Spiderweb Retrospective]]'''<br />
|A retrospective in which teams rated their abilities in each of the categories, displayed the different ratings on a spider graph, and then discussed the result.<br />
|To talk about what abilities are important to an Agile team and how your team rates against them<br />
|60<br />
|-<br />
|'''[[Appreciative Retrospective]]'''<br />
|Uses Appreciative Inquiry to identify what went so well. There is no blame or negativity, and builds on the Prime Directive, that everyone in the team did the best job they could possibly do.<br />
|To remind everyone what a good job their doing rather than focusing on negatives every time you run a retrospective.<br />
|60<br />
|-<br />
|'''[[Strengths-Based Retrospective]]'''<br />
|A strength-based retrospective consists of two steps: discovering strengths, then defining actions that use them.<br />
|Come up with actions that result in doing more of the things that you are already doing and which you are good at.<br />
|45-90<br />
|-<br />
|'''[[Top 5]]'''<br />
|Participants choose top 5 issues and bring them along for group to discuss and resolve<br />
|Expose the most pressing issues in an initially anonymous manner and determine the most effective actions to resolve them<br />
|45<br />
|-<br />
|'''[[Plan of Action]]'''<br />
|A Retrospective Technique for short term actions from long term goals<br />
|Really good for forcing achievable actions from your retrospectives.<br />
|40<br />
|-<br />
|'''[[Start, Stop, Continue, More of, Less of Wheel]]'''<br />
|The facilitator captures team open-ended feedback using a wheel that encourages team members to assess an iteration or milestone using 5 categories. Allow some time following completing the “wheel” to discuss and agree on specific changes to implement<br />
|Obtain feedback on team process in order to learn what should be continued and what should be adjusted as the team moves forward. Is a fast way to conduct a “meta” process discussion.<br />
|10-25<br />
|-<br />
|'''[[Each One Meets All]]'''<br />
|The method ensures that each participant meets and interacts with every other participant.<br />
|When retrospective participants do not know each other well<br />
|Variable!<br />
|-<br />
|'''[[The Complexity Retrospective]]'''<br />
|Use various tools such as a complexity radar to discover and find out how to deal with the complexity in your project<br />
|Many projects go awry due to excessive complexity; use this plan to evaluate whether your team is approaching things in the simplest way that can work; especially when the deadlines begin to loom.<br />
|40-60<br />
|-<br />
|'''[[Force Field Analysis]]'''<br />
|A plan designed around the force field analysis technique<br />
|A retrospective for your whole company/department or to analyse a particular topic<br />
|60<br />
|-<br />
|'''[[Pomodoro Retrospective]]'''<br />
|Focused and time-constrained by using the Pomodoro technique<br />
|Useful for determining a single action to improve the work of a small team<br />
|25<br />
|-<br />
|'''[[Retrospective Surgery]]'''<br />
|A retrospective for retrospectives<br />
|To learn how to improve the effectiveness of your retrospectives<br />
|60+<br />
|-<br />
|'''[[Questions Retrospective]]'''<br />
|Iteration retrospective<br />
|To get different perspectives on the same events<br />
|60<br />
|-<br />
|'''[[Everyday Retrospective]]'''<br />
|Simple sprint retrospective<br />
|Basic / everyday retrospective plan<br />
|90 - 120<br />
|-<br />
|'''[[Four L's Retrospective]]'''<br />
|Liked – Learned – Lacked – Longed For<br />
|Iteration and project retrospectives as well as for retrospection of training and conference events.<br />
|90 - 120<br />
|-<br />
|'''[[Sailboat]]'''<br />
|What anchors slow the team down, what wind propels it forward?<br />
|Good for the "gather data" and "generate insights" portions of a retrospective<br />
|90 - 120<br />
|-<br />
|'''[[Weekly Retrospective Simple + delta]]'''<br />
|Review, Plus-Delta, Vote, Actions, Owners<br />
|A weekly retrospective for your project<br />
|60<br />
|-<br />
|'''[[Jeopardy Retrospective]]'''<br />
|Use the answers as base to get all the good things and bad things that happened<br />
|A different way to "gather data" and to get all different opinions on a subject<br />
|60<br />
|-<br />
|'''[[Bubble Up]]'''<br />
|An approach to scaling retrospectives by collecting outcomes across an Agile Release Train, Tribe or any multi team scenario.<br />
|Use for understanding challenges and opportunities across teams when scaling agile.<br />
|15-30<br />
|-<br />
|'''[[Tiny Retrospective]]'''<br />
|A look at some of the smaller changes that the team could make.<br />
|Use to get the team to focus on the really small things that can sometimes make a big difference.<br />
|60<br />
|-<br />
|'''[[An Agile Christmas Carol]]'''<br />
|A light weight Christmas themed retrospective inspired by Dickens' A Christmas Carol<br />
|An approach to reflecting on the year that was and making wishes for the year ahead.<br />
|60<br />
|-<br />
|'''[[Deep Tissue Massage Retrospective]]'''<br />
|Massage out your team's sore knots: Tackle those common themes that come up again and again.<br />
|Targeted retrospective to tackle some of those lingering issues<br />
|60<br />
|-<br />
|'''[[Glad, Sad, Mad]]'''<br />
|Categorize issues as those that made you glad, sad or mad.<br />
|A fairly basic, “no gimmicks” retrospective plan.<br />
|60<br />
|-<br />
|'''[[Do-Si-Do]]'''<br />
|Team members move from station to station like an old fashioned dance.<br />
|An approach that allows team members to focus on actions.<br />
|60-90<br />
|-<br />
|'''[[A Serious (Play) Retro]]'''<br />
|A retrospective in which the team builds Lego models to assess their performance.<br />
|To create a playful mindset from which to more honestly self-evaluate.<br />
|60<br />
|-<br />
|'''[[Guess Who?]]'''<br />
|An 'empathy hack' retro designed for team members to see others' points of view.<br />
|When you're looking to build team cohesion. <br />
|60<br />
|-<br />
|'''[[Scrum Values]]'''<br />
|A look from two angles on how the team evaluates their adherence to the Scrum Values.<br />
|To get a common understanding of the Scrum Values, evaluate how the team adheres to them and dig deeper in the context of transparency, inspection and adaptation.<br />
|60<br />
|-<br />
|'''[[Facebook Reactions Retrospective]]'''<br />
|A simple and refreshing variation of the very popular "Glad", "Sad", "Mad" retrospective.<br />
|Instead of the original three "Glad", "Sad", "Mad" columns the team uses the following six: "Liked", "Loved", "Made me laugh", "Surprised me", "Made me sad", "Made me angry" inspired by the reactions feature used on Facebook.<br />
|60-120<br />
|-<br />
|'''[[2 fast 2 valuable]]'''<br />
|A way for a team to talk about how their ways of working impact how effective they are<br />
|Useful when a team is newly formed or have different ways of working (for example if they don't pair program)<br />
|60-120<br />
|-<br />
|'''[[Mountain Hiking]]'''<br />
|A way for a team to talk about goals, risks, impediments in the sprint.<br />
|Useful when a team is not sure of team goal, and would like them to think about the risks and impediments.<br />
|60-120<br />
|-<br />
|'''[[Fly High]]'''<br />
|A way for a team to talk about team level and organizational level impediments.<br />
|Useful when a team is not sure of what impediments the teams can resolve by themselves and what cannot.<br />
|60<br />
|-<br />
|'''[[Highway Drive]]'''<br />
|A way for a team to talk about team goals, risks, impediments and enablers during their sprints.<br />
|Useful for understanding the team's thoughts and ideas in terms of small and big blockers, enablers .<br />
|60<br />
|-<br />
|'''[[Snakes and Ladders]]'''<br />
|A way for a team to talk about impediments and enablers during their sprints.<br />
|Useful for understanding the team's thoughts on what is helping them during the sprint and what is not, and also talk about the action items .<br />
|60<br />
|-<br />
|'''[[Basket Ball]]'''<br />
|A way for a team to discuss how can they work as an agile team.<br />
|Useful for brainstorming what it takes for team members working in silos to start working as an agile team.<br />
|60<br />
|-<br />
|'''[[A-Team]]'''<br />
|A way for a team to discuss goals, achievements, particularities and team work.<br />
|Useful as an alternative to a basic retrospective.<br />
|60<br />
|-<br />
|'''[[Our Empathy Survey Says – Awesome Retro]]'''<br />
|A fun gameshow-style format, guessing what others have answered.<br />
|Designed to create the circumstances for empathy to grow within the team in a fun way whilst also generating improvement ideas.<br />
|30-60<br />
|-</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1159Rob's Guide to Effective Retrospectives2022-03-09T13:59:13Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring meetings are not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional retrospectives which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working:<br />
<br />
'''''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It's common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn't) mean they have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour. This has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the work in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1158Rob's Guide to Effective Retrospectives2022-03-09T13:54:22Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring meetings are not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional retrospectives which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working:<br />
<br />
'''''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn't) mean they have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour. This has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the work in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1157Agile Retrospective Resource Wiki2022-03-09T13:01:51Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
=Welcome!=<br />
<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in software teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects." - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will have to [[Special:RequestAccount| request an account]] to do so, which will have to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools]]====<br />
Smaller exercises which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
Currently a random collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
====[[Rob's guide to effective retrospectives]]====<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki was set up and is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or thoughts on how to improve the wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki&diff=1156Agile Retrospective Resource Wiki2022-03-09T13:01:24Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
=Welcome!=<br />
<br />
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.<br />
Retrospectives play a crucial role in software teams. It is time specifically put aside to reflect on how the team is performing and what can be done to improve.<br />
<br />
"[...] a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects." - [http://en.wikipedia.org/wiki/Retrospective#Software_development Wikipedia]<br />
<br />
The process of retrospecting is at the heart of Scrum (Inspect and Adapt), eXtreme Programming (fix it when it breaks) and Lean Software Development (Kaizen or Continuous Improvement)<br />
<br />
==Contribute==<br />
If you've come up with a [[Retrospective Plans| retrospective]] you think worked really well and is worth sharing, or have [[Tools]] or [[Tips & tricks | Tips & Tricks]] please share them here. You will have to [[Special:RequestAccount| request an account]] to do so, which will have to be approved by the administrator ([http://twitter.com/@robbowley @robbowley]). Sorry for the bureaucracy but the wiki gets hammered by spam bots!<br />
<br />
==Sections==<br />
<br />
====[[Retrospective Plans]]====<br />
<br />
A constantly evolving list of retrospective plans you could try for either specific situations or to simply mix things up to stop them going stale.<br />
<br />
====[[Tools]]====<br />
Smaller exercises which can be used on their own or as part of larger sessions. Examples of use may be to break the ice, gauge the temperature or remind people of significant events.<br />
<br />
====[[Tips_%26_tricks | Tips & Tricks]]====<br />
Currently a random collection of quick tips to ensure you're getting the most from your retrospectives<br />
<br />
====[[Common_ailments_%26_cures | Common Ailments & Cures]]====<br />
A list of common problems that have occurred with retrospectives and suggestions on how to deal with them.<br />
<br />
===[[Rob's guide to effective retrospectives]]===<br />
The wiki maintainer's personal guide to running effective retrospectives<br />
<br />
====[[Retrospective Surgery]]====<br />
A "retrospective for retrospectives". Used to gather a lot of the original content on this site.<br />
<br />
====[[External Resources]]====<br />
Links to other places you can find out about retrospectives.<br />
<br />
====Contact====<br />
This wiki was set up and is maintained by [https://twitter.com/@robbowley Rob Bowley]. Please get in touch if you have any questions or thoughts on how to improve the wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1155Rob's Guide to Effective Retrospectives2022-03-09T12:54:26Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring meetings are not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional retrospectives which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working:<br />
<br />
'''''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn't) mean they have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the work in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1154Rob's Guide to Effective Retrospectives2022-03-09T12:54:00Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring meetings are not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional retrospectives which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working:<br />
<br />
''''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."''''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn't) mean they have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the work in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1153Rob's Guide to Effective Retrospectives2022-03-09T12:53:16Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring meetings are not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional retrospectives which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working:<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn't) mean they have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the work in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1152Rob's Guide to Effective Retrospectives2022-03-09T12:46:04Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring meetings are not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional retrospectives which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working:<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the work in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1151Rob's Guide to Effective Retrospectives2022-03-09T12:44:57Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring meetings are not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional retrospectives which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working:<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1150Rob's Guide to Effective Retrospectives2022-03-09T12:41:32Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring meetings are not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional transactional retrospectives which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working:<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1149Rob's Guide to Effective Retrospectives2022-03-09T12:39:50Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working:<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1148Rob's Guide to Effective Retrospectives2022-03-09T12:37:01Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]:<br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br/><br />
A place with tension, difficulty and honest searching for a better way.<br/><br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br/><br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1147Rob's Guide to Effective Retrospectives2022-03-09T12:35:48Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
''"Retrospectives should be where people truly critique the status quo. <br />
A place with tension, difficulty and honest searching for a better way. <br />
Where people make themselves vulnerable and do the hard work of forging agreement. <br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Begin the retrospective by reviewing the actions from the previous retrospective. Have the been completed? If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then consider increasing the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1146Rob's Guide to Effective Retrospectives2022-03-09T12:33:25Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice.<br />
<br />
Conversely - and something more common with the increase in remote working and online meetings - is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
''"Retrospectives should be where people truly critique the status quo. <br />
A place with tension, difficulty and honest searching for a better way. <br />
Where people make themselves vulnerable and do the hard work of forging agreement. <br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Before doing anything else, begin the retrospective by going through the actions from the previous retrospective have been completed. If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then maybe they can increase the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1145Rob's Guide to Effective Retrospectives2022-03-09T12:33:00Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice. Conversely - and something more common with the increase in remote working and online meetings - is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
''"Retrospectives should be where people truly critique the status quo. <br />
A place with tension, difficulty and honest searching for a better way. <br />
Where people make themselves vulnerable and do the hard work of forging agreement. <br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Before doing anything else, begin the retrospective by going through the actions from the previous retrospective have been completed. If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then maybe they can increase the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1144Rob's Guide to Effective Retrospectives2022-03-09T12:31:45Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice. Conversely - and something more common with the increase in remote working and online meetings - is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br />
A place with tension, difficulty and honest searching for a better way.<br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Before doing anything else, begin the retrospective by going through the actions from the previous retrospective have been completed. If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then maybe they can increase the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1143Rob's Guide to Effective Retrospectives2022-03-09T12:31:30Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice. Conversely - and something more common with the increase in remote working and online meetings - is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br />
<br />
A place with tension, difficulty and honest searching for a better way.<br />
<br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br />
<br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Before doing anything else, begin the retrospective by going through the actions from the previous retrospective have been completed. If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then maybe they can increase the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1142Rob's Guide to Effective Retrospectives2022-03-09T12:31:06Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice. <br />
<br />
Conversely - and something more common with remote working and online meetings - is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br />
<br />
A place with tension, difficulty and honest searching for a better way.<br />
<br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br />
<br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Before doing anything else, begin the retrospective by going through the actions from the previous retrospective have been completed. If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then maybe they can increase the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1141Rob's Guide to Effective Retrospectives2022-03-09T12:30:51Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading for how to effectively facilitate retrospectives.<br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice. <br />
<br />
Conversely - and something more common with remote working and online meetings - is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br />
<br />
A place with tension, difficulty and honest searching for a better way.<br />
<br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br />
<br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Before doing anything else, begin the retrospective by going through the actions from the previous retrospective have been completed. If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then maybe they can increase the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1140Rob's Guide to Effective Retrospectives2022-03-09T12:30:09Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice. <br />
<br />
Conversely - and something more common with remote working and online meetings - is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br />
<br />
A place with tension, difficulty and honest searching for a better way.<br />
<br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br />
<br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading. <br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Before doing anything else, begin the retrospective by going through the actions from the previous retrospective have been completed. If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then maybe they can increase the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1139Rob's Guide to Effective Retrospectives2022-03-09T12:29:44Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice. <br />
<br />
Conversely, and something more common with remote working and online meetings is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br />
<br />
A place with tension, difficulty and honest searching for a better way.<br />
<br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br />
<br />
With these kinds of retros, things actually change."'' - [https://twitter.com/chrismdp/status/1493155573965090818?s=20&t=UagX05G8gwHBwSBrI1hdbA Chris Parsons]<br />
<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading. <br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Before doing anything else, begin the retrospective by going through the actions from the previous retrospective have been completed. If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then maybe they can increase the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1138Rob's Guide to Effective Retrospectives2022-03-09T12:28:34Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading. <br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice. <br />
<br />
Conversely, and something more common with remote working and online meetings is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
''"Retrospectives should be where people truly critique the status quo.<br />
<br />
A place with tension, difficulty and honest searching for a better way.<br />
<br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br />
<br />
With these kinds of retros, things actually change."''<br />
<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Before doing anything else, begin the retrospective by going through the actions from the previous retrospective have been completed. If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then maybe they can increase the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowleyhttps://retrospectivewiki.org/index.php?title=Rob%27s_Guide_to_Effective_Retrospectives&diff=1137Rob's Guide to Effective Retrospectives2022-03-09T12:28:14Z<p>Robbowley: </p>
<hr />
<div>__NOTOC__<br />
===Retrospective facilitation is a skill===<br />
The first three chapters of Derby and Larson's book [http://pragprog.com/book/dlret/agile-retrospectives Agile Retrospectives: Making good Teams Great] remain essential reading. <br />
<br />
Ensuring the meeting is not being driven by whoever shouts the loudest or ending up as a long ineffectual debate takes thought and practice. <br />
<br />
Conversely, and something more common with remote working and online meetings is highly transactional transactional meetings which are no more than [https://twitter.com/chrismdp/status/1493155571154833413?s=20&t=UagX05G8gwHBwSBrI1hdbA Improvement Theatre]. <br />
<br />
'"Retrospectives should be where people truly critique the status quo.<br />
<br />
A place with tension, difficulty and honest searching for a better way.<br />
<br />
Where people make themselves vulnerable and do the hard work of forging agreement.<br />
<br />
With these kinds of retros, things actually change."'<br />
<br />
<br />
===Start each retrospective with [[The Prime Directive]]===<br />
The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working.<br />
<br />
'''"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."'''<br />
<br />
--Norm Kerth, Project Retrospectives: A Handbook for Team Review<br />
<br />
===Rotate the facilitator role===<br />
It is common for it to be one person's job (e.g. Scrum Master, Team Lead) to facilitate/lead retrospectives. This can result in bias towards their point of view and prevent a team from feeling engaged and empowered to solve their own problems. Whilst it may be one person's job to make sure they happen, that doesn't (and shouldn'tt) mean they also have to run every retrospective too.<br />
<br />
Get everyone to take turns facilitating. Not only does this ensure no one feels retrospectives are being driven by one person's agenda, there are many other side benefits, including:<br />
* Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.<br />
* The burden of planning retrospectives is shared across multiple people.<br />
* Retrospectives are less likely to become dull or repetitive.<br />
<br />
Really easy to do if you have more than one team - '''ask for someone from another team to facilitate your retrospective''' and when it's their turn return the favour and has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.<br />
<br />
===Achievable actions and owners for each action===<br />
A common failing with retrospectives is either not taking actions away or the actions not being completed. My first tip here is make your actions small, really small. Big vague goals like "write more unit tests" are pointless. A great retrospective to encourage small achievable actions is the [[Plan of Action]] retrospective.<br />
<br />
Once you have your achievable actions make sure someone is responsible for each and every one you choose to take away. This doesn't have to be the person who is going to do the work, just the person who is responsible for making sure it happens before the next retrospective.<br />
<br />
Track the actions as you would with the rest of the activity in your team in your favourite work tracking tool<br />
<br />
===Start each retrospective by going through the actions from the previous one===<br />
Before doing anything else, begin the retrospective by going through the actions from the previous retrospective have been completed. If not, why not? Time box this to 5 minutes.<br />
<br />
If the team took 5 actions but completed none, agree to take fewer actions away from this retrospective. Once the team has got better at completing the actions they've committed to then maybe they can increase the amount of actions they take away.<br />
<br />
<br />
====Who is Rob?====<br />
I'm [https://twitter.com/@robbowley Rob Bowley], the person who set up this wiki.</div>Robbowley