<?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"
	>
<channel>
	<title>Comments on: Production System Alignment and Measurement</title>
	<atom:link href="http://www.dailykaizen.org/archives/340/feed" rel="self" type="application/rss+xml" />
	<link>http://www.dailykaizen.org/archives/340</link>
	<description>A blog about improvement in health care</description>
	<pubDate>Mon, 01 Dec 2008 20:38:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Anand</title>
		<link>http://www.dailykaizen.org/archives/340#comment-3756</link>
		<dc:creator>Anand</dc:creator>
		<pubDate>Wed, 11 Jul 2007 13:40:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/archives/340#comment-3756</guid>
		<description>Hi Lee,

I do agree with you on the fact that the teams are not aligned and 'Agile' is not the solution. My comment was oriented more towards prioritization.

About metrics, you are right. 'HPA claims' and 'ISD claims' are not measured on the same metrics though the value stream encompasses both groups. I'm excited about the new PAs (I still have not seen it yet) where the metrics is more oriented towards behaviour.

Anand</description>
		<content:encoded><![CDATA[<p>Hi Lee,</p>
<p>I do agree with you on the fact that the teams are not aligned and &#8216;Agile&#8217; is not the solution. My comment was oriented more towards prioritization.</p>
<p>About metrics, you are right. &#8216;HPA claims&#8217; and &#8216;ISD claims&#8217; are not measured on the same metrics though the value stream encompasses both groups. I&#8217;m excited about the new PAs (I still have not seen it yet) where the metrics is more oriented towards behaviour.</p>
<p>Anand</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Fried</title>
		<link>http://www.dailykaizen.org/archives/340#comment-3751</link>
		<dc:creator>Lee Fried</dc:creator>
		<pubDate>Tue, 10 Jul 2007 17:31:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/archives/340#comment-3751</guid>
		<description>Hi Anand, 

You are far more connected to the work then I am so I thank you for your comments.  

I do believe that we still have alignment problems across the production system.  We still struggle on a daily basis in keeping operational teams aligned, let alone supporting teams.  

I believe Agile provides a lot of value in helping bridge this gap, but I would argue that just because the business teams make decisions on what the priorities are of IT projects moving forward does not mean that teams will be in alignment.  Alignment will result only when the management and measurement systems come together in support of the Value Stream.  Toyota has mastered this alignment and when the Andon cord gets pulled everyone knows what needs to be done to get the production line up and moving and the root cause of the problem fixed.

Please don't take my post as being critical, I believe the work being done on both sides of the house is impressive and encouraging. And I agree 100% with your comment about change, it will take time and a lot of hard work.  The important part will be that we keep learning and working together to solve the hard problems!

Thanks for the post,

Lee</description>
		<content:encoded><![CDATA[<p>Hi Anand, </p>
<p>You are far more connected to the work then I am so I thank you for your comments.  </p>
<p>I do believe that we still have alignment problems across the production system.  We still struggle on a daily basis in keeping operational teams aligned, let alone supporting teams.  </p>
<p>I believe Agile provides a lot of value in helping bridge this gap, but I would argue that just because the business teams make decisions on what the priorities are of IT projects moving forward does not mean that teams will be in alignment.  Alignment will result only when the management and measurement systems come together in support of the Value Stream.  Toyota has mastered this alignment and when the Andon cord gets pulled everyone knows what needs to be done to get the production line up and moving and the root cause of the problem fixed.</p>
<p>Please don&#8217;t take my post as being critical, I believe the work being done on both sides of the house is impressive and encouraging. And I agree 100% with your comment about change, it will take time and a lot of hard work.  The important part will be that we keep learning and working together to solve the hard problems!</p>
<p>Thanks for the post,</p>
<p>Lee</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anand</title>
		<link>http://www.dailykaizen.org/archives/340#comment-3750</link>
		<dc:creator>Anand</dc:creator>
		<pubDate>Tue, 10 Jul 2007 15:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/archives/340#comment-3750</guid>
		<description>There is a slight disconnect with what is mentioned here and reality.

I work in Claims Information Sytems (IS) group and we are following the Agile development methodology. In this new process, the business sets the priorities and not the IS group. The prioritization happens every month based on the need. So the discussion of aligning priorities between the processing group and the IS group does not make sense. 

But, to a certain extent, what is mentioned is true. This is regarding the urgency to get something done by both groups. Claims IS group does not support just HPA Claims. They support the Web team, Finance, Contracts, eWatson, etc. This is just one reason why priorities are a little different. 

The problem here goes back to an older post on managing change. Not all groups are changing at the same time and this is the disconnect. Though we cannot use a big-bang approach, this is something we have to live with during the transition phase and we are all still learning.</description>
		<content:encoded><![CDATA[<p>There is a slight disconnect with what is mentioned here and reality.</p>
<p>I work in Claims Information Sytems (IS) group and we are following the Agile development methodology. In this new process, the business sets the priorities and not the IS group. The prioritization happens every month based on the need. So the discussion of aligning priorities between the processing group and the IS group does not make sense. </p>
<p>But, to a certain extent, what is mentioned is true. This is regarding the urgency to get something done by both groups. Claims IS group does not support just HPA Claims. They support the Web team, Finance, Contracts, eWatson, etc. This is just one reason why priorities are a little different. </p>
<p>The problem here goes back to an older post on managing change. Not all groups are changing at the same time and this is the disconnect. Though we cannot use a big-bang approach, this is something we have to live with during the transition phase and we are all still learning.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
