<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Retrospectives on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/retrospectives/</link>
    <description>Recent content in Retrospectives on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 22 Dec 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/retrospectives/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Running Effective Retrospectives (and Actually Following Up)</title>
      <link>https://www.secdev.uk/blog/leadership/3.7-running-effective-retrospectives/</link>
      <pubDate>Mon, 22 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/3.7-running-effective-retrospectives/</guid>
      <description>&lt;p&gt;Retrospectives should be the engine of continuous improvement. In practice, they&amp;rsquo;re often the meeting everyone tolerates but nobody values, a ritual performed out of obligation rather than conviction, producing sticky notes that get photographed and forgotten.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve run hundreds of retrospectives over the years, and I&amp;rsquo;ve wasted more of them than I&amp;rsquo;d like to admit. The ones that worked had a few things in common. The ones that didn&amp;rsquo;t were all failing in the same ways.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
