<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>stakeholder engagement on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/stakeholder-engagement/</link>
    <description>Recent content in stakeholder engagement 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/stakeholder-engagement/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Sprint Review Is Not a Demo</title>
      <link>https://agilesoftdev.com/the-sprint-review-is-not-a-demo/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/the-sprint-review-is-not-a-demo/</guid>
      <description>The sprint review is consistently misunderstood as a presentation event. The team demonstrates what was built, stakeholders applaud or raise concerns, and everyone moves on to the retrospective. Run this way, the review produces polished demos and no feedback that the team can act on. It is theater with a product backlog.
The sprint review is a working session. Its purpose is inspection and adaptation at the product level: the team shows what was built, stakeholders engage with it substantively, and the conversation that follows informs the backlog.</description>
    </item>
    
  </channel>
</rss>
