<?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>Software Engineering on Sajna Space</title>
    <link>https://sajna.space/tags/software-engineering/</link>
    <description>Recent content in Software Engineering on Sajna Space</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 01 Apr 2026 08:00:00 +0200</lastBuildDate>
    <atom:link href="https://sajna.space/tags/software-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Velocity Trap: Why &#39;Features Per Day&#39; Misleads Everyone</title>
      <link>https://sajna.space/posts/velocity-vs-value-the-velocity-trap/</link>
      <pubDate>Wed, 01 Apr 2026 08:00:00 +0200</pubDate>
      <guid>https://sajna.space/posts/velocity-vs-value-the-velocity-trap/</guid>
      <description>Velocity is a planning tool, not a performance target. Here&amp;#39;s what happens when organizations confuse the two — and what to measure instead.</description>
    </item>
    <item>
      <title>Velocity vs Value: How to Measure Success in the Age of AI</title>
      <link>https://sajna.space/posts/velocity-vs-value/</link>
      <pubDate>Tue, 31 Mar 2026 09:00:00 +0200</pubDate>
      <guid>https://sajna.space/posts/velocity-vs-value/</guid>
      <description>Your organization wants velocity and AI adoption. You want to deliver value. Here&amp;#39;s a framework for measuring what actually matters — and promoting your team&amp;#39;s real impact.</description>
    </item>
  </channel>
</rss>
