<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.arquitecturadesoftware.org/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Agile Methods: Stand-up Meetings</title><link>http://www.arquitecturadesoftware.org/blogs/hugoribeiro/archive/2007/01/30/agile-methods-stand-up-meetings.aspx</link><description>Stand-up meetings are a very important part of Agile methodologies, Scrum in particular. This article by Martin Fowler focus on the most important aspects that should be considered in the organization of this kind of meetings. In particular, those aspects</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.2)</generator><item><title>re: Agile Methods: Stand-up Meetings</title><link>http://www.arquitecturadesoftware.org/blogs/hugoribeiro/archive/2007/01/30/agile-methods-stand-up-meetings.aspx#779</link><pubDate>Tue, 30 Jan 2007 19:22:01 GMT</pubDate><guid isPermaLink="false">f91c5163-993a-4ad3-b0c6-9418870e089f:779</guid><dc:creator>João Pedro Martins</dc:creator><description>&lt;p&gt;Interestingly, I've had very similar experiences to this one. &amp;nbsp;When the PM/Scrum Master or Architect was present, devs tended to talk at them, and not to the rest of the team. Other times the devs work in very different and specific areas, so what they have to say isn't really very relevant to the rest of the team. This may help explain the &amp;quot;obligation&amp;quot; feeling you describe. Also very important is trying to keep this meeting short and directed.&lt;/p&gt;
&lt;p&gt;On the upside, I've seen team members themselves speak to control the topics discussed or the duration of the meetings, which means they adhered to the approach.&lt;/p&gt;
&lt;p&gt;I think education is vital in this whole &amp;quot;empowering&amp;quot; process. Team members have to &amp;quot;buy&amp;quot; into the approach, and they have to feel they make a difference and can have a real contribution to the end product, that they are not only executants.&lt;/p&gt;
</description></item><item><title>re: Agile Methods: Stand-up Meetings</title><link>http://www.arquitecturadesoftware.org/blogs/hugoribeiro/archive/2007/01/30/agile-methods-stand-up-meetings.aspx#781</link><pubDate>Wed, 31 Jan 2007 14:22:54 GMT</pubDate><guid isPermaLink="false">f91c5163-993a-4ad3-b0c6-9418870e089f:781</guid><dc:creator>hgr</dc:creator><description>&lt;p&gt;Jota:&lt;/p&gt;
&lt;p&gt;I couldn't agree more with your last paragraph. I really think that's the main question: participants need to feel that their words make some difference in the project evolution. And that's why the PM/Master becomes an issue. It's hard for someone to talk now as a peer to someone that 15 minutes later is his boss again. May be the solution is to appoint a Scrum-master that is actually a &amp;quot;regular&amp;quot; team member.&lt;/p&gt;
</description></item><item><title>transientis.com - A succession of transient moods  &amp;raquo; Blog Archive   &amp;raquo; Scrum - experiences from a scrum master and a pig - part 1</title><link>http://www.arquitecturadesoftware.org/blogs/hugoribeiro/archive/2007/01/30/agile-methods-stand-up-meetings.aspx#798</link><pubDate>Sat, 03 Feb 2007 16:42:56 GMT</pubDate><guid isPermaLink="false">f91c5163-993a-4ad3-b0c6-9418870e089f:798</guid><dc:creator>transientis.com - A succession of transient moods  » Blog Archive   » Scrum - experiences from a scrum master and a pig - part 1</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://transientis.com/2007/02/scrum-experiences-from-a-scrum-master-and-a-pig-part-1/"&gt;http://transientis.com/2007/02/scrum-experiences-from-a-scrum-master-and-a-pig-part-1/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>