<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Customer Working Agreement on Engineering as a Leadership System</title>
		<link>https://engineering.hinshelwood.com/workshops/customer-working-agreement/</link>
		<description>Recent content in Customer Working Agreement on Engineering as a Leadership System</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 17 Sep 2024 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://engineering.hinshelwood.com/workshops/customer-working-agreement/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Customer Working Agreement</title>
				<link>https://engineering.hinshelwood.com/workshops/customer-working-agreement/versions/2024/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/workshops/customer-working-agreement/versions/2024/</guid>
				<description>A Customer Working Agreement workshop, lasting about 60 minutes, helps both parties define a clear Statement of Work and agree on the level of agility to apply. It ensures customers understand their responsibilities, such as providing a Product Owner, clear goals, and attending Sprint Reviews, while the development team commits to delivering usable increments and a dedicated team. Development managers should use this workshop early to clarify expectations, roles, and trade-offs for successful collaboration.</description>
			</item>
	</channel>
</rss>
