<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Development is Ready.  What about Production and Support?</title>
	<atom:link href="http://www.implementingscrum.com/2008/02/11/development-is-ready-what-about-production-and-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.implementingscrum.com/2008/02/11/development-is-ready-what-about-production-and-support/</link>
	<description>Starting Tough Conversations about Software Development</description>
	<lastBuildDate>Wed, 18 Jan 2012 21:57:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: mvizdos</title>
		<link>http://www.implementingscrum.com/2008/02/11/development-is-ready-what-about-production-and-support/comment-page-1/#comment-142</link>
		<dc:creator>mvizdos</dc:creator>
		<pubDate>Wed, 13 Feb 2008 04:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.implementingscrum.com/blog/2008/02/11/development-is-ready-what-about-production-and-support/#comment-142</guid>
		<description>Tobias,

A very thought provoking response and question.  

This is one that I struggle with teams -- especially in very large enterprise situations -- because the &quot;production and support&quot; people a lot of time are in their own matrix / functional organization.

I do agree that the team that creates the working software should be responsible for maintaining it in the future.

This can -- and does -- lead to some very interesting team dynamics!

Is it possible to do this?

Of course.

It is easy?

Not always.

What works in your situation?

- mike vizdos
  www.michaelvizdos.com
  www.implementingscrum.com</description>
		<content:encoded><![CDATA[<p>Tobias,</p>
<p>A very thought provoking response and question.  </p>
<p>This is one that I struggle with teams &#8212; especially in very large enterprise situations &#8212; because the &#8220;production and support&#8221; people a lot of time are in their own matrix / functional organization.</p>
<p>I do agree that the team that creates the working software should be responsible for maintaining it in the future.</p>
<p>This can &#8212; and does &#8212; lead to some very interesting team dynamics!</p>
<p>Is it possible to do this?</p>
<p>Of course.</p>
<p>It is easy?</p>
<p>Not always.</p>
<p>What works in your situation?</p>
<p>- mike vizdos<br />
  <a href="http://www.michaelvizdos.com" rel="nofollow">http://www.michaelvizdos.com</a><br />
  <a href="http://www.implementingscrum.com" rel="nofollow">http://www.implementingscrum.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tobiasmayer</title>
		<link>http://www.implementingscrum.com/2008/02/11/development-is-ready-what-about-production-and-support/comment-page-1/#comment-140</link>
		<dc:creator>tobiasmayer</dc:creator>
		<pubDate>Tue, 12 Feb 2008 03:09:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.implementingscrum.com/blog/2008/02/11/development-is-ready-what-about-production-and-support/#comment-140</guid>
		<description>Mike, you clearly describe the unhealthy outcome of having a special group be responsible for support and production, and suggest a good first step.  Would you agree that in the longer term the support group should be dissolved and every single team member should be responsible for support and maintenance of the system?

It makes sense that if the whole team were responsible for maintaining their own code that there would be an increased focus on stability and robustness.</description>
		<content:encoded><![CDATA[<p>Mike, you clearly describe the unhealthy outcome of having a special group be responsible for support and production, and suggest a good first step.  Would you agree that in the longer term the support group should be dissolved and every single team member should be responsible for support and maintenance of the system?</p>
<p>It makes sense that if the whole team were responsible for maintaining their own code that there would be an increased focus on stability and robustness.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

