<?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: Build Listening Systems for Project Success</title>
	<link>http://www.reformingprojectmanagement.com/2003/04/04/157/</link>
	<description>The magazine for the project age</description>
	<pubDate>Wed, 07 Jan 2009 08:58:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Claude Emond
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/04/04/157/#comment-323</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/04/04/157/#comment-323</guid>
					<description>
        it is not a coincidence that one of the 4 cornerstones of agile programming projects, as illustrated by the eXtreme programming philosophy and rules is LISTENING: see  http://xp.c2.com/ExtremeProgramming.html 

Those 4 cornerstones are Coding, Testing, Listening and Designing. This is what is said about listening:

«You have to learn what the problem is in the first place, then you have to learn what numbers to put in the tests. You probably won't know this yourself, so you have to get good at listening to clients - users, managers, and business people»

For sure, when project teams use SCRUM approaches, approaches that consist in having 30 minutes meetings to adjust the work EVERY SINGLE DAY, there is a lot of listening going own, not only from the project-team manager/leader but from EVERYONE. Since in Agile, the team accepts to collectively be accountable for the results, listening, but also the whole function of COMMUNICATION, is the business of EVERYBODY. In fact, in a SCRUM setting, those meetings-conversations are at the center of the management process; they are even the whole of the management process in many instances. 

I imagine that similar comments apply to the LAST PLANNER System,with which you are more familiar than me. From what I understand, one of its main features implies listening to the last planners (those who do the work) BEFORE we start anything (as opposed to asking for suggestions when it is already too late in the execution of a plan that was developped in isolation and imposed without consultation)

Listening has my vote as a major key success factor of project management. It is even a pre-condition to planning, for without proper listening, your initial planning will only be unshared wishful thinking and, furthermore, you won't be able to adjust it when the real world confronts you during execution.

Amen
      </description>
		<content:encoded><![CDATA[<p>it is not a coincidence that one of the 4 cornerstones of agile programming projects, as illustrated by the eXtreme programming philosophy and rules is LISTENING: see  <a href="http://xp.c2.com/ExtremeProgramming.html" rel="nofollow">http://xp.c2.com/ExtremeProgramming.html</a> </p>
<p>Those 4 cornerstones are Coding, Testing, Listening and Designing. This is what is said about listening:</p>
<p>«You have to learn what the problem is in the first place, then you have to learn what numbers to put in the tests. You probably won&#8217;t know this yourself, so you have to get good at listening to clients - users, managers, and business people»</p>
<p>For sure, when project teams use SCRUM approaches, approaches that consist in having 30 minutes meetings to adjust the work EVERY SINGLE DAY, there is a lot of listening going own, not only from the project-team manager/leader but from EVERYONE. Since in Agile, the team accepts to collectively be accountable for the results, listening, but also the whole function of COMMUNICATION, is the business of EVERYBODY. In fact, in a SCRUM setting, those meetings-conversations are at the center of the management process; they are even the whole of the management process in many instances. </p>
<p>I imagine that similar comments apply to the LAST PLANNER System,with which you are more familiar than me. From what I understand, one of its main features implies listening to the last planners (those who do the work) BEFORE we start anything (as opposed to asking for suggestions when it is already too late in the execution of a plan that was developped in isolation and imposed without consultation)</p>
<p>Listening has my vote as a major key success factor of project management. It is even a pre-condition to planning, for without proper listening, your initial planning will only be unshared wishful thinking and, furthermore, you won&#8217;t be able to adjust it when the real world confronts you during execution.</p>
<p>Amen
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hal
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/04/04/157/#comment-324</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/04/04/157/#comment-324</guid>
					<description>
        Well said, Claude.  :+:

So much of our attention in project management is on the tangible aspects: contracts, budget, schedules, activities, tasks, materiel, methods, etc.  Too often we fail to put the humanness of projects front and center.

How often have we encountered projects in trouble and the team members know what to do to fix it, but those actions are not being taken?  Each time I've encountered that situation I've also run into a project manager who doesn't listen.

Listening is one of the foundational skills of project managers.  Without a high level of competence at listenting projects are doomed to drift.  Given the general characterization by wives that husbands don't listen, anytime we have project managers who are men we have a potential breakdown.

So...for anyone recruiting/selecting project maangers find a way to assess their competence and openness of listening.  The success of your projects depends on it.
      </description>
		<content:encoded><![CDATA[<p>Well said, Claude.  :+:</p>
<p>So much of our attention in project management is on the tangible aspects: contracts, budget, schedules, activities, tasks, <acronym title="refers to equipment, tools, material, and supplies needed for production">materiel</acronym>, methods, etc.  Too often we fail to put the humanness of projects front and center.</p>
<p>How often have we encountered projects in trouble and the team members know what to do to fix it, but those actions are not being taken?  Each time I&#8217;ve encountered that situation I&#8217;ve also run into a project manager who doesn&#8217;t listen.</p>
<p>Listening is one of the foundational skills of project managers.  Without a high level of competence at listenting projects are doomed to drift.  Given the general characterization by wives that husbands don&#8217;t listen, anytime we have project managers who are men we have a potential breakdown.</p>
<p>So&#8230;for anyone recruiting/selecting project maangers find a way to assess their competence and openness of listening.  The success of your projects depends on it.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eli Robillard
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/04/04/157/#comment-325</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/04/04/157/#comment-325</guid>
					<description>
        Good post. In one of my own I make the case that both listening and taste are the keys to writing useful software. There is art to listening: http://dotnetweblogs.com/ERobillard/Story/4479.aspx

Take care,
Eli.
      </description>
		<content:encoded><![CDATA[<p>Good post. In one of my own I make the case that both listening and taste are the keys to writing useful software. There is art to listening: <a href="http://dotnetweblogs.com/ERobillard/Story/4479.aspx" rel="nofollow">http://dotnetweblogs.com/ERobillard/Story/4479.aspx</a></p>
<p>Take care,<br />
Eli.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
