<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Vroom and the &#8220;Capability Principle&#8221;: from sharing the project vision to successfully delivering projects</title>
	<link>http://www.reformingprojectmanagement.com/2008/03/12/862/</link>
	<description>The magazine for the project age</description>
	<pubDate>Sat, 30 Aug 2008 05:50:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Harry Clovenheit</title>
		<link>http://www.reformingprojectmanagement.com/2008/03/12/862/#comment-20756</link>
		<pubDate>Wed, 28 May 2008 23:46:29 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2008/03/12/862/#comment-20756</guid>
					<description>Claude,
Although I’m no PM buff, I agree with you about the whole sharing project vision concept. I am merely a contractor having sometimes to travel a fair bit to get my job done, but the firm I work for uses this PM software which allows me to communicate my development with them simply by updating my progress. I don’t know if any other PM software has this feature, but it’s great. The point is, even though I’m only a contractor it encompasses me into their project vision simply by keeping in touch about my development, no matter how insignificant or dispersed I am. I see it as technology’s great rejection of the older dinosaur ethics of PM you were appalled by. By the way if anyone is interested in the software, I have included the link for it &lt;a href="http://www.project123.com/" rel="nofollow"&gt;Project123&lt;/a&gt;. 

Great article, keep it up.</description>
		<content:encoded><![CDATA[<p>Claude,<br />
Although I’m no PM buff, I agree with you about the whole sharing project vision concept. I am merely a contractor having sometimes to travel a fair bit to get my job done, but the firm I work for uses this PM software which allows me to communicate my development with them simply by updating my progress. I don’t know if any other PM software has this feature, but it’s great. The point is, even though I’m only a contractor it encompasses me into their project vision simply by keeping in touch about my development, no matter how insignificant or dispersed I am. I see it as technology’s great rejection of the older dinosaur ethics of PM you were appalled by. By the way if anyone is interested in the software, I have included the link for it <a href="http://www.project123.com/" rel="nofollow">Project123</a>. </p>
<p>Great article, keep it up.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tom Cagley</title>
		<link>http://www.reformingprojectmanagement.com/2008/03/12/862/#comment-20741</link>
		<pubDate>Fri, 11 Apr 2008 15:20:28 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2008/03/12/862/#comment-20741</guid>
					<description>The Capability Principle is strongly coupled the triggers to behaviour change (motivation, ability to perform and trigger).   All three components need to exist for change to happen or capability.  Information critical to enable capability.  

The Capability Principle also dove tails with comments made by Phil Armour on the Software Process and Measurment Cast (www.spamcast.net) in a recent interview.  One that struck me was that most structures reflect a command and control structure versus a structure needed to support more chaotic / knowledge based endevours.</description>
		<content:encoded><![CDATA[<p>The Capability Principle is strongly coupled the triggers to behaviour change (motivation, ability to perform and trigger).   All three components need to exist for change to happen or capability.  Information critical to enable capability.  </p>
<p>The Capability Principle also dove tails with comments made by Phil Armour on the Software Process and Measurment Cast (www.spamcast.net) in a recent interview.  One that struck me was that most structures reflect a command and control structure versus a structure needed to support more chaotic / knowledge based endevours.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: David Green</title>
		<link>http://www.reformingprojectmanagement.com/2008/03/12/862/#comment-20736</link>
		<pubDate>Fri, 14 Mar 2008 01:45:15 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2008/03/12/862/#comment-20736</guid>
					<description>The big trouble with not sharing the vision, and everything else that you are able to share about a project, is that you limit the capability of the team. It is impossible to predict which connections are going to be important for any particular task, and a really important connection might not be made if a team member is not aware of the overall context of his or her actions and so the project ends up limping instead of running and failing in the detail.
The failing that leads to this form of management is a misconception that people are machines. All work is a social activity and it must be allowed to work socially to be effective. Strange that in the home of modern democracy work could be done in such an authoritarian manner!</description>
		<content:encoded><![CDATA[<p>The big trouble with not sharing the vision, and everything else that you are able to share about a project, is that you limit the capability of the team. It is impossible to predict which connections are going to be important for any particular task, and a really important connection might not be made if a team member is not aware of the overall context of his or her actions and so the project ends up limping instead of running and failing in the detail.<br />
The failing that leads to this form of management is a misconception that people are machines. All work is a social activity and it must be allowed to work socially to be effective. Strange that in the home of modern democracy work could be done in such an authoritarian manner!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: shailendra</title>
		<link>http://www.reformingprojectmanagement.com/2008/03/12/862/#comment-20735</link>
		<pubDate>Thu, 13 Mar 2008 13:08:11 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2008/03/12/862/#comment-20735</guid>
					<description>sharing vision is a wonderful idea for, an achievement motivation is always a driving tool. however two things will matter - 1. the communication reciever recieves it in exactly same meaning as it is send. for assuring this, a feedback/ verification is must. 
2. capacity should be assessed in two ways - objectively or unbiased and, existing or acquired(by training). Again it requires external support as it is a subjective matter for everyone to assess his own capability.
One last thing - Saying 'NO' is itself is a matter of personality.</description>
		<content:encoded><![CDATA[<p>sharing vision is a wonderful idea for, an achievement motivation is always a driving tool. however two things will matter - 1. the communication reciever recieves it in exactly same meaning as it is send. for assuring this, a feedback/ verification is must.<br />
2. capacity should be assessed in two ways - objectively or unbiased and, existing or acquired(by training). Again it requires external support as it is a subjective matter for everyone to assess his own capability.<br />
One last thing - Saying &#8216;NO&#8217; is itself is a matter of personality.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
