<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Definition of Done on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/workshops/definition-of-done/</link>
		<description>Recent content in Definition of Done 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-preview.hinshelwood.com/workshops/definition-of-done/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/workshops/definition-of-done/versions/2024/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/workshops/definition-of-done/versions/2024/</guid>
				<description>The Definition of Done (DoD) clarifies when work is truly complete, ensuring shared understanding and consistent quality across the team. Key steps include aligning on what &amp;ldquo;done&amp;rdquo; means, using exercises to explore the concept, and applying it to increments of work. Development managers should ensure their teams have a clear, agreed-upon DoD to improve delivery consistency and product quality.</description>
			</item>
	</channel>
</rss>
