<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Change Management</title>
	<atom:link href="http://tskraghu.wordpress.com/2008/04/08/change-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://tskraghu.wordpress.com/2008/04/08/change-management/</link>
	<description>Jottings from a professional</description>
	<lastBuildDate>Sun, 28 Jun 2009 05:04:10 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tskraghu</title>
		<link>http://tskraghu.wordpress.com/2008/04/08/change-management/#comment-22</link>
		<dc:creator>tskraghu</dc:creator>
		<pubDate>Mon, 21 Jul 2008 16:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://tskraghu.wordpress.com/?p=13#comment-22</guid>
		<description>The context here is akin to software development services for Product Engineering where a proposal, perhaps single-shot, is submitted and gets evaluated. The point made is that the internal and external parameters of the estimates in the proposal need to be clearly and explicitly communicated to the delivery function so that changes to these parameters are controlled as early as possible with well-informed alertness. Now it is possible to identify uplanned unprovided-for scope escalation as soon as it occurs so that it may be handled in an apprpriate manner.</description>
		<content:encoded><![CDATA[<p>The context here is akin to software development services for Product Engineering where a proposal, perhaps single-shot, is submitted and gets evaluated. The point made is that the internal and external parameters of the estimates in the proposal need to be clearly and explicitly communicated to the delivery function so that changes to these parameters are controlled as early as possible with well-informed alertness. Now it is possible to identify uplanned unprovided-for scope escalation as soon as it occurs so that it may be handled in an apprpriate manner.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Basudev Pal</title>
		<link>http://tskraghu.wordpress.com/2008/04/08/change-management/#comment-21</link>
		<dc:creator>Basudev Pal</dc:creator>
		<pubDate>Mon, 21 Jul 2008 07:48:29 +0000</pubDate>
		<guid isPermaLink="false">http://tskraghu.wordpress.com/?p=13#comment-21</guid>
		<description>I am a Nerd or an ego-centric person to fight with my delivery manager on issues of scope changes. I am a front-end sales guy who looks into the eyes of the client to make a committment. What I sell is change management encapsulated in service which is measured by SLAs. What I expect is a clrity of operation. Mind you to the deilvery person I am his/her customer FIRST. I need to be satisfied that WE will deliver what I promised. 
SO does the ageold proposal can manage this expectation. Well Mr/Ms delivery manager you have written 40 - 50 pages of material stating what shall you do which is cut and pasted from your previous assignment expecting it to be true every time.
So what is change management ? deviation from the normal work program. Is it acceptable ? Yes as business needs it. How do you manage ? Well if I change my proposal to an Operational process of your portfolio then am I not getting in your shoes to understand your need of MY involvement ? I should first understand what you do . Then understand what you want . Thirdly say how do I deliver it. Well now I have my operational process in place then I ask the work streams to be placed in this operational process. The work streams are controlled by Statement of Work goverend by SLA s which arise from the Operational process. Is this not what quality process is all about ?
What are the merits - My estimation is a clear transparent document which is a subset of my operational process. My workflow is clearly defined which has the sign-off of the client as a method of going forward. 
Do we still need the ageold proposal ?</description>
		<content:encoded><![CDATA[<p>I am a Nerd or an ego-centric person to fight with my delivery manager on issues of scope changes. I am a front-end sales guy who looks into the eyes of the client to make a committment. What I sell is change management encapsulated in service which is measured by SLAs. What I expect is a clrity of operation. Mind you to the deilvery person I am his/her customer FIRST. I need to be satisfied that WE will deliver what I promised.<br />
SO does the ageold proposal can manage this expectation. Well Mr/Ms delivery manager you have written 40 &#8211; 50 pages of material stating what shall you do which is cut and pasted from your previous assignment expecting it to be true every time.<br />
So what is change management ? deviation from the normal work program. Is it acceptable ? Yes as business needs it. How do you manage ? Well if I change my proposal to an Operational process of your portfolio then am I not getting in your shoes to understand your need of MY involvement ? I should first understand what you do . Then understand what you want . Thirdly say how do I deliver it. Well now I have my operational process in place then I ask the work streams to be placed in this operational process. The work streams are controlled by Statement of Work goverend by SLA s which arise from the Operational process. Is this not what quality process is all about ?<br />
What are the merits &#8211; My estimation is a clear transparent document which is a subset of my operational process. My workflow is clearly defined which has the sign-off of the client as a method of going forward.<br />
Do we still need the ageold proposal ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
