<?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: How to Give a Great Sprint Demo</title>
	<atom:link href="http://www.richardlawrence.info/2009/04/24/how-to-give-a-great-sprint-demo/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.richardlawrence.info/2009/04/24/how-to-give-a-great-sprint-demo/</link>
	<description>On making software teams happier and more productive</description>
	<lastBuildDate>Fri, 03 Feb 2012 10:41:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Prakash</title>
		<link>http://www.richardlawrence.info/2009/04/24/how-to-give-a-great-sprint-demo/comment-page-1/#comment-28</link>
		<dc:creator>Prakash</dc:creator>
		<pubDate>Tue, 09 Mar 2010 22:54:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardlawrence.info/?p=161#comment-28</guid>
		<description>I like the demo but with a pinch of salt, with my experience, the &quot;demo day&quot; is huge overhead  time spend in the project.

-Preparing the software for demo
-Practicing for the demo (as per you)
-Sometimes preparing special hardware for the demostration purpose only.

All this shows ok, the software works as per the PBI.

having a functional software every sprint end is not always realistic, sometimes a software needs refactoring or &quot;break all bones before rebuilding&quot; all that does not happen in a sprint time and in such cases software are not in a demonstrable state.

The only people who are happy with the demos are the product managers who likes to see nice nice thing all the time.

Peer engineers knows the problem and would rather would like to spend time on getting the software working rather then spend time demostrating and preparing for demos.

all in all, with all the software processes i have gone through, i find the scrum process to be very cumberson one.

The process is not really agile, the only part of aglity is ability to be prepared for a change in spec. otherwise, Scrum is not really an interesting process.</description>
		<content:encoded><![CDATA[<p>I like the demo but with a pinch of salt, with my experience, the &#8220;demo day&#8221; is huge overhead  time spend in the project.</p>
<p>-Preparing the software for demo<br />
-Practicing for the demo (as per you)<br />
-Sometimes preparing special hardware for the demostration purpose only.</p>
<p>All this shows ok, the software works as per the PBI.</p>
<p>having a functional software every sprint end is not always realistic, sometimes a software needs refactoring or &#8220;break all bones before rebuilding&#8221; all that does not happen in a sprint time and in such cases software are not in a demonstrable state.</p>
<p>The only people who are happy with the demos are the product managers who likes to see nice nice thing all the time.</p>
<p>Peer engineers knows the problem and would rather would like to spend time on getting the software working rather then spend time demostrating and preparing for demos.</p>
<p>all in all, with all the software processes i have gone through, i find the scrum process to be very cumberson one.</p>
<p>The process is not really agile, the only part of aglity is ability to be prepared for a change in spec. otherwise, Scrum is not really an interesting process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ellen Gottesdiener</title>
		<link>http://www.richardlawrence.info/2009/04/24/how-to-give-a-great-sprint-demo/comment-page-1/#comment-27</link>
		<dc:creator>Ellen Gottesdiener</dc:creator>
		<pubDate>Thu, 30 Jul 2009 10:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardlawrence.info/?p=161#comment-27</guid>
		<description>Great tips Richard, thanks!

Another suggestion: have the customer/product owner &quot;run&quot; the demo him or herself.

thanks for your blogging!
~ ellen</description>
		<content:encoded><![CDATA[<p>Great tips Richard, thanks!</p>
<p>Another suggestion: have the customer/product owner &#8220;run&#8221; the demo him or herself.</p>
<p>thanks for your blogging!<br />
~ ellen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.richardlawrence.info/2009/04/24/how-to-give-a-great-sprint-demo/comment-page-1/#comment-20</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Thu, 30 Apr 2009 01:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardlawrence.info/?p=161#comment-20</guid>
		<description>@Steven - Thanks for the kind words. I agree, there&#039;s no reason you have to choose between exciting and entertaining and relevant and informative. The most relevant and informative demos ought to also be the most exciting, assuming you&#039;re really building a valuable product.

@Bob - Good point. I like to rotate the demo role around the team usually. But one interesting case I saw was a team where the Product Owner did the demos. The demo wasn&#039;t the team showing her what they built--it was her showing the rest of the stakeholders what *her team* built.</description>
		<content:encoded><![CDATA[<p>@Steven &#8211; Thanks for the kind words. I agree, there&#8217;s no reason you have to choose between exciting and entertaining and relevant and informative. The most relevant and informative demos ought to also be the most exciting, assuming you&#8217;re really building a valuable product.</p>
<p>@Bob &#8211; Good point. I like to rotate the demo role around the team usually. But one interesting case I saw was a team where the Product Owner did the demos. The demo wasn&#8217;t the team showing her what they built&#8211;it was her showing the rest of the stakeholders what *her team* built.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Hartman</title>
		<link>http://www.richardlawrence.info/2009/04/24/how-to-give-a-great-sprint-demo/comment-page-1/#comment-19</link>
		<dc:creator>Bob Hartman</dc:creator>
		<pubDate>Mon, 27 Apr 2009 16:34:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardlawrence.info/?p=161#comment-19</guid>
		<description>[...] Oh, and while we’re on the topic, if you want to know how to have a great demo, read this blog entry.  It has some awesome ideas that all teams should try to follow.  The only thing I would add is to have someone other than a developer or tester be able to try the software during the demo.  Too many horror stories about how things were missed when developers went through demos too fast! [...]</description>
		<content:encoded><![CDATA[<p>[...] Oh, and while we’re on the topic, if you want to know how to have a great demo, read this blog entry.  It has some awesome ideas that all teams should try to follow.  The only thing I would add is to have someone other than a developer or tester be able to try the software during the demo.  Too many horror stories about how things were missed when developers went through demos too fast! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven M. Smith</title>
		<link>http://www.richardlawrence.info/2009/04/24/how-to-give-a-great-sprint-demo/comment-page-1/#comment-18</link>
		<dc:creator>Steven M. Smith</dc:creator>
		<pubDate>Sun, 26 Apr 2009 00:25:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardlawrence.info/?p=161#comment-18</guid>
		<description>Excellent advice written with style and grace.

I especially like the idea of an exciting and entertaining demo, which, contrary to some people&#039;s opinion, can still be relevant and informative.

I also like your advice about the importance of practice. Any presentation, which is what a demo is, benefits from practice.

Nice work, Richard. I like your writing a lot.</description>
		<content:encoded><![CDATA[<p>Excellent advice written with style and grace.</p>
<p>I especially like the idea of an exciting and entertaining demo, which, contrary to some people&#8217;s opinion, can still be relevant and informative.</p>
<p>I also like your advice about the importance of practice. Any presentation, which is what a demo is, benefits from practice.</p>
<p>Nice work, Richard. I like your writing a lot.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

