<?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 in Under 10 Minutes (HD) by @hamids</title>
	<atom:link href="http://jobssoftware.com/blog/?feed=rss2&#038;p=10" rel="self" type="application/rss+xml" />
	<link>http://jobssoftware.com/blog/?p=10</link>
	<description>Blog on software development</description>
	<lastBuildDate>Mon, 30 Aug 2010 11:42:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: hshojaee</title>
		<link>http://jobssoftware.com/blog/?p=10&#038;cpage=1#comment-106</link>
		<dc:creator>hshojaee</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jobssoftware.com/blog/?p=10#comment-106</guid>
		<description>Armond, what&#039;s important is the information that is gathered from a daily standup, not the daily standup itself. If that information is already gathered in an efficient way (such as a small team that works in the same room and openly discusses everything throughout the day), there is no need for an additional meeting. DO NOT confuse my statement with thinking there is no need for the daily standup. If you don&#039;t have a better way of getting the info, the daily standup is the way to go.</description>
		<content:encoded><![CDATA[<p>Armond, what&#8217;s important is the information that is gathered from a daily standup, not the daily standup itself. If that information is already gathered in an efficient way (such as a small team that works in the same room and openly discusses everything throughout the day), there is no need for an additional meeting. DO NOT confuse my statement with thinking there is no need for the daily standup. If you don&#8217;t have a better way of getting the info, the daily standup is the way to go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cablop</title>
		<link>http://jobssoftware.com/blog/?p=10&#038;cpage=1#comment-107</link>
		<dc:creator>cablop</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jobssoftware.com/blog/?p=10#comment-107</guid>
		<description>Excellent, excellent, excellent video! Not only interesting, but assertive and fun!

There&#039;s just one bad point about it... it has to low volume... i barely could hear it :( except raising my speakers volume and hope nobody will nudge me on msn while having the speaker near my ear!</description>
		<content:encoded><![CDATA[<p>Excellent, excellent, excellent video! Not only interesting, but assertive and fun!</p>
<p>There&#8217;s just one bad point about it&#8230; it has to low volume&#8230; i barely could hear it <img src='http://jobssoftware.com/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  except raising my speakers volume and hope nobody will nudge me on msn while having the speaker near my ear!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CaptainMacNasty</title>
		<link>http://jobssoftware.com/blog/?p=10&#038;cpage=1#comment-108</link>
		<dc:creator>CaptainMacNasty</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jobssoftware.com/blog/?p=10#comment-108</guid>
		<description>Excellent video!  As for all the debates below, folks who have worked with MANY methodologies in MANY environments (including Agile/ Scrum/ AUP) know that any aspect of any methodology may be excluded from the project, provided there is justification for that exclusion, and understanding of the consequences.   Scrum is just as adaptable as other PM/ SDLC methodologies, since &quot;The Methodology isn&#039;t the Project&quot;, just as &quot;The Schedule isn&#039;t the Project&quot;.</description>
		<content:encoded><![CDATA[<p>Excellent video!  As for all the debates below, folks who have worked with MANY methodologies in MANY environments (including Agile/ Scrum/ AUP) know that any aspect of any methodology may be excluded from the project, provided there is justification for that exclusion, and understanding of the consequences.   Scrum is just as adaptable as other PM/ SDLC methodologies, since &#8220;The Methodology isn&#8217;t the Project&#8221;, just as &#8220;The Schedule isn&#8217;t the Project&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hammer92025</title>
		<link>http://jobssoftware.com/blog/?p=10&#038;cpage=1#comment-109</link>
		<dc:creator>hammer92025</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jobssoftware.com/blog/?p=10#comment-109</guid>
		<description>Hamid, 


Could you please address the reasons for dismissing the importance of DAILY scrum meetings? 

You do such a great job of explaining Scrum but then pour cold water on, what most people, consider to be a non-negotiable aspect of Scrum: the daily 15 minute stand-up meeting with the whole team. 

Sincerely,

-Armond</description>
		<content:encoded><![CDATA[<p>Hamid, </p>
<p>Could you please address the reasons for dismissing the importance of DAILY scrum meetings? </p>
<p>You do such a great job of explaining Scrum but then pour cold water on, what most people, consider to be a non-negotiable aspect of Scrum: the daily 15 minute stand-up meeting with the whole team. </p>
<p>Sincerely,</p>
<p>-Armond</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: izidave</title>
		<link>http://jobssoftware.com/blog/?p=10&#038;cpage=1#comment-110</link>
		<dc:creator>izidave</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jobssoftware.com/blog/?p=10#comment-110</guid>
		<description>Generally a good video, but I STRONGLY DISAGREE that daily scrum is optional.  Daily scrum meetings are MOST important.  Even if you work with remote developers you MUST do it every day (eg via Skype).  If you miss it when things are going well, you will be unable to call it when things go off track, then the whole process unravels.  Great video, just be sure to do DAILY scrum meetings/calls</description>
		<content:encoded><![CDATA[<p>Generally a good video, but I STRONGLY DISAGREE that daily scrum is optional.  Daily scrum meetings are MOST important.  Even if you work with remote developers you MUST do it every day (eg via Skype).  If you miss it when things are going well, you will be unable to call it when things go off track, then the whole process unravels.  Great video, just be sure to do DAILY scrum meetings/calls</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aprepo</title>
		<link>http://jobssoftware.com/blog/?p=10&#038;cpage=1#comment-111</link>
		<dc:creator>aprepo</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jobssoftware.com/blog/?p=10#comment-111</guid>
		<description>To clarify: I am not against burndowns, but saying that burndown chart == scrum is a bit... simplified.</description>
		<content:encoded><![CDATA[<p>To clarify: I am not against burndowns, but saying that burndown chart == scrum is a bit&#8230; simplified.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aprepo</title>
		<link>http://jobssoftware.com/blog/?p=10&#038;cpage=1#comment-112</link>
		<dc:creator>aprepo</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jobssoftware.com/blog/?p=10#comment-112</guid>
		<description>So, without burndown charts, you are not doing scrum? Burndown is a tool. It is not what scrum is about. All agile methodologies are pretty similar in core their core values and methods, since they all are based on the agile manifesto. There are several cases where the burndown does not bring much value.</description>
		<content:encoded><![CDATA[<p>So, without burndown charts, you are not doing scrum? Burndown is a tool. It is not what scrum is about. All agile methodologies are pretty similar in core their core values and methods, since they all are based on the agile manifesto. There are several cases where the burndown does not bring much value.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hshojaee</title>
		<link>http://jobssoftware.com/blog/?p=10&#038;cpage=1#comment-113</link>
		<dc:creator>hshojaee</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jobssoftware.com/blog/?p=10#comment-113</guid>
		<description>The burndown is probably the most important new aspect of software development that scrum brings to the table. All of the other concepts are found in a collection of other methodologies. Therefore, burndowns are the most important piece of scrum.</description>
		<content:encoded><![CDATA[<p>The burndown is probably the most important new aspect of software development that scrum brings to the table. All of the other concepts are found in a collection of other methodologies. Therefore, burndowns are the most important piece of scrum.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aprepo</title>
		<link>http://jobssoftware.com/blog/?p=10&#038;cpage=1#comment-114</link>
		<dc:creator>aprepo</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jobssoftware.com/blog/?p=10#comment-114</guid>
		<description>overemphasis on the burndown chart and silly dismissal of the importance of the daily standup meeting.</description>
		<content:encoded><![CDATA[<p>overemphasis on the burndown chart and silly dismissal of the importance of the daily standup meeting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: raghavan20</title>
		<link>http://jobssoftware.com/blog/?p=10&#038;cpage=1#comment-115</link>
		<dc:creator>raghavan20</dc:creator>
		<pubDate>Thu, 17 Dec 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jobssoftware.com/blog/?p=10#comment-115</guid>
		<description>excellent work mate! that was quick and clear. i had been seeing a few big presentations but it is good to see that you did not miss any important information. good job!</description>
		<content:encoded><![CDATA[<p>excellent work mate! that was quick and clear. i had been seeing a few big presentations but it is good to see that you did not miss any important information. good job!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
