<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>distributed teams on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/distributed-teams/</link>
    <description>Recent content in distributed teams 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/distributed-teams/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remote Agile Teams Fail at the Informal Layer, Not the Ceremony Layer</title>
      <link>https://agilesoftdev.com/remote-agile-teams-fail-at-the-informal-layer-not-the-ceremony-layer/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/remote-agile-teams-fail-at-the-informal-layer-not-the-ceremony-layer/</guid>
      <description>When agile teams moved to remote work, the common concern was whether the ceremonies would survive the transition. Would sprint planning work over video? Could retrospectives produce candor without physical presence? Would the daily standup maintain its discipline when the team was distributed across time zones?
These concerns were largely misplaced. The ceremonies adapted. Video-based sprint planning, while less fluid than in-person, functions well enough with the right tools and facilitation.</description>
    </item>
    
  </channel>
</rss>
