<?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>Enterprise Software on Agile Congruence</title>
    <link>https://agilecongruence.com/tags/enterprise-software/</link>
    <description>Recent content in Enterprise Software on Agile Congruence</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Apr 2025 13:30:54 +0000</lastBuildDate>
    <atom:link href="https://agilecongruence.com/tags/enterprise-software/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Introduction to Agile Congruence</title>
      <link>https://agilecongruence.com/posts/introduction-to-agile-congruence/</link>
      <pubDate>Thu, 03 Apr 2025 13:30:54 +0000</pubDate>
      <guid>https://agilecongruence.com/posts/introduction-to-agile-congruence/</guid>
      <description>&lt;p&gt;One of my responsibilities at my former employer was to give an introductory talk about the Technology Team and our SAAS platform to new hires. This is always an interesting experience because of the diverse range of backgrounds in the audience. Accountants, Financial Analysts, Developers, and new graduates among others will all have very different levels of understanding of modern software development processes. After one such Intro to the Technology Team talk a newly hired Product Owner came up to me and said, “That was interesting, I’ve never heard anyone describe Agile Software Development as an Organizational Change process before”. That comment really made me think. Could my conceptual model of the process of building enterprise software help other organizations?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
