<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Whole Team on The Agile Techies Daily List</title>
    <link>https://agiletechies.com/tags/whole-team/</link>
    <description>Recent content in Whole Team on The Agile Techies Daily List</description>
    <image>
      <title>The Agile Techies Daily List</title>
      <url>https://agiletechies.com/images/papermod-cover.png</url>
      <link>https://agiletechies.com/images/papermod-cover.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-US</language>
    <managingEditor>rajesh@duggalmail.com (Raj Duggal)</managingEditor>
    <webMaster>rajesh@duggalmail.com (Raj Duggal)</webMaster>
    <lastBuildDate>Wed, 28 May 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://agiletechies.com/tags/whole-team/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Whole Team in One Space</title>
      <link>https://agiletechies.com/posts/the-whole-team-in-one-space/</link>
      <pubDate>Wed, 28 May 2025 00:00:00 +0000</pubDate><author>rajesh@duggalmail.com (Raj Duggal)</author>
      <guid>https://agiletechies.com/posts/the-whole-team-in-one-space/</guid>
      <description>&lt;p&gt;Years ago it was the norm for teams to work together in the same office. In close proximity.  These days, teams work remotely, or partially remote.&lt;/p&gt;
&lt;p&gt;The idea of &amp;ldquo;On‑Site Customer&amp;rdquo; was simple: put the right product owner or customer or end-user in proximity of the builders. Close enough so they could quickly shoot questions/answers and get clarity on things, ad-hoc.&lt;/p&gt;
&lt;p&gt;This resulted in questions getting answered in seconds, and potential misunderstandings caught early.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
