<?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 ProjectBrief Blog</title>
	<atom:link href="http://www.watermarklearning.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.watermarklearning.com/blog</link>
	<description>For Business Analysts and Project Managers</description>
	<lastBuildDate>Fri, 16 Jul 2010 18:18:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on Scrum vs. Waterfall: The Fight Continues by ElizabethLarson</title>
		<link>http://www.watermarklearning.com/blog/scrum-vs-waterfall-pt2/comment-page-1/#comment-370</link>
		<dc:creator>ElizabethLarson</dc:creator>
		<pubDate>Fri, 16 Jul 2010 18:18:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.watermarklearning.com/blog/?p=609#comment-370</guid>
		<description>Martin,
You pose an interesting and important question: what happens when you don&#039;t have high-performance team member(s) on your Scrum project. I have seen some teams that are not uniformly high-performing start off OK, get frustrated, and then look to the Scrum Master to resolve conflicts, which is iffy at best. When the Scrum Master remains neutral and doesn&#039;t try to take on a leadership role,  a leader often emerges who ironically is not the one who talks the most or has the most experience. My preference is for a strong product owners to get the team members motivated because forgetting chickens and pigs,if the project goes awry, the organization (represented by the product owner) doesn&#039;t get what it needs.</description>
		<content:encoded><![CDATA[<p>Martin,<br />
You pose an interesting and important question: what happens when you don&#8217;t have high-performance team member(s) on your Scrum project. I have seen some teams that are not uniformly high-performing start off OK, get frustrated, and then look to the Scrum Master to resolve conflicts, which is iffy at best. When the Scrum Master remains neutral and doesn&#8217;t try to take on a leadership role,  a leader often emerges who ironically is not the one who talks the most or has the most experience. My preference is for a strong product owners to get the team members motivated because forgetting chickens and pigs,if the project goes awry, the organization (represented by the product owner) doesn&#8217;t get what it needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scrum vs. Waterfall: The Fight Continues by ElizabethLarson</title>
		<link>http://www.watermarklearning.com/blog/scrum-vs-waterfall-pt2/comment-page-1/#comment-368</link>
		<dc:creator>ElizabethLarson</dc:creator>
		<pubDate>Fri, 16 Jul 2010 17:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.watermarklearning.com/blog/?p=609#comment-368</guid>
		<description>Jeff,
Great ideas for successful projects, regardless of whether the approach taken is Waterfall or Agile! Thanks so much for writing in! I, too as a PM have found your tips invaluable. The one I should have used more was feedback. Respectful feedback among the team and stakeholders throughout the project would have been a benefit to us all. Again, great tips and thanks!
Elizabeth</description>
		<content:encoded><![CDATA[<p>Jeff,<br />
Great ideas for successful projects, regardless of whether the approach taken is Waterfall or Agile! Thanks so much for writing in! I, too as a PM have found your tips invaluable. The one I should have used more was feedback. Respectful feedback among the team and stakeholders throughout the project would have been a benefit to us all. Again, great tips and thanks!<br />
Elizabeth</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Five Tips for Estimating Requirements by ElizabethLarson</title>
		<link>http://www.watermarklearning.com/blog/estimating-requirements/comment-page-1/#comment-367</link>
		<dc:creator>ElizabethLarson</dc:creator>
		<pubDate>Fri, 16 Jul 2010 17:43:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.watermarklearning.com/blog/?p=209#comment-367</guid>
		<description>I&#039;m so glad you found this useful! Thanks so much for writing in.
Elziabeth</description>
		<content:encoded><![CDATA[<p>I&#8217;m so glad you found this useful! Thanks so much for writing in.<br />
Elziabeth</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scrum vs. Waterfall: The Fight Continues by Martin Schedlbauer</title>
		<link>http://www.watermarklearning.com/blog/scrum-vs-waterfall-pt2/comment-page-1/#comment-346</link>
		<dc:creator>Martin Schedlbauer</dc:creator>
		<pubDate>Wed, 14 Jul 2010 15:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.watermarklearning.com/blog/?p=609#comment-346</guid>
		<description>The issue is not where Scrum and Waterfall are similar, but how they accomplish their tasks and how likely they will succeed in that. Of course, both approaches need to prioritize requirements. The question really is: which ones is likely going to be successful. The waterfall approach of asking stakeholders to prioritize most of their requirements early in the project lifecycle often does not work in practice. The Scrum approach of doing the prioritization at the beginning of each spring is more likely to succeed. Scrum plans &quot;in the small&quot; which is more tangible, whereas waterfall tends to plan &quot;in the large&quot; which is often too abstract for many stakeholders.

Jeff&#039;s comments on &quot;team health&quot; is also important to consider. Good Scrum teams are those that are relatively small and consist of high performance individuals. An interesting question is the following: what happens when you have to staff a Scrum project with &quot;mediocre&quot; resources either because that is what your company has or because those are the only resource left. Now, those individuals may need more guidance, hand-holding, and &quot;management&quot; -- the hallmark of traditional project management.

Scrum requires &quot;willing and able&quot; resources (as well as co-location, strong product owners, etc.) if you don&#039;t have those, Scrum is less likely to succeed and more traditional &quot;performance management&quot; may have to be brought to bear.</description>
		<content:encoded><![CDATA[<p>The issue is not where Scrum and Waterfall are similar, but how they accomplish their tasks and how likely they will succeed in that. Of course, both approaches need to prioritize requirements. The question really is: which ones is likely going to be successful. The waterfall approach of asking stakeholders to prioritize most of their requirements early in the project lifecycle often does not work in practice. The Scrum approach of doing the prioritization at the beginning of each spring is more likely to succeed. Scrum plans &#8220;in the small&#8221; which is more tangible, whereas waterfall tends to plan &#8220;in the large&#8221; which is often too abstract for many stakeholders.</p>
<p>Jeff&#8217;s comments on &#8220;team health&#8221; is also important to consider. Good Scrum teams are those that are relatively small and consist of high performance individuals. An interesting question is the following: what happens when you have to staff a Scrum project with &#8220;mediocre&#8221; resources either because that is what your company has or because those are the only resource left. Now, those individuals may need more guidance, hand-holding, and &#8220;management&#8221; &#8212; the hallmark of traditional project management.</p>
<p>Scrum requires &#8220;willing and able&#8221; resources (as well as co-location, strong product owners, etc.) if you don&#8217;t have those, Scrum is less likely to succeed and more traditional &#8220;performance management&#8221; may have to be brought to bear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scrum vs. Waterfall: The Fight Continues by Jeff Gordon</title>
		<link>http://www.watermarklearning.com/blog/scrum-vs-waterfall-pt2/comment-page-1/#comment-295</link>
		<dc:creator>Jeff Gordon</dc:creator>
		<pubDate>Tue, 06 Jul 2010 18:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.watermarklearning.com/blog/?p=609#comment-295</guid>
		<description>I believe there is a fundamental differences which even the heavy hitters of agile never put their fingers on. This viewpoint was extracted from the writings of the early agile folks. In earlier years I developed high performance teams. What we found is that the relative &quot;health&quot; of the team was critical to our success. That health was dependent on a high degree of openness, trust, and recognition for each other&#039;s ideas as well as confidence that we were pursuing mutually benefical objectives. Recognition of each other&#039;s ideas was an indicator of how much openness and trust existed. Follow through and successful completion of assigned activities is another. A common understanding of the current state, baseline and shared vision of the future state was also most critical to the success of the group. Use of vehicles like sharepoint or a common area on a network for team materials in ongoing development for real time discussion and update is essential. We used meetings only when the group process was needed to resolve issues or make decisions. Everyone was trained in tools and techniques for systematic problem solving. Lastly; and most importantly, intensive feedback among all stakeholders, project members and users throughout the project. Treating each other&#039;s work with the utmost respect and the end user as the customer. What I am saying is that good old &quot;Performance Management&quot; avoids a ton of wasted time and gets a team to high quality results every time. Defining the Baseline and Future State. Setting measurable objectives and tasks, giving feedback throughout, and recognizing behaviors and results that contribute to project progress will get the team to success every time!</description>
		<content:encoded><![CDATA[<p>I believe there is a fundamental differences which even the heavy hitters of agile never put their fingers on. This viewpoint was extracted from the writings of the early agile folks. In earlier years I developed high performance teams. What we found is that the relative &#8220;health&#8221; of the team was critical to our success. That health was dependent on a high degree of openness, trust, and recognition for each other&#8217;s ideas as well as confidence that we were pursuing mutually benefical objectives. Recognition of each other&#8217;s ideas was an indicator of how much openness and trust existed. Follow through and successful completion of assigned activities is another. A common understanding of the current state, baseline and shared vision of the future state was also most critical to the success of the group. Use of vehicles like sharepoint or a common area on a network for team materials in ongoing development for real time discussion and update is essential. We used meetings only when the group process was needed to resolve issues or make decisions. Everyone was trained in tools and techniques for systematic problem solving. Lastly; and most importantly, intensive feedback among all stakeholders, project members and users throughout the project. Treating each other&#8217;s work with the utmost respect and the end user as the customer. What I am saying is that good old &#8220;Performance Management&#8221; avoids a ton of wasted time and gets a team to high quality results every time. Defining the Baseline and Future State. Setting measurable objectives and tasks, giving feedback throughout, and recognizing behaviors and results that contribute to project progress will get the team to success every time!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Five Tips for Estimating Requirements by PMP Project Management</title>
		<link>http://www.watermarklearning.com/blog/estimating-requirements/comment-page-1/#comment-266</link>
		<dc:creator>PMP Project Management</dc:creator>
		<pubDate>Wed, 30 Jun 2010 11:11:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.watermarklearning.com/blog/?p=209#comment-266</guid>
		<description>Just what I was looking for. I was searching for Project Management articles when I discovered this post on Yahoo. This is exactly what I was looking for. I&#039;ve bookmarked this post for future reference :-) Nice post - Cheers Lisa</description>
		<content:encoded><![CDATA[<p>Just what I was looking for. I was searching for Project Management articles when I discovered this post on Yahoo. This is exactly what I was looking for. I&#8217;ve bookmarked this post for future reference <img src='http://www.watermarklearning.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  Nice post &#8211; Cheers Lisa</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What&#8217;s On Your Sponsorship Short List? by Andrea Brockmeier</title>
		<link>http://www.watermarklearning.com/blog/getting-the-most-from-your-sponsor/comment-page-1/#comment-172</link>
		<dc:creator>Andrea Brockmeier</dc:creator>
		<pubDate>Tue, 08 Jun 2010 16:44:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.watermarklearning.com/blog/?p=527#comment-172</guid>
		<description>Thanks so much for the feedback and for including the article on your site.  I appreciate your interest!</description>
		<content:encoded><![CDATA[<p>Thanks so much for the feedback and for including the article on your site.  I appreciate your interest!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What&#8217;s On Your Sponsorship Short List? by PM Hut</title>
		<link>http://www.watermarklearning.com/blog/getting-the-most-from-your-sponsor/comment-page-1/#comment-134</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Tue, 01 Jun 2010 15:57:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.watermarklearning.com/blog/?p=527#comment-134</guid>
		<description>Hi Andrea,

This is an excellent article and I would like to publish on PM Hut. Please either email me or contact me through the &quot;Contact Us&quot; form on the PM Hut site in case you&#039;re OK with this.</description>
		<content:encoded><![CDATA[<p>Hi Andrea,</p>
<p>This is an excellent article and I would like to publish on PM Hut. Please either email me or contact me through the &#8220;Contact Us&#8221; form on the PM Hut site in case you&#8217;re OK with this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BA Centers of Excellence Blogisode 1: Why do you need Business Analysis Maturity?  OR… Welcome to my Planetoid! by Bob Prentiss</title>
		<link>http://www.watermarklearning.com/blog/ba-centers-of-excellence-blogisode/comment-page-1/#comment-59</link>
		<dc:creator>Bob Prentiss</dc:creator>
		<pubDate>Wed, 05 May 2010 15:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.watermarklearning.com/blog/?p=436#comment-59</guid>
		<description>Thank you for the reply!  Kathleen has been a leader in the BACOE arena for many years.  In fact, I read that article several years ago as I was first embarking on setting up my own BACOE where I worked at the time.  It is a great foundational article and everyone should definitely read it.  Some of the things that we will explore through my blogisodes though will shed some light on where theory stops and real life application starts.  There are many hidden things that only experience can tell us.  Things like cultural evaluation - determining how much of a BACOE is right for you and your organization.  It is simply not practical to implement everything.  Also, understanding how long the BACOE concept might be good for.  They actually can have a limited lifespan.  And much more.  Thanks again for sharing the article with us and look forward to more comments in the future!
Regards,
Bob</description>
		<content:encoded><![CDATA[<p>Thank you for the reply!  Kathleen has been a leader in the BACOE arena for many years.  In fact, I read that article several years ago as I was first embarking on setting up my own BACOE where I worked at the time.  It is a great foundational article and everyone should definitely read it.  Some of the things that we will explore through my blogisodes though will shed some light on where theory stops and real life application starts.  There are many hidden things that only experience can tell us.  Things like cultural evaluation &#8211; determining how much of a BACOE is right for you and your organization.  It is simply not practical to implement everything.  Also, understanding how long the BACOE concept might be good for.  They actually can have a limited lifespan.  And much more.  Thanks again for sharing the article with us and look forward to more comments in the future!<br />
Regards,<br />
Bob</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BA Centers of Excellence Blogisode 1: Why do you need Business Analysis Maturity?  OR… Welcome to my Planetoid! by Paskwa</title>
		<link>http://www.watermarklearning.com/blog/ba-centers-of-excellence-blogisode/comment-page-1/#comment-52</link>
		<dc:creator>Paskwa</dc:creator>
		<pubDate>Wed, 28 Apr 2010 16:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.watermarklearning.com/blog/?p=436#comment-52</guid>
		<description>Kathleen B. Hass, PMP, Richard Avery, Terry Longo, and Alice Zavala posted an interesting article about this in the IIBA St. Louis chapter website...I&#039;m reading it as I write this.

http://stlouis.theiiba.org/download/BACoE.pdf

Thanks,
Paskwa</description>
		<content:encoded><![CDATA[<p>Kathleen B. Hass, PMP, Richard Avery, Terry Longo, and Alice Zavala posted an interesting article about this in the IIBA St. Louis chapter website&#8230;I&#8217;m reading it as I write this.</p>
<p><a href="http://stlouis.theiiba.org/download/BACoE.pdf" rel="nofollow">http://stlouis.theiiba.org/download/BACoE.pdf</a></p>
<p>Thanks,<br />
Paskwa</p>
]]></content:encoded>
	</item>
</channel>
</rss>
