<?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 Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/retrospectives/</link>
    <description>Recent content in retrospectives on Agile Software Development</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agilesoftdev.com/tags/retrospectives/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Retrospectives That Change Nothing Are Worse Than No Retrospective</title>
      <link>https://agilesoftdev.com/retrospectives-that-change-nothing-are-worse-than-no-retrospective/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/retrospectives-that-change-nothing-are-worse-than-no-retrospective/</guid>
      <description>The retrospective is the most important ceremony in the sprint cycle and the one most commonly reduced to ritual. Teams go through the motions — what went well, what didn&amp;rsquo;t, what to improve — produce a list of action items, and proceed to the next sprint having changed nothing. The list sits in a document somewhere. The problems repeat.
This failure mode is so common that many experienced practitioners have concluded retrospectives do not work.</description>
    </item>
    
  </channel>
</rss>
