<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>daily standup on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/daily-standup/</link>
    <description>Recent content in daily standup 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/daily-standup/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Daily Standup Has Three Failure Modes and Teams Hit All of Them</title>
      <link>https://agilesoftdev.com/the-daily-standup-has-three-failure-modes-and-teams-hit-all-of-them/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/the-daily-standup-has-three-failure-modes-and-teams-hit-all-of-them/</guid>
      <description>The daily standup is fifteen minutes. It is the shortest ceremony in the sprint cycle and the one with the highest ratio of complaints to duration. Most of the complaints are legitimate, and they cluster around three patterns that are distinct enough to be worth naming separately.
The first is the status report disguised as a standup. Each team member addresses the scrum master or manager rather than the team, describes what they did yesterday and what they will do today, and waits for the next person to do the same.</description>
    </item>
    
  </channel>
</rss>
