<?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 on: Scrum Alliance Reflux</title>
	<atom:link href="http://blog.coryfoy.com/2010/02/scrum-alliance-reflux/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.coryfoy.com/2010/02/scrum-alliance-reflux/</link>
	<description>It&#039;s all about delivering</description>
	<lastBuildDate>Fri, 03 Feb 2012 07:28:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Phil Ruse</title>
		<link>http://blog.coryfoy.com/2010/02/scrum-alliance-reflux/comment-page-1/#comment-995</link>
		<dc:creator>Phil Ruse</dc:creator>
		<pubDate>Wed, 03 Mar 2010 12:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coryfoy.com/?p=660#comment-995</guid>
		<description>This was a really great read. I&#039;m on the outside looking in but nonetheless am following the development of scrum with great interest - who knows maybe one day I&#039;ll actually get to be agile rather than just hear about it?

Are you saying then that SA should provide the framework and then concentrate on specific (and a limited number of) &#039;verticals&#039; (such as software development) and how to implement in those environments in greater detail? Would each of these &#039;verticals&#039; evolve independently and/or do you  envisage a point where they would inevitably &#039;merge&#039;. Or do you see evolution in different directions - albeit with common ancestry?

Sorry for all the questions!</description>
		<content:encoded><![CDATA[<p>This was a really great read. I&#8217;m on the outside looking in but nonetheless am following the development of scrum with great interest &#8211; who knows maybe one day I&#8217;ll actually get to be agile rather than just hear about it?</p>
<p>Are you saying then that SA should provide the framework and then concentrate on specific (and a limited number of) &#8216;verticals&#8217; (such as software development) and how to implement in those environments in greater detail? Would each of these &#8216;verticals&#8217; evolve independently and/or do you  envisage a point where they would inevitably &#8216;merge&#8217;. Or do you see evolution in different directions &#8211; albeit with common ancestry?</p>
<p>Sorry for all the questions!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ilja Preuß</title>
		<link>http://blog.coryfoy.com/2010/02/scrum-alliance-reflux/comment-page-1/#comment-994</link>
		<dc:creator>Ilja Preuß</dc:creator>
		<pubDate>Tue, 02 Mar 2010 15:41:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coryfoy.com/?p=660#comment-994</guid>
		<description>Cory, thanks for the clarification! I agree that helping people adopting Scrum by helping them to see which changes in running und organizing a business are necessary would be a good goal.

I&#039;m not sure we are so far that the SA is in position to *define* and *teach* those changes. Seems to me that  supporting ideas and building communities where ideas are developed, exchanged, tested, scrutinized, etc. might be the best that can be done right now. And I would love to see that happen!</description>
		<content:encoded><![CDATA[<p>Cory, thanks for the clarification! I agree that helping people adopting Scrum by helping them to see which changes in running und organizing a business are necessary would be a good goal.</p>
<p>I&#8217;m not sure we are so far that the SA is in position to *define* and *teach* those changes. Seems to me that  supporting ideas and building communities where ideas are developed, exchanged, tested, scrutinized, etc. might be the best that can be done right now. And I would love to see that happen!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cory Foy</title>
		<link>http://blog.coryfoy.com/2010/02/scrum-alliance-reflux/comment-page-1/#comment-993</link>
		<dc:creator>Cory Foy</dc:creator>
		<pubDate>Tue, 02 Mar 2010 11:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coryfoy.com/?p=660#comment-993</guid>
		<description>Thanks Ilja. My point is that I created the CFmera, and I don&#039;t offer a manual, or workshops, on what you need to change. Some of my company&#039;s instructors happen to be very good, and so slip in their own tips, but it isn&#039;t consistent. 

My new CFmera isn&#039;t about a slightly different control. It&#039;s about fundamentally altering your identity as a photographer. You still have to know some basics (framing) but even those have changed slightly (you don&#039;t have to wait to have all of the picture framed just right before starting to take the picture). 

But you&#039;re right - analogies only go so far. Scrum isn&#039;t the one to blame here. All I&#039;m saying is that if we aren&#039;t looking for ways to /modify/ Scrum (which has been pretty clear) then it would seem like the Scrum Alliance&#039;s goal should be to help people /adopt/ it. 

And if we&#039;re about helping the adoption, then we need to help with the organizational change part. It&#039;s very similar to the CSD efforts - you could create a &quot;Certified Scrum Developer&quot; program which was a class where someone learned about TDD, small stories, Simple Design, etc. But if they go back to their jobs and are still measured on how many lines of code they right and how fast they get the crap out of the door; and every one of the other developers are working 10, 12, 16 hour days - what&#039;s the point?

It goes back to Jesse&#039;s comment. Would a CSD class be, or is the CSM class, worthwhile? Sure. People would see an improvement in what they are doing. An incremental improvement. But if we&#039;re really going to &quot;transform the world of work&quot;; if we&#039;re /really/ going to tell everyone that by adopting Scrum, or XP, or Lean, or &quot;Agile&quot; you&#039;ll see faster releases, higher quality and more money - we&#039;ve got to see an effort to change the fundamental way we teach people how to run and organize business. 

If the Scrum Alliance is doing *that* then imagine the impact we could see in the entire software community. That could be truly amazing. Instead we have to bicker about whether someone taking a two-day CSM class should have to take an exam. And, to me, that&#039;s just sad.</description>
		<content:encoded><![CDATA[<p>Thanks Ilja. My point is that I created the CFmera, and I don&#8217;t offer a manual, or workshops, on what you need to change. Some of my company&#8217;s instructors happen to be very good, and so slip in their own tips, but it isn&#8217;t consistent. </p>
<p>My new CFmera isn&#8217;t about a slightly different control. It&#8217;s about fundamentally altering your identity as a photographer. You still have to know some basics (framing) but even those have changed slightly (you don&#8217;t have to wait to have all of the picture framed just right before starting to take the picture). </p>
<p>But you&#8217;re right &#8211; analogies only go so far. Scrum isn&#8217;t the one to blame here. All I&#8217;m saying is that if we aren&#8217;t looking for ways to /modify/ Scrum (which has been pretty clear) then it would seem like the Scrum Alliance&#8217;s goal should be to help people /adopt/ it. </p>
<p>And if we&#8217;re about helping the adoption, then we need to help with the organizational change part. It&#8217;s very similar to the CSD efforts &#8211; you could create a &#8220;Certified Scrum Developer&#8221; program which was a class where someone learned about TDD, small stories, Simple Design, etc. But if they go back to their jobs and are still measured on how many lines of code they right and how fast they get the crap out of the door; and every one of the other developers are working 10, 12, 16 hour days &#8211; what&#8217;s the point?</p>
<p>It goes back to Jesse&#8217;s comment. Would a CSD class be, or is the CSM class, worthwhile? Sure. People would see an improvement in what they are doing. An incremental improvement. But if we&#8217;re really going to &#8220;transform the world of work&#8221;; if we&#8217;re /really/ going to tell everyone that by adopting Scrum, or XP, or Lean, or &#8220;Agile&#8221; you&#8217;ll see faster releases, higher quality and more money &#8211; we&#8217;ve got to see an effort to change the fundamental way we teach people how to run and organize business. </p>
<p>If the Scrum Alliance is doing *that* then imagine the impact we could see in the entire software community. That could be truly amazing. Instead we have to bicker about whether someone taking a two-day CSM class should have to take an exam. And, to me, that&#8217;s just sad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ilja Preuß</title>
		<link>http://blog.coryfoy.com/2010/02/scrum-alliance-reflux/comment-page-1/#comment-992</link>
		<dc:creator>Ilja Preuß</dc:creator>
		<pubDate>Tue, 02 Mar 2010 07:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coryfoy.com/?p=660#comment-992</guid>
		<description>Cory, the camery is an interesting analogy. I have a slightly different perspective on it, though:

A camera is just a tool. No photographer should expect a camera making him a better photographer. Sure, a company might sell a camera that gives you exceptional control over how to take photos. It might give you some new kind of helpful feedback, or some suggestions. But in the end it&#039;s the responsibility of the photographer to learn how to use that information to make good photos. And a successful photographer will probably have done it by not just reading the camera&#039;s manual and/or taking some workshops. He will have looked at the work of other photographers, got in contact with a community, and practiced for years and years.</description>
		<content:encoded><![CDATA[<p>Cory, the camery is an interesting analogy. I have a slightly different perspective on it, though:</p>
<p>A camera is just a tool. No photographer should expect a camera making him a better photographer. Sure, a company might sell a camera that gives you exceptional control over how to take photos. It might give you some new kind of helpful feedback, or some suggestions. But in the end it&#8217;s the responsibility of the photographer to learn how to use that information to make good photos. And a successful photographer will probably have done it by not just reading the camera&#8217;s manual and/or taking some workshops. He will have looked at the work of other photographers, got in contact with a community, and practiced for years and years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Pietri</title>
		<link>http://blog.coryfoy.com/2010/02/scrum-alliance-reflux/comment-page-1/#comment-990</link>
		<dc:creator>William Pietri</dc:creator>
		<pubDate>Mon, 01 Mar 2010 17:09:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coryfoy.com/?p=660#comment-990</guid>
		<description>Wow, Cory. I&#039;m sorry for your esophagus, but I hope this doesn&#039;t die. As an outsider to the whole Scrum thing, it&#039;s exciting to see somebody internal holding the Scrum Alliance to account, and demanding results that match the hype.

The whole notion that it&#039;s ok to take something that could make teams wildly better and settle for &quot;a little bit better&quot; is bullshit of the highest order. It&#039;s a great way for lazy CSTs and consultants to make a pile of money, but it results in a classic tragedy of the commons: everybody ends up thinking that Agile only gets you &quot;a little bit better&quot;, and having tried it once, they may never try again.

So thanks for speaking up on this.</description>
		<content:encoded><![CDATA[<p>Wow, Cory. I&#8217;m sorry for your esophagus, but I hope this doesn&#8217;t die. As an outsider to the whole Scrum thing, it&#8217;s exciting to see somebody internal holding the Scrum Alliance to account, and demanding results that match the hype.</p>
<p>The whole notion that it&#8217;s ok to take something that could make teams wildly better and settle for &#8220;a little bit better&#8221; is bullshit of the highest order. It&#8217;s a great way for lazy CSTs and consultants to make a pile of money, but it results in a classic tragedy of the commons: everybody ends up thinking that Agile only gets you &#8220;a little bit better&#8221;, and having tried it once, they may never try again.</p>
<p>So thanks for speaking up on this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Fewell</title>
		<link>http://blog.coryfoy.com/2010/02/scrum-alliance-reflux/comment-page-1/#comment-989</link>
		<dc:creator>Jesse Fewell</dc:creator>
		<pubDate>Mon, 01 Mar 2010 15:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coryfoy.com/?p=660#comment-989</guid>
		<description>Good stuff, Cory. We can disagree about the breadth/depth thing, but I sense that we&#039;re getting to some passionate agreement around helping people with the details and implications of this stuff. In particular, even if the SA focuses only on &quot;transforming the world of software&quot;, we still need way more detailed resources on how to go about the transforming part.

So, at the risk of making you vomit, I&#039;ll put a fork in this one for now. Instead, I&#039;ll go add some more stuff into my Scrum curriculum about the CFmera.

Cheers, 
-jesse</description>
		<content:encoded><![CDATA[<p>Good stuff, Cory. We can disagree about the breadth/depth thing, but I sense that we&#8217;re getting to some passionate agreement around helping people with the details and implications of this stuff. In particular, even if the SA focuses only on &#8220;transforming the world of software&#8221;, we still need way more detailed resources on how to go about the transforming part.</p>
<p>So, at the risk of making you vomit, I&#8217;ll put a fork in this one for now. Instead, I&#8217;ll go add some more stuff into my Scrum curriculum about the CFmera.</p>
<p>Cheers,<br />
-jesse</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Gregory</title>
		<link>http://blog.coryfoy.com/2010/02/scrum-alliance-reflux/comment-page-1/#comment-987</link>
		<dc:creator>Tim Gregory</dc:creator>
		<pubDate>Mon, 01 Mar 2010 13:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coryfoy.com/?p=660#comment-987</guid>
		<description>Nice post Cory. Spot on.
I think that the SA has to face their critics head-on, and soon. Withdrawing from the conversation to focus on Scrum Gatherings is not the way forward.
Perhaps the answer is simple - start prescribing some development and management practices that fit well with Scrum?
The Nokia Test is pretty good at rooting out whether the processes that you need to run alongside scrum are in place, and some of these should probably be folded into the core of the process.</description>
		<content:encoded><![CDATA[<p>Nice post Cory. Spot on.<br />
I think that the SA has to face their critics head-on, and soon. Withdrawing from the conversation to focus on Scrum Gatherings is not the way forward.<br />
Perhaps the answer is simple &#8211; start prescribing some development and management practices that fit well with Scrum?<br />
The Nokia Test is pretty good at rooting out whether the processes that you need to run alongside scrum are in place, and some of these should probably be folded into the core of the process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Dempsey</title>
		<link>http://blog.coryfoy.com/2010/02/scrum-alliance-reflux/comment-page-1/#comment-986</link>
		<dc:creator>Robert Dempsey</dc:creator>
		<pubDate>Mon, 01 Mar 2010 12:18:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coryfoy.com/?p=660#comment-986</guid>
		<description>You&#039;ve hit the nail on the head with this post Cory. The implications that Scrum has on an organization are wide ranging. The transparency and visibility it brings for project and everyone involved in them can be risky for some people, especially if they&#039;ve been floating along in their organization, not rocking the boat, just doing the minimum, or not even that.

I believe that to be more successful implementing Scrum, it needs to become less risky and more palatable for the people involved. We need to get top-down buy in and support, and it needs to be publicly stated.

Also we need to start gathering many more metrics on projects (post coming on that today) so we can show solid improvements in the business.

Also, everyone that is fanatical about what is and isn&#039;t &quot;agile&quot; needs to stop doing that. I remember when Chad Fowler told the Ruby on Rails community to stop being a bunch of jerks so the community could grow. I think the same needs to happen here. I understand branding, but seriously, the &quot;you&#039;re not doing agile if you aren&#039;t doing [blah]&quot; needs to stop. If you&#039;re adhering to Agile principles and working to improve, then who cares? Only people trying to make money on selling the mythical silver bullet.</description>
		<content:encoded><![CDATA[<p>You&#8217;ve hit the nail on the head with this post Cory. The implications that Scrum has on an organization are wide ranging. The transparency and visibility it brings for project and everyone involved in them can be risky for some people, especially if they&#8217;ve been floating along in their organization, not rocking the boat, just doing the minimum, or not even that.</p>
<p>I believe that to be more successful implementing Scrum, it needs to become less risky and more palatable for the people involved. We need to get top-down buy in and support, and it needs to be publicly stated.</p>
<p>Also we need to start gathering many more metrics on projects (post coming on that today) so we can show solid improvements in the business.</p>
<p>Also, everyone that is fanatical about what is and isn&#8217;t &#8220;agile&#8221; needs to stop doing that. I remember when Chad Fowler told the Ruby on Rails community to stop being a bunch of jerks so the community could grow. I think the same needs to happen here. I understand branding, but seriously, the &#8220;you&#8217;re not doing agile if you aren&#8217;t doing [blah]&#8221; needs to stop. If you&#8217;re adhering to Agile principles and working to improve, then who cares? Only people trying to make money on selling the mythical silver bullet.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

