<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>fixed price contracts on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/fixed-price-contracts/</link>
    <description>Recent content in fixed price contracts on Agile Software Development</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agilesoftdev.com/tags/fixed-price-contracts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixed Price Software Development: When It Works and When It Blows Up</title>
      <link>https://agilesoftdev.com/fixed-price-software-development-when-it-works-and-when-it-blows-up/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/fixed-price-software-development-when-it-works-and-when-it-blows-up/</guid>
      <description>A client asks for a fixed price. The vendor writes a spec, quotes a number, and both sides sign it feeling like they&amp;rsquo;ve eliminated risk. Six weeks in, the client wants a feature that wasn&amp;rsquo;t in the spec, the vendor calls it a change order, and the relationship that started as a handshake is now a negotiation over what &amp;ldquo;originally scoped&amp;rdquo; meant. That&amp;rsquo;s not a fixed price project gone wrong. That&amp;rsquo;s what most fixed price projects actually look like once real requirements meet a document written before anyone had built anything.</description>
    </item>
    
  </channel>
</rss>
