<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>roles on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/roles/</link>
    <description>Recent content in roles 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/roles/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How AI Has Shifted the Leverage Points in Engineering Teams</title>
      <link>https://agilesoftdev.com/how-ai-has-shifted-the-leverage-points-in-engineering-teams/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/how-ai-has-shifted-the-leverage-points-in-engineering-teams/</guid>
      <description>Engineering team composition has historically been organized around the constraint that writing code is slow and skilled developers are scarce. Ratios of developers to product managers, to QA engineers, to designers, to technical writers — all of these reflect an underlying assumption about where the production bottleneck sits. When that bottleneck moves, the ratios that were optimized for the old constraint become wrong.
AI-assisted development has moved the bottleneck. For teams working effectively with generation tools, the constraint is no longer coding throughput.</description>
    </item>
    
  </channel>
</rss>
