<?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 agilethinking.net Blog</title>
	<atom:link href="http://agilethinking.net/blog/index.php/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://agilethinking.net/blog</link>
	<description>Tobias Mayer's Blog</description>
	<lastBuildDate>Fri, 27 May 2011 13:57:11 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on When is Scrum not Scrum? by webdesigner</title>
		<link>http://agilethinking.net/blog/2007/02/21/when-is-scrum-not-scrum/comment-page-2/#comment-186224</link>
		<dc:creator>webdesigner</dc:creator>
		<pubDate>Fri, 27 May 2011 13:57:11 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2007/02/21/when-is-scrum-not-scrum/#comment-186224</guid>
		<description>that list looks really good</description>
		<content:encoded><![CDATA[<p>that list looks really good</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Essence of Scrum by Essence of Scrum &#171; CONSCIRES AGILE PRACTICES</title>
		<link>http://agilethinking.net/blog/2009/04/06/essence-of-scrum/comment-page-1/#comment-168990</link>
		<dc:creator>Essence of Scrum &#171; CONSCIRES AGILE PRACTICES</dc:creator>
		<pubDate>Sun, 19 Sep 2010 05:12:42 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/essence-of-scrum/#comment-168990</guid>
		<description>[...]   This article titled as &#8220;Essence of Scrum&#8221; was originally published by Tobias Mayer at Agilethinking.net on April 6, 2009 and this version is adapted by David [...]</description>
		<content:encoded><![CDATA[<p>[...]   This article titled as &#8220;Essence of Scrum&#8221; was originally published by Tobias Mayer at Agilethinking.net on April 6, 2009 and this version is adapted by David [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Shock Therapy&#8230; or Compassion? by Danielle Rousseau</title>
		<link>http://agilethinking.net/blog/2008/09/15/shock-therapy-or-compassion/comment-page-1/#comment-166238</link>
		<dc:creator>Danielle Rousseau</dc:creator>
		<pubDate>Sun, 04 Jul 2010 18:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2008/09/15/shock-therapy-or-compassion/#comment-166238</guid>
		<description>You mention not being able to evaluate metrics of those who use them. One very straightforward approach is to simply question the assumptions that form the basis of the &quot;metrics&quot;. Are they modernist and reductionist (e.g.. who is in their study, and who is excluded who might &quot;muddy&quot; the waters), or are they inclusive of all who have the same problem. What are the time frames of testing results, and what are the tests being used? Are such tests valid and reliable, and again, in what time frame? 
You mention anecdotal evidence (&quot;gut feeling&quot;) can be substantiated  - and is in the literature. Look at DBT from BehaviorTech (although they also use behavioural means, they are most often compassion based.) Paul Gilbert, In Compassion Focused Therapy, makes a case for compassion. You might check on his metrics, too.
In any case, make the distinction between the qualitative and quantitative analysis. Distinguishing between cure and healing, the time frame of the improvement, the actual definition of compliance or commitment, the therapy used, etc. will give you  lot of assumptive bases to explore. That speaks to your response to April about metrics, I think. Let me know and warm wishes. - Danielle</description>
		<content:encoded><![CDATA[<p>You mention not being able to evaluate metrics of those who use them. One very straightforward approach is to simply question the assumptions that form the basis of the &#8220;metrics&#8221;. Are they modernist and reductionist (e.g.. who is in their study, and who is excluded who might &#8220;muddy&#8221; the waters), or are they inclusive of all who have the same problem. What are the time frames of testing results, and what are the tests being used? Are such tests valid and reliable, and again, in what time frame?<br />
You mention anecdotal evidence (&#8221;gut feeling&#8221;) can be substantiated  &#8211; and is in the literature. Look at DBT from BehaviorTech (although they also use behavioural means, they are most often compassion based.) Paul Gilbert, In Compassion Focused Therapy, makes a case for compassion. You might check on his metrics, too.<br />
In any case, make the distinction between the qualitative and quantitative analysis. Distinguishing between cure and healing, the time frame of the improvement, the actual definition of compliance or commitment, the therapy used, etc. will give you  lot of assumptive bases to explore. That speaks to your response to April about metrics, I think. Let me know and warm wishes. &#8211; Danielle</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scaling Scrum: the alcoholic perspective by Dan Schaeffer</title>
		<link>http://agilethinking.net/blog/2008/04/09/scaling-scrum-the-alcoholic-perspective/comment-page-1/#comment-160581</link>
		<dc:creator>Dan Schaeffer</dc:creator>
		<pubDate>Sat, 06 Feb 2010 21:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2008/04/09/scaling-scrum-the-alcoholic-perspective/#comment-160581</guid>
		<description>I think what this is missing has been been touched upon by Christina.  The person who asks that question is channeling her manager.  The questioner may have utter faith in the ability of the scrum framework to arrive at a solution but she knows her organization will not make space for the framework to do its job without some sort of guarantee that it will succeed.  It&#039;s dandy to say that a self-organized team will empirically create a process that will enable a large project to be estimated but it would be a much easier sell if you could point to an example of how that worked elsewhere.

In my line of work we build and sell expensive instruments for analyical chemists that are driven by large software data systems (3-4 million lines of code).  These systems have to control and optimize the instrument, store and analyze the data for 30 different applications, enforce security policies for provenance of the data, enable distributed data processing, and produce all manner of different printed reports.  When my manager says to me &quot;How long will it take us to move all of our existing functionality from the Mac to the PC and what will it cost?&quot; all I can say to him is that I need to convene a scrum team of 7 people and we will self-organize into a team that will develop an empirical process which will iterate toward an estimate.  While that may be the most honest answer, you&#039;re not likely going to be asked to do the job.  It would be far better to be able to say &quot;This is the process by which one scrum team managed to deploy scrum across a group of 28 developers and delivered a product of similar magnitude in 3 years.  If you&#039;ll allow me to form a team, I&#039;m sure we can empirically create a process process that will enable us to give you an estimate.&quot;</description>
		<content:encoded><![CDATA[<p>I think what this is missing has been been touched upon by Christina.  The person who asks that question is channeling her manager.  The questioner may have utter faith in the ability of the scrum framework to arrive at a solution but she knows her organization will not make space for the framework to do its job without some sort of guarantee that it will succeed.  It&#8217;s dandy to say that a self-organized team will empirically create a process that will enable a large project to be estimated but it would be a much easier sell if you could point to an example of how that worked elsewhere.</p>
<p>In my line of work we build and sell expensive instruments for analyical chemists that are driven by large software data systems (3-4 million lines of code).  These systems have to control and optimize the instrument, store and analyze the data for 30 different applications, enforce security policies for provenance of the data, enable distributed data processing, and produce all manner of different printed reports.  When my manager says to me &#8220;How long will it take us to move all of our existing functionality from the Mac to the PC and what will it cost?&#8221; all I can say to him is that I need to convene a scrum team of 7 people and we will self-organize into a team that will develop an empirical process which will iterate toward an estimate.  While that may be the most honest answer, you&#8217;re not likely going to be asked to do the job.  It would be far better to be able to say &#8220;This is the process by which one scrum team managed to deploy scrum across a group of 28 developers and delivered a product of similar magnitude in 3 years.  If you&#8217;ll allow me to form a team, I&#8217;m sure we can empirically create a process process that will enable us to give you an estimate.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scrum: its place in the world by La esencia de Scrum - Tobias Mayer &#124; Aplicando Scrum</title>
		<link>http://agilethinking.net/blog/2008/09/26/scrum-its-place-in-the-world/comment-page-1/#comment-160455</link>
		<dc:creator>La esencia de Scrum - Tobias Mayer &#124; Aplicando Scrum</dc:creator>
		<pubDate>Wed, 03 Feb 2010 13:57:13 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2008/09/26/scrum-its-place-in-the-world/#comment-160455</guid>
		<description>[...] referencias: Scrum: its place in the world Scrum for Software Development   [...]</description>
		<content:encoded><![CDATA[<p>[...] referencias: Scrum: its place in the world Scrum for Software Development   [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scaling Scrum: the alcoholic perspective by Scrum 4 You &#8212; News of the week &#124; Blogs and more</title>
		<link>http://agilethinking.net/blog/2008/04/09/scaling-scrum-the-alcoholic-perspective/comment-page-1/#comment-158574</link>
		<dc:creator>Scrum 4 You &#8212; News of the week &#124; Blogs and more</dc:creator>
		<pubDate>Mon, 11 Jan 2010 11:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2008/04/09/scaling-scrum-the-alcoholic-perspective/#comment-158574</guid>
		<description>[...] Scrum the alcoholic perspective, Tobias Mayer [...]</description>
		<content:encoded><![CDATA[<p>[...] Scrum the alcoholic perspective, Tobias Mayer [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PMI at the Scrum Gathering — a footnote by PMI to Keynote Another Agile Conference</title>
		<link>http://agilethinking.net/blog/2009/04/08/pmi-at-the-scrum-gathering-a-footnote/comment-page-1/#comment-158300</link>
		<dc:creator>PMI to Keynote Another Agile Conference</dc:creator>
		<pubDate>Fri, 08 Jan 2010 22:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2009/04/08/pmi-at-the-scrum-gathering-a-footnote/#comment-158300</guid>
		<description>[...] Orlando 2009 this past May. At that event, Ballestrero&#8217;s unifying remarks, and his one-on-one conversations with Agile sketpics, facilitated some very real collaboration between the PMI and Agile communities through some [...]</description>
		<content:encoded><![CDATA[<p>[...] Orlando 2009 this past May. At that event, Ballestrero&#8217;s unifying remarks, and his one-on-one conversations with Agile sketpics, facilitated some very real collaboration between the PMI and Agile communities through some [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Oppression, Revolution and the Future of Scrum — #2 by Bob Davis</title>
		<link>http://agilethinking.net/blog/2009/03/16/oppression-revolution-and-the-future-of-scrum-%e2%80%94-2/comment-page-1/#comment-156929</link>
		<dc:creator>Bob Davis</dc:creator>
		<pubDate>Tue, 22 Dec 2009 19:45:46 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2009/03/16/oppression-revolution-and-the-future-of-scrum-%e2%80%94-2/#comment-156929</guid>
		<description>Interesting discussions and great comments.  Some of the arguments/comments are difficult to respond to when they seem to be framed so tightly as to only be able to allo only the answer that a person is looking for.  Perhaps I need to dust off my philosophy hat and wear it more but for now I&#039;m content to think and absorb.  

I&#039;m a PMP and have to manage different projects using different &#039;styles&#039; based upon the need, complexity, and product to be delivered.  To assume that, as a PMP, I have all the tools necessary to &#039;develop/build everything&#039; would be proof that I wasn&#039;t paying attention when I was learning about PM.  As someone said in an earlier post, PMI does not deal with how the work is to be done, but in how to manage the process to ensure a greater possibility of success.  How the work is to be done is really dependent upon the nature of the project and the team. Just as I wouldn&#039;t use every tool in my toolbox to drive a wood screw, every tool/process in the PMBOX is not appropriate for all projects.

In our development efforts we&#039;re attempting to use more &#039;agile&#039; methodologies while working in an environment (government) that wants to see everything planned out prior to releasing funding and before work can begin.  Since we&#039;re spending other peoples money there&#039;s wisdom in the approach but only to a point.  My current view is that agile methodologies can be applied most effectively in the execution and control portions of a project where the actual work is accomplished while the appropriate PMI methodologies for the project can be effectively applied in the initiating, planning, and closeout portions of the project.  

This approach may be overly simplistic to many but I&#039;m open to learn.  Thanks for the time.</description>
		<content:encoded><![CDATA[<p>Interesting discussions and great comments.  Some of the arguments/comments are difficult to respond to when they seem to be framed so tightly as to only be able to allo only the answer that a person is looking for.  Perhaps I need to dust off my philosophy hat and wear it more but for now I&#8217;m content to think and absorb.  </p>
<p>I&#8217;m a PMP and have to manage different projects using different &#8217;styles&#8217; based upon the need, complexity, and product to be delivered.  To assume that, as a PMP, I have all the tools necessary to &#8216;develop/build everything&#8217; would be proof that I wasn&#8217;t paying attention when I was learning about PM.  As someone said in an earlier post, PMI does not deal with how the work is to be done, but in how to manage the process to ensure a greater possibility of success.  How the work is to be done is really dependent upon the nature of the project and the team. Just as I wouldn&#8217;t use every tool in my toolbox to drive a wood screw, every tool/process in the PMBOX is not appropriate for all projects.</p>
<p>In our development efforts we&#8217;re attempting to use more &#8216;agile&#8217; methodologies while working in an environment (government) that wants to see everything planned out prior to releasing funding and before work can begin.  Since we&#8217;re spending other peoples money there&#8217;s wisdom in the approach but only to a point.  My current view is that agile methodologies can be applied most effectively in the execution and control portions of a project where the actual work is accomplished while the appropriate PMI methodologies for the project can be effectively applied in the initiating, planning, and closeout portions of the project.  </p>
<p>This approach may be overly simplistic to many but I&#8217;m open to learn.  Thanks for the time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scale Back: Small is Beautiful by Curso de Scrum de Tobias Mayer en Buenos Aires - Angel &#34;Java&#34; Lopez</title>
		<link>http://agilethinking.net/blog/2008/08/18/scale-back-small-is-beautiful/comment-page-1/#comment-156170</link>
		<dc:creator>Curso de Scrum de Tobias Mayer en Buenos Aires - Angel &#34;Java&#34; Lopez</dc:creator>
		<pubDate>Mon, 14 Dec 2009 17:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2008/08/18/scale-back-small-is-beautiful/#comment-156170</guid>
		<description>[...] Scale Back: Small is Beautiful — Agile2008 session [...]</description>
		<content:encoded><![CDATA[<p>[...] Scale Back: Small is Beautiful — Agile2008 session [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scrum: its place in the world by Tales from the Scrum: La esencia de Scrum</title>
		<link>http://agilethinking.net/blog/2008/09/26/scrum-its-place-in-the-world/comment-page-1/#comment-155989</link>
		<dc:creator>Tales from the Scrum: La esencia de Scrum</dc:creator>
		<pubDate>Sat, 12 Dec 2009 17:51:49 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2008/09/26/scrum-its-place-in-the-world/#comment-155989</guid>
		<description>[...] referencias: Scrum: its place in the world  [...]</description>
		<content:encoded><![CDATA[<p>[...] referencias: Scrum: its place in the world  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.300 seconds -->

