<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>engineering on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/engineering/</link>
    <description>Recent content in engineering 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/engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Technical Debt Belongs in the Backlog, Not in Side Conversations</title>
      <link>https://agilesoftdev.com/technical-debt-belongs-in-the-backlog-not-in-side-conversations/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/technical-debt-belongs-in-the-backlog-not-in-side-conversations/</guid>
      <description>Technical debt in most agile teams exists in two places: in the codebase, where it slows down every sprint without appearing in any sprint report, and in informal conversations between developers, where it is acknowledged but never prioritized. This arrangement persists because engineers are reluctant to burden the product owner with implementation concerns, and product owners are reluctant to prioritize work that has no visible user-facing outcome. The debt accumulates. The sprints slow down.</description>
    </item>
    
  </channel>
</rss>
