<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Sprint Review on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/sprint-review/</link>
		<description>Recent content in Sprint Review on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 17 Sep 2024 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership.hinshelwood.com/tags/sprint-review/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The fallacy of the rejected backlog item</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</link>
				<pubDate>Mon, 13 Jul 2020 08:55:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/</guid>
				<description>Rejecting individual backlog items at the Sprint Review is a misunderstanding, since the increment is delivered as a whole and removing a single item is complex and risky. The Sprint Review is for feedback and learning, not for accepting or rejecting specific items, and any gaps should inform future backlog updates. Development managers should focus on clear communication, well-structured backlog items, and using feature flags to provide flexibility and faster feedback.</description>
			</item>
			<item>
				<title>Sprint Review #1</title>
				<link>https://engineering-leadership.hinshelwood.com/workshops/sprint-review-1/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/workshops/sprint-review-1/</guid>
				<description>Guides a 160-minute Sprint Review workshop using Liberating Structures to inspect product progress, gather feedback, and plan next steps for Scrum teams and stakeholders.</description>
			</item>
			<item>
				<title>What is the Sprint Review workshop and how will it help organisations?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/</link>
				<pubDate>Fri, 30 Jun 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/</guid>
				<description>The Sprint Review workshop helps teams align product development with stakeholder needs, adapt to market changes, and drive continuous improvement. It offers practical guidance on running effective reviews, boosting stakeholder engagement, and turning feedback into actionable improvements. Development managers should consider this workshop to enhance team performance and ensure products deliver real value.</description>
			</item>
			<item>
				<title>Sprint Review Recipe</title>
				<link>https://engineering-leadership.hinshelwood.com/recipes/sprint-review-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/recipes/sprint-review-recipe/</guid>
				<description>Step-by-step guide for running a Sprint Review, including presenting the increment, gathering feedback, updating the backlog, forecasting, and addressing stakeholder questions.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile apocalypse - Silence</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/</link>
				<pubDate>Mon, 23 Oct 2023 11:00:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/</guid>
				<description>Silence during agile sprint reviews signals deeper issues like lack of engagement, unclear goals, and poor product ownership, which can derail team effectiveness. To address this, focus on building trust, communicating clear objectives, and actively involving all stakeholders through inclusive practices and open discussions. Development managers should ensure product owners foster transparency and engagement to transform passive meetings into collaborative, value-driven sessions.</description>
			</item>
			<item>
				<title>What should you do if your Sprint Review delivers harsh, scathing feedback?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/</link>
				<pubDate>Fri, 08 Sep 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/</guid>
				<description>Harsh feedback in Sprint reviews signals a need for immediate attention and should be seen as an opportunity to realign with stakeholder needs. Investigate the root causes, engage stakeholders more effectively, and be ready to halt, pivot, or persevere based on what you learn. Use open communication and flexibility to turn negative feedback into actionable improvements for your product and process.</description>
			</item>
			<item>
				<title>Who Should Lead the Sprint Review? Unpacking the Role of the Product Owner in Agile Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</link>
				<pubDate>Wed, 06 Sep 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</guid>
				<description>The Product Owner should lead the Sprint Review because they are accountable for maximising value and are best positioned to gather insights from stakeholders. The review should focus on aligning everyone on the product vision, showcasing progress, encouraging feedback, and updating the product backlog with new information. Development managers should ensure the Product Owner leads this process and experiment with review formats to keep the backlog relevant and guide the team&amp;rsquo;s next steps.</description>
			</item>
			<item>
				<title>Transforming Sprint Reviews: How to Engage Stakeholders and Secure Meaningful Feedback</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-sprint-reviews-how-to-engage-stakeholders-and-secure-meaningful-feedback/</link>
				<pubDate>Fri, 15 Dec 2023 11:00:17 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-sprint-reviews-how-to-engage-stakeholders-and-secure-meaningful-feedback/</guid>
				<description>Sprint reviews often fail to engage stakeholders or generate useful feedback because stakeholders do not see the value or feel emotionally connected to the work. To address this, communicate the benefits of participation early, use visuals, create a safe space for feedback, engage stakeholders before reviews, and tailor your approach to their interests. Development managers should focus on making Sprint reviews relevant and personal to stakeholders to drive better engagement and product outcomes.</description>
			</item>
			<item>
				<title>Worst Contribution from a Product Owner that You Know Of</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/worst-contribution-from-a-product-owner-that-you-know-of/</link>
				<pubDate>Tue, 06 Jun 2023 11:00:34 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/worst-contribution-from-a-product-owner-that-you-know-of/</guid>
				<description>A product owner publicly blamed the development team during a sprint review instead of supporting them when stakeholders questioned product decisions, undermining trust and collaboration. Product owners should balance accountability to stakeholders with support for their teams, especially under pressure. Development managers should ensure product owners are prepared to defend team decisions and foster a collaborative environment.</description>
			</item>
			<item>
				<title>What should be top of mind when a Scrum team prepare for a Sprint review?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/</link>
				<pubDate>Mon, 04 Sep 2023 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/</guid>
				<description>To get the most out of Sprint reviews, focus on engaging stakeholders by understanding their priorities, communicating value in clear and relevant terms, and encouraging active participation. Regular check-ins, feedback loops, and making information accessible to all stakeholders help build stronger relationships and increase involvement. Make Sprint reviews a collaborative opportunity rather than just a technical update to drive better outcomes and transparency.</description>
			</item>
	</channel>
</rss>
