<?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 for Ensemble</title>
	<atom:link href="http://ensemblemc.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://ensemblemc.com</link>
	<description>A Commitment-Based Way of Working</description>
	<lastBuildDate>Tue, 21 Feb 2012 16:31:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<meta xmlns="http://www.w3.org/1999/xhtml" name="robots" content="noindex,follow" />
	<item>
		<title>Comment on Our Talks by Timm J. Esque</title>
		<link>http://ensemblemc.com/resources/our-talks/#comment-162</link>
		<dc:creator>Timm J. Esque</dc:creator>
		<pubDate>Tue, 21 Feb 2012 16:31:01 +0000</pubDate>
		<guid isPermaLink="false">http://brightmonk.com/ensemble/?page_id=81#comment-162</guid>
		<description>There is a concept in Taoism called Wu Wei - sometimes translated as action through inaction.  I don&#039;t think pushing is consistent with this concept.  When we feel the need to push others, we have run out of ideas to reason with them.
Team members on a project generally want the project to succeed as much as the PM.  They need to understand what they specifically need to produce to support success and who is depending on them.  They need to know that every team member is holding the other&#039;s accountable, not just the PM.  When the PM puts these things in place, pushing is not necessary (and doesn&#039;t help anyway).  
The closest productive thing to pushing that PMs can do is clearly communicate a challenging and worthy project goal, and then follow through on disciplined CBPM practices.
Timm</description>
		<content:encoded><![CDATA[<p>There is a concept in Taoism called Wu Wei &#8211; sometimes translated as action through inaction.  I don&#8217;t think pushing is consistent with this concept.  When we feel the need to push others, we have run out of ideas to reason with them.<br />
Team members on a project generally want the project to succeed as much as the PM.  They need to understand what they specifically need to produce to support success and who is depending on them.  They need to know that every team member is holding the other&#8217;s accountable, not just the PM.  When the PM puts these things in place, pushing is not necessary (and doesn&#8217;t help anyway).<br />
The closest productive thing to pushing that PMs can do is clearly communicate a challenging and worthy project goal, and then follow through on disciplined CBPM practices.<br />
Timm</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Hardest Lesson to Learn? by Clinton</title>
		<link>http://ensemblemc.com/2012/01/04/the-hardest-lesson-to-learn/#comment-134</link>
		<dc:creator>Clinton</dc:creator>
		<pubDate>Thu, 09 Feb 2012 06:02:37 +0000</pubDate>
		<guid isPermaLink="false">http://ensemblemc.com/?p=1736#comment-134</guid>
		<description>kanban in Lean is more alctrauecy described as a tool or technique rather than an overall process or system.  So it&#8217;s kind of confusing to compare kanban with Scrum.I like the idea of focusing on improving rather than being Agile, Lean, etc.</description>
		<content:encoded><![CDATA[<p>kanban in Lean is more alctrauecy described as a tool or technique rather than an overall process or system.  So it&#8217;s kind of confusing to compare kanban with Scrum.I like the idea of focusing on improving rather than being Agile, Lean, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Our Talks by Yudith</title>
		<link>http://ensemblemc.com/resources/our-talks/#comment-133</link>
		<dc:creator>Yudith</dc:creator>
		<pubDate>Thu, 09 Feb 2012 05:01:58 +0000</pubDate>
		<guid isPermaLink="false">http://brightmonk.com/ensemble/?page_id=81#comment-133</guid>
		<description>I like the blog - thank you for psoting.  But I have a question about pushing as mentioned in the Tao and in your post: if the PM does not push - how do you expedite when the schedule slips?  Does not pushing mean that you just flow like water and try to see if there are alternatives to getting the work done within the same constraints - a change in words (which can result in a completely different atmosphere)?Thanks againTryllid</description>
		<content:encoded><![CDATA[<p>I like the blog &#8211; thank you for psoting.  But I have a question about pushing as mentioned in the Tao and in your post: if the PM does not push &#8211; how do you expedite when the schedule slips?  Does not pushing mean that you just flow like water and try to see if there are alternatives to getting the work done within the same constraints &#8211; a change in words (which can result in a completely different atmosphere)?Thanks againTryllid</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Team Building and Ensuring Goals are Met : Same Thing by Birgit Zacher Hanson</title>
		<link>http://ensemblemc.com/2012/01/23/team-building-and-ensuring-goals-are-met-same-thing/#comment-111</link>
		<dc:creator>Birgit Zacher Hanson</dc:creator>
		<pubDate>Tue, 31 Jan 2012 21:33:26 +0000</pubDate>
		<guid isPermaLink="false">http://ensemblemc.com/?p=1812#comment-111</guid>
		<description>The dysfunction on most of the teams I have witnessed is that people do not see and thus step over the first two layers in this model. They are so focused on getting the task done, the deadlines met and keeping their clients happy that they fail to develop an approach to systematically build trust and manage commitments.
 
Unfortunately, the lack of trust goes hand in hand with the withholding of important information (including the internal conversations around willingness and capacity.)  

Without trust people wont&#039; open up fully, won&#039;t renegotiate powerfully and the silence is often misinterpreted as buy-in leading to future and costly breakdowns.  This book lays the foundation for commitment-based management. Thanks for the review and reminder of such pertinent information.</description>
		<content:encoded><![CDATA[<p>The dysfunction on most of the teams I have witnessed is that people do not see and thus step over the first two layers in this model. They are so focused on getting the task done, the deadlines met and keeping their clients happy that they fail to develop an approach to systematically build trust and manage commitments.</p>
<p>Unfortunately, the lack of trust goes hand in hand with the withholding of important information (including the internal conversations around willingness and capacity.)  </p>
<p>Without trust people wont&#8217; open up fully, won&#8217;t renegotiate powerfully and the silence is often misinterpreted as buy-in leading to future and costly breakdowns.  This book lays the foundation for commitment-based management. Thanks for the review and reminder of such pertinent information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Questions from Commitment-Based Project Management (CBPM) Practitioners by Timm Esque</title>
		<link>http://ensemblemc.com/2011/11/16/questions-from-commitment-based-project-management-cbpm-practitioners/#comment-53</link>
		<dc:creator>Timm Esque</dc:creator>
		<pubDate>Wed, 14 Dec 2011 19:01:04 +0000</pubDate>
		<guid isPermaLink="false">http://ensemblemc.com/?p=1625#comment-53</guid>
		<description>Anil is referring to the simple CBPM rule that a deliverable is not considered Done until the downstream Users of that deliverable say that they received the deliverable and it meets pre-defined quality specifications.  
The other simple rule that applies here is that quality for a deliverable should always be agreed to (between owners and users) before a commit date is put on that deliverable.  If I was concerned that my Users were letting the Owners off too easy, I would start asking some probing questions about the quality criteria in the review meetings.  E.g. what were the agreed to criteria?  And you are saying you are satisfied that each of them has been met?  I would do this for all deliverables for awhile, and then just on a random sampling basis after awhile.
These are some generic answers to subtle issues.  It is always a good idea to do a lot of listening before jumping to conclusions about what is making it difficult for someone to get on board.  What are they committed to?  What is missing?  What can be done to help them choose to tryout CBPM as it is designed?
Thanks for the questions.</description>
		<content:encoded><![CDATA[<p>Anil is referring to the simple CBPM rule that a deliverable is not considered Done until the downstream Users of that deliverable say that they received the deliverable and it meets pre-defined quality specifications.<br />
The other simple rule that applies here is that quality for a deliverable should always be agreed to (between owners and users) before a commit date is put on that deliverable.  If I was concerned that my Users were letting the Owners off too easy, I would start asking some probing questions about the quality criteria in the review meetings.  E.g. what were the agreed to criteria?  And you are saying you are satisfied that each of them has been met?  I would do this for all deliverables for awhile, and then just on a random sampling basis after awhile.<br />
These are some generic answers to subtle issues.  It is always a good idea to do a lot of listening before jumping to conclusions about what is making it difficult for someone to get on board.  What are they committed to?  What is missing?  What can be done to help them choose to tryout CBPM as it is designed?<br />
Thanks for the questions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Questions from Commitment-Based Project Management (CBPM) Practitioners by Timm Esque</title>
		<link>http://ensemblemc.com/2011/11/16/questions-from-commitment-based-project-management-cbpm-practitioners/#comment-52</link>
		<dc:creator>Timm Esque</dc:creator>
		<pubDate>Wed, 14 Dec 2011 18:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://ensemblemc.com/?p=1625#comment-52</guid>
		<description>Thanks for getting this started Jim.  Going to take a while to build up the community, so in the interim will share my thoughts on your specific question.  Still interested in how others would/have approached this situation.

Our first advice when someone is resisting to make weekly commitments is to ask what they can commit to.  What are they working on now and what can they commit to have done end of tomorrow or even end of today.  It can help to discuss how making commitments gives a person more power to say &quot;No&quot; to some of those requests that pop up.
There is also a common mis-perception that commitments are written in stone. In fact, a principle of managing with commitments is that commitments are negotiable.  There should be no stigma attached to speaking up as soon as a commitment seems to be in jeopardy and negotiating a modified commitment in alignment with the team&#039;s goals.  This sometimes needs to be over-communicated, especially when people feel they were unfairly treated in the past (could have happened in another org or before you got there).  Obviously, a habit of renegotiation commitments all the time is not very productive, but our experience is when people start managing commits, they get better at meeting them.
Peer pressure is also helpful especially in getting started managing commitments.  It is a lot harder for one person to say it is impossible to operate from commitments, when their colleagues are making and meeting commitments in their regular team meetings.
Other thoughts?</description>
		<content:encoded><![CDATA[<p>Thanks for getting this started Jim.  Going to take a while to build up the community, so in the interim will share my thoughts on your specific question.  Still interested in how others would/have approached this situation.</p>
<p>Our first advice when someone is resisting to make weekly commitments is to ask what they can commit to.  What are they working on now and what can they commit to have done end of tomorrow or even end of today.  It can help to discuss how making commitments gives a person more power to say &#8220;No&#8221; to some of those requests that pop up.<br />
There is also a common mis-perception that commitments are written in stone. In fact, a principle of managing with commitments is that commitments are negotiable.  There should be no stigma attached to speaking up as soon as a commitment seems to be in jeopardy and negotiating a modified commitment in alignment with the team&#8217;s goals.  This sometimes needs to be over-communicated, especially when people feel they were unfairly treated in the past (could have happened in another org or before you got there).  Obviously, a habit of renegotiation commitments all the time is not very productive, but our experience is when people start managing commits, they get better at meeting them.<br />
Peer pressure is also helpful especially in getting started managing commitments.  It is a lot harder for one person to say it is impossible to operate from commitments, when their colleagues are making and meeting commitments in their regular team meetings.<br />
Other thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Questions from Commitment-Based Project Management (CBPM) Practitioners by Anil Jain</title>
		<link>http://ensemblemc.com/2011/11/16/questions-from-commitment-based-project-management-cbpm-practitioners/#comment-31</link>
		<dc:creator>Anil Jain</dc:creator>
		<pubDate>Mon, 21 Nov 2011 08:16:34 +0000</pubDate>
		<guid isPermaLink="false">http://ensemblemc.com/?p=1625#comment-31</guid>
		<description>One challenge I have run across from time to time is the situation where harmony is chosen over constructive debate.  Specifically, in the scenario I am referring to, a team member affirms that his deliverable is completed and the receiving team members confirm receipt, but do not bring up the fact that the deliverable is of insufficient quality or is incomplete. I surmise the reluctance to bring this up is to preserve the relationship between team members.

How can we encourage team members to be completely open and communicate exactly what their assessment is, with everyone aligned around the shared purpose of the final goal.</description>
		<content:encoded><![CDATA[<p>One challenge I have run across from time to time is the situation where harmony is chosen over constructive debate.  Specifically, in the scenario I am referring to, a team member affirms that his deliverable is completed and the receiving team members confirm receipt, but do not bring up the fact that the deliverable is of insufficient quality or is incomplete. I surmise the reluctance to bring this up is to preserve the relationship between team members.</p>
<p>How can we encourage team members to be completely open and communicate exactly what their assessment is, with everyone aligned around the shared purpose of the final goal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Questions from Commitment-Based Project Management (CBPM) Practitioners by Jim Wilder, PMP</title>
		<link>http://ensemblemc.com/2011/11/16/questions-from-commitment-based-project-management-cbpm-practitioners/#comment-28</link>
		<dc:creator>Jim Wilder, PMP</dc:creator>
		<pubDate>Wed, 16 Nov 2011 21:06:03 +0000</pubDate>
		<guid isPermaLink="false">http://ensemblemc.com/?p=1625#comment-28</guid>
		<description>There have been a few occasions when an individual is assigned to my CBPM team that has a very difficult time making a commitment. Even after private coaching and stepping through the logic of the CBPM mapping process, I&#039;ve been told things like &quot;I can&#039;t make a commitment because I never know what new work is going to pop up during the week&quot;. I have in some cases resorted to having direct managers present in a map meeting to help coach/support individuals in their departments. Has anyone else run across this issue and, if so, what technique are you using to manage them?</description>
		<content:encoded><![CDATA[<p>There have been a few occasions when an individual is assigned to my CBPM team that has a very difficult time making a commitment. Even after private coaching and stepping through the logic of the CBPM mapping process, I&#8217;ve been told things like &#8220;I can&#8217;t make a commitment because I never know what new work is going to pop up during the week&#8221;. I have in some cases resorted to having direct managers present in a map meeting to help coach/support individuals in their departments. Has anyone else run across this issue and, if so, what technique are you using to manage them?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Do You Know the Golden Rule of Project Reporting? by us postage rates</title>
		<link>http://ensemblemc.com/2011/10/26/do-you-know-the-golden-rule-of-project-reporting/#comment-27</link>
		<dc:creator>us postage rates</dc:creator>
		<pubDate>Tue, 15 Nov 2011 06:35:07 +0000</pubDate>
		<guid isPermaLink="false">http://ensemblemc.com/?p=1532#comment-27</guid>
		<description>My definition of stress is being held accountable for that which you can&#039;t control.</description>
		<content:encoded><![CDATA[<p>My definition of stress is being held accountable for that which you can&#8217;t control.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

