<?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: New Years Resolution</title>
	<atom:link href="http://www.bigvisible.com/asroka/new-years-resolution/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bigvisible.com/asroka/new-years-resolution/</link>
	<description></description>
	<lastBuildDate>Tue, 20 Jul 2010 04:54:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: steve blais</title>
		<link>http://www.bigvisible.com/asroka/new-years-resolution/comment-page-1/#comment-21432</link>
		<dc:creator>steve blais</dc:creator>
		<pubDate>Mon, 04 Jan 2010 12:30:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.bigvisible.com/?p=704#comment-21432</guid>
		<description>Clearly we must always keep changing and improving or we stagnate and basically stop living. A pattern of simply changing for the purpose of changing, while it will bring benefits thru positive results, albeit small improvements, seems somewhat haphazard.  Shouldn&#039;t there be an overall plan to the changes being made?  Or is it improvement enough to drop a pound of weight one week, read a classic book the next, stop a bad eating habit the third, go back and drop another pound the fourth and so on?  This haphazardness, while more in line with normal human attention spans and in many ways a lot more satisfying, does not translate well to software development, the start of the analogy. Without some organization and longer term goal setting and planning, the PO may continually change the backlog based on most current needs causing a lot of work to be done, software delivered each spring and after six months, no appreciable progress, nothing of significant value delivered to the organization.  
Agreed. Change little at a time and make the change continuous. Constantly focus on process improvement, and self-improvement. And you feel good about losing that pound or finishing the next chapter of War and Peace.  Isn&#039;t it a better feeling and more positive impact on the self esteem to get to a target weight or finish the book?  Isn&#039;t it better for the team and the organization when the final product is completed and the project over to the adulation and praise of a thankful management? 
OK. So I&#039;m going overboard a little, but you get the point. Or, is the concept of achieving a set goal a little at a time assumed in your initial post?</description>
		<content:encoded><![CDATA[<p>Clearly we must always keep changing and improving or we stagnate and basically stop living. A pattern of simply changing for the purpose of changing, while it will bring benefits thru positive results, albeit small improvements, seems somewhat haphazard.  Shouldn&#8217;t there be an overall plan to the changes being made?  Or is it improvement enough to drop a pound of weight one week, read a classic book the next, stop a bad eating habit the third, go back and drop another pound the fourth and so on?  This haphazardness, while more in line with normal human attention spans and in many ways a lot more satisfying, does not translate well to software development, the start of the analogy. Without some organization and longer term goal setting and planning, the PO may continually change the backlog based on most current needs causing a lot of work to be done, software delivered each spring and after six months, no appreciable progress, nothing of significant value delivered to the organization.<br />
Agreed. Change little at a time and make the change continuous. Constantly focus on process improvement, and self-improvement. And you feel good about losing that pound or finishing the next chapter of War and Peace.  Isn&#8217;t it a better feeling and more positive impact on the self esteem to get to a target weight or finish the book?  Isn&#8217;t it better for the team and the organization when the final product is completed and the project over to the adulation and praise of a thankful management?<br />
OK. So I&#8217;m going overboard a little, but you get the point. Or, is the concept of achieving a set goal a little at a time assumed in your initial post?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Sroka</title>
		<link>http://www.bigvisible.com/asroka/new-years-resolution/comment-page-1/#comment-21425</link>
		<dc:creator>Adam Sroka</dc:creator>
		<pubDate>Mon, 04 Jan 2010 05:31:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.bigvisible.com/?p=704#comment-21425</guid>
		<description>Hi Steve:

Don&#039;t think of these as different projects, think of them as different features of the same product. Every aspect of your life affects every other aspect. When you improve something at work it will change things at home and vice versa. 

I presume it is possible, at least mathematically, to reach a point where no change will yield a foreseeable improvement. I don&#039;t think it is something we ought to worry about, though.</description>
		<content:encoded><![CDATA[<p>Hi Steve:</p>
<p>Don&#8217;t think of these as different projects, think of them as different features of the same product. Every aspect of your life affects every other aspect. When you improve something at work it will change things at home and vice versa. </p>
<p>I presume it is possible, at least mathematically, to reach a point where no change will yield a foreseeable improvement. I don&#8217;t think it is something we ought to worry about, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steve blais</title>
		<link>http://www.bigvisible.com/asroka/new-years-resolution/comment-page-1/#comment-21413</link>
		<dc:creator>steve blais</dc:creator>
		<pubDate>Sun, 03 Jan 2010 11:35:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.bigvisible.com/?p=704#comment-21413</guid>
		<description>Good concept.  Is there an end?  Is it possible to get to a place where you feel no further change is necessary in a certain area?  Even in agile there is an end to an evolving product.  The cost of the next change is greater than the benefits that will derive from that change. With a system the development team must go on to other systems or disperse. With our own personal change we can move from changing our weight when we get to a weight we are comfortable with, to improving our analytical abilities by reading or playing brain games or learning a new language. 
Perhaps it&#039;s more about setting a goal and evolving toward it.  Then setting a new goal. Also quite agile. Each iteration or sprint is a new goal. However, that is not quite a new concept.  Serial achievement of goals as a method to be successful extends back to the Romans if not before.</description>
		<content:encoded><![CDATA[<p>Good concept.  Is there an end?  Is it possible to get to a place where you feel no further change is necessary in a certain area?  Even in agile there is an end to an evolving product.  The cost of the next change is greater than the benefits that will derive from that change. With a system the development team must go on to other systems or disperse. With our own personal change we can move from changing our weight when we get to a weight we are comfortable with, to improving our analytical abilities by reading or playing brain games or learning a new language.<br />
Perhaps it&#8217;s more about setting a goal and evolving toward it.  Then setting a new goal. Also quite agile. Each iteration or sprint is a new goal. However, that is not quite a new concept.  Serial achievement of goals as a method to be successful extends back to the Romans if not before.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
