<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ProjectManagement on emsenn.net</title>
    <link>https://emsenn.net/tags/projectmanagement/</link>
    <description>Recent content in ProjectManagement on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 05 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/projectmanagement/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>technical debt</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/software/domains/programming/terms/technical-debt/</link>
      <pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/software/domains/programming/terms/technical-debt/</guid>
      <description>&lt;p&gt;Technical debt is the accumulated cost of deferred or incomplete work in a software system. The term was introduced by &lt;a href=&#34;../../../../../../../../humanities/domains/general/domains/people/ward-cunningham.md&#34; class=&#34;link-internal&#34;&gt;Ward Cunningham&lt;/a&gt; in 1992 as a metaphor: just as financial debt incurs interest that makes future payments more expensive, shortcuts in software development incur maintenance costs that make future changes harder.&lt;/p&gt;&#xA;&lt;p&gt;Technical debt is not inherently negative. Deliberately incurring debt — choosing a simpler implementation now with a plan to revise later — can be a reasonable trade-off when the cost of delay outweighs the cost of revision. Debt becomes harmful when it is untracked, unacknowledged, or allowed to accumulate without a plan for repayment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
