<?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: Misinterpretation of Command and Control</title>
	<atom:link href="http://blogs.agilefaqs.com/2009/06/21/misinterpretation-of-command-and-control/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.agilefaqs.com/2009/06/21/misinterpretation-of-command-and-control/</link>
	<description>Naresh Jain&#039;s Random Thoughts on Software Development and Adventure Sports</description>
	<lastBuildDate>Tue, 10 Jan 2012 14:24:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: John Stoneham</title>
		<link>http://blogs.agilefaqs.com/2009/06/21/misinterpretation-of-command-and-control/comment-page-1/#comment-14767</link>
		<dc:creator>John Stoneham</dc:creator>
		<pubDate>Sun, 28 Jun 2009 05:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.agilefaqs.com/?p=787#comment-14767</guid>
		<description>A great book to get an understanding of how the military uses this sort of command, and how it survives (or doesn&#039;t survive) contact with the enemy, is Tom Clancy&#039;s non-fiction work Into The Storm: A Study In Command, which is a detailed look at Fred Franks&#039; work in Desert Storm commanding VII Corps and also his time at TRADOC.</description>
		<content:encoded><![CDATA[<p>A great book to get an understanding of how the military uses this sort of command, and how it survives (or doesn&#8217;t survive) contact with the enemy, is Tom Clancy&#8217;s non-fiction work Into The Storm: A Study In Command, which is a detailed look at Fred Franks&#8217; work in Desert Storm commanding VII Corps and also his time at TRADOC.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Stoneham</title>
		<link>http://blogs.agilefaqs.com/2009/06/21/misinterpretation-of-command-and-control/comment-page-1/#comment-15794</link>
		<dc:creator>John Stoneham</dc:creator>
		<pubDate>Sun, 28 Jun 2009 05:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.agilefaqs.com/?p=787#comment-15794</guid>
		<description>A great book to get an understanding of how the military uses this sort of command, and how it survives (or doesn&#039;t survive) contact with the enemy, is Tom Clancy&#039;s non-fiction work Into The Storm: A Study In Command, which is a detailed look at Fred Franks&#039; work in Desert Storm commanding VII Corps and also his time at TRADOC.</description>
		<content:encoded><![CDATA[<p>A great book to get an understanding of how the military uses this sort of command, and how it survives (or doesn&#8217;t survive) contact with the enemy, is Tom Clancy&#8217;s non-fiction work Into The Storm: A Study In Command, which is a detailed look at Fred Franks&#8217; work in Desert Storm commanding VII Corps and also his time at TRADOC.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kalpesh</title>
		<link>http://blogs.agilefaqs.com/2009/06/21/misinterpretation-of-command-and-control/comment-page-1/#comment-14758</link>
		<dc:creator>Kalpesh</dc:creator>
		<pubDate>Thu, 25 Jun 2009 07:56:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.agilefaqs.com/?p=787#comment-14758</guid>
		<description>I guess command &amp; control makes a lot more sense when there is a vision laid out by top guys &amp; guys who are in execution are dedicated to that goal (in a larger sense). Smaller details are left to people &amp; it is required to make sure that they meet the desired small goals which will lead to bigger goals.

e.g. block the border on west, do an air strike, topple the basic infrastructure, infiltrate the government with spies.

Those are smaller goals which lead to a larger goal of a country&#039;s military. 

The style of organization (military) is different than a manufacturing org (such as Toyota). In case of military, a soldier doesn&#039;t have a full-circle view of things. In case of Toyota, it is workers who are much closer to the components, design etc when compared to top management.

Joel has written about different style of management, I guess.</description>
		<content:encoded><![CDATA[<p>I guess command &amp; control makes a lot more sense when there is a vision laid out by top guys &amp; guys who are in execution are dedicated to that goal (in a larger sense). Smaller details are left to people &amp; it is required to make sure that they meet the desired small goals which will lead to bigger goals.</p>
<p>e.g. block the border on west, do an air strike, topple the basic infrastructure, infiltrate the government with spies.</p>
<p>Those are smaller goals which lead to a larger goal of a country&#8217;s military. </p>
<p>The style of organization (military) is different than a manufacturing org (such as Toyota). In case of military, a soldier doesn&#8217;t have a full-circle view of things. In case of Toyota, it is workers who are much closer to the components, design etc when compared to top management.</p>
<p>Joel has written about different style of management, I guess.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kalpesh</title>
		<link>http://blogs.agilefaqs.com/2009/06/21/misinterpretation-of-command-and-control/comment-page-1/#comment-15793</link>
		<dc:creator>Kalpesh</dc:creator>
		<pubDate>Thu, 25 Jun 2009 07:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.agilefaqs.com/?p=787#comment-15793</guid>
		<description>I guess command &amp; control makes a lot more sense when there is a vision laid out by top guys &amp; guys who are in execution are dedicated to that goal (in a larger sense). Smaller details are left to people &amp; it is required to make sure that they meet the desired small goals which will lead to bigger goals.

e.g. block the border on west, do an air strike, topple the basic infrastructure, infiltrate the government with spies.

Those are smaller goals which lead to a larger goal of a country&#039;s military. 

The style of organization (military) is different than a manufacturing org (such as Toyota). In case of military, a soldier doesn&#039;t have a full-circle view of things. In case of Toyota, it is workers who are much closer to the components, design etc when compared to top management.

Joel has written about different style of management, I guess.</description>
		<content:encoded><![CDATA[<p>I guess command &amp; control makes a lot more sense when there is a vision laid out by top guys &amp; guys who are in execution are dedicated to that goal (in a larger sense). Smaller details are left to people &amp; it is required to make sure that they meet the desired small goals which will lead to bigger goals.</p>
<p>e.g. block the border on west, do an air strike, topple the basic infrastructure, infiltrate the government with spies.</p>
<p>Those are smaller goals which lead to a larger goal of a country&#8217;s military. </p>
<p>The style of organization (military) is different than a manufacturing org (such as Toyota). In case of military, a soldier doesn&#8217;t have a full-circle view of things. In case of Toyota, it is workers who are much closer to the components, design etc when compared to top management.</p>
<p>Joel has written about different style of management, I guess.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobias Mayer</title>
		<link>http://blogs.agilefaqs.com/2009/06/21/misinterpretation-of-command-and-control/comment-page-1/#comment-14748</link>
		<dc:creator>Tobias Mayer</dc:creator>
		<pubDate>Tue, 23 Jun 2009 11:34:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.agilefaqs.com/?p=787#comment-14748</guid>
		<description>This understanding of Command and Control may be true in the army, but in the corporate world the term has become synonymous with a style of management where the manager attempts to both instruct the workers and then attempt to control how they do their work.  So terms aside, it is this style of management that Agilists are railing against.

“The advantage which a commander thinks he can attain through continued personal intervention is largely illusory. By engaging in it he assumes a task that really belongs to others, whose effectiveness he thus destroys.&quot;

This I completely agree with, and there is certainly much we can learn from the art of war, but any attempt to redeem the term &quot;command and control&quot; from its sad corner in the nether regions of appallingly bad corporate management is ultimately futile.</description>
		<content:encoded><![CDATA[<p>This understanding of Command and Control may be true in the army, but in the corporate world the term has become synonymous with a style of management where the manager attempts to both instruct the workers and then attempt to control how they do their work.  So terms aside, it is this style of management that Agilists are railing against.</p>
<p>“The advantage which a commander thinks he can attain through continued personal intervention is largely illusory. By engaging in it he assumes a task that really belongs to others, whose effectiveness he thus destroys.&#8221;</p>
<p>This I completely agree with, and there is certainly much we can learn from the art of war, but any attempt to redeem the term &#8220;command and control&#8221; from its sad corner in the nether regions of appallingly bad corporate management is ultimately futile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobias Mayer</title>
		<link>http://blogs.agilefaqs.com/2009/06/21/misinterpretation-of-command-and-control/comment-page-1/#comment-15792</link>
		<dc:creator>Tobias Mayer</dc:creator>
		<pubDate>Tue, 23 Jun 2009 11:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.agilefaqs.com/?p=787#comment-15792</guid>
		<description>This understanding of Command and Control may be true in the army, but in the corporate world the term has become synonymous with a style of management where the manager attempts to both instruct the workers and then attempt to control how they do their work.  So terms aside, it is this style of management that Agilists are railing against.

“The advantage which a commander thinks he can attain through continued personal intervention is largely illusory. By engaging in it he assumes a task that really belongs to others, whose effectiveness he thus destroys.&quot;

This I completely agree with, and there is certainly much we can learn from the art of war, but any attempt to redeem the term &quot;command and control&quot; from its sad corner in the nether regions of appallingly bad corporate management is ultimately futile.</description>
		<content:encoded><![CDATA[<p>This understanding of Command and Control may be true in the army, but in the corporate world the term has become synonymous with a style of management where the manager attempts to both instruct the workers and then attempt to control how they do their work.  So terms aside, it is this style of management that Agilists are railing against.</p>
<p>“The advantage which a commander thinks he can attain through continued personal intervention is largely illusory. By engaging in it he assumes a task that really belongs to others, whose effectiveness he thus destroys.&#8221;</p>
<p>This I completely agree with, and there is certainly much we can learn from the art of war, but any attempt to redeem the term &#8220;command and control&#8221; from its sad corner in the nether regions of appallingly bad corporate management is ultimately futile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D. André Dhondt</title>
		<link>http://blogs.agilefaqs.com/2009/06/21/misinterpretation-of-command-and-control/comment-page-1/#comment-14746</link>
		<dc:creator>D. André Dhondt</dc:creator>
		<pubDate>Tue, 23 Jun 2009 07:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.agilefaqs.com/?p=787#comment-14746</guid>
		<description>So are you saying that &#039;command and control&#039; is a desirable management technique?  Would the Toyota Development System, described below, be an example?
When developing the Toyota Prius, the goal was to make a family car that could get 50mpg (the &#039;command&#039;).  The engineering teams auto-organized around this goal, working with different types of engines... and reconvened on a regular basis to share what they&#039;d learned (the &#039;control&#039;).  Ultimately they built a hybrid engine, and successfully deployed a new car in 15 months.
Even if this is what you&#039;re saying, I think that &#039;command and control&#039; is a misleading title.  In the same presentation, Poppendieck uses the term &#039;mission control&#039; to describe this management style as well.  I think that is a little better, but still prone to miscommunication.</description>
		<content:encoded><![CDATA[<p>So are you saying that &#8216;command and control&#8217; is a desirable management technique?  Would the Toyota Development System, described below, be an example?<br />
When developing the Toyota Prius, the goal was to make a family car that could get 50mpg (the &#8216;command&#8217;).  The engineering teams auto-organized around this goal, working with different types of engines&#8230; and reconvened on a regular basis to share what they&#8217;d learned (the &#8216;control&#8217;).  Ultimately they built a hybrid engine, and successfully deployed a new car in 15 months.<br />
Even if this is what you&#8217;re saying, I think that &#8216;command and control&#8217; is a misleading title.  In the same presentation, Poppendieck uses the term &#8216;mission control&#8217; to describe this management style as well.  I think that is a little better, but still prone to miscommunication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D. André Dhondt</title>
		<link>http://blogs.agilefaqs.com/2009/06/21/misinterpretation-of-command-and-control/comment-page-1/#comment-15791</link>
		<dc:creator>D. André Dhondt</dc:creator>
		<pubDate>Tue, 23 Jun 2009 07:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.agilefaqs.com/?p=787#comment-15791</guid>
		<description>So are you saying that &#039;command and control&#039; is a desirable management technique?  Would the Toyota Development System, described below, be an example?
When developing the Toyota Prius, the goal was to make a family car that could get 50mpg (the &#039;command&#039;).  The engineering teams auto-organized around this goal, working with different types of engines... and reconvened on a regular basis to share what they&#039;d learned (the &#039;control&#039;).  Ultimately they built a hybrid engine, and successfully deployed a new car in 15 months.
Even if this is what you&#039;re saying, I think that &#039;command and control&#039; is a misleading title.  In the same presentation, Poppendieck uses the term &#039;mission control&#039; to describe this management style as well.  I think that is a little better, but still prone to miscommunication.</description>
		<content:encoded><![CDATA[<p>So are you saying that &#8216;command and control&#8217; is a desirable management technique?  Would the Toyota Development System, described below, be an example?<br />
When developing the Toyota Prius, the goal was to make a family car that could get 50mpg (the &#8216;command&#8217;).  The engineering teams auto-organized around this goal, working with different types of engines&#8230; and reconvened on a regular basis to share what they&#8217;d learned (the &#8216;control&#8217;).  Ultimately they built a hybrid engine, and successfully deployed a new car in 15 months.<br />
Even if this is what you&#8217;re saying, I think that &#8216;command and control&#8217; is a misleading title.  In the same presentation, Poppendieck uses the term &#8216;mission control&#8217; to describe this management style as well.  I think that is a little better, but still prone to miscommunication.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

