<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet title="XSL formatting" type="text/xsl" href="http://blog.netapsys.fr/index.php/feed/rss2/xslt" ?><rss version="2.0"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Netapsys Blog - Tag - not dispersed</title>
  <link>http://blog.netapsys.fr/index.php/</link>
  <atom:link href="http://blog.netapsys.fr/index.php/feed/tag/not%20dispersed/rss2" rel="self" type="application/rss+xml"/>
  <description></description>
  <language>fr</language>
  <pubDate>Wed, 08 Feb 2012 20:39:38 +0100</pubDate>
  <copyright>Netapsys 2008 - 2011</copyright>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Dotclear</generator>
  
    
  <item>
    <title>Stand-up meeting : (Not?) to do lists</title>
    <link>http://blog.netapsys.fr/index.php/post/2008/04/04/Stand-up-meeting-%3A</link>
    <guid isPermaLink="false">urn:md5:3cebdeb17afe30f8e83f4c6b26dc3a84</guid>
    <pubDate>Fri, 04 Apr 2008 14:50:00 +0200</pubDate>
    <dc:creator>Can Atac</dc:creator>
        <category>Méthodologies et bonnes pratiques</category>
        <category>diverse</category><category>high quality software</category><category>highly demanding customer</category><category>last minute problems</category><category>low budgets</category><category>low commitment</category><category>many bugs</category><category>no tools</category><category>no visibility</category><category>not dispersed</category><category>project</category><category>small team</category>    
    <description>&lt;p&gt;&lt;strong&gt;Context :&lt;/strong&gt;
Project, small team, diverse, not dispersed, highly demanding customer, high quality software&lt;/p&gt;


&lt;p&gt;&lt;strong&gt;Problem :&lt;/strong&gt;
No visibility, last minute problems, low commitment (not necessarily real but perceived as such), no tools, low budgets, high maintenance charge&lt;/p&gt;


&lt;p&gt;&lt;strong&gt;Solution :&lt;/strong&gt;
Among other techniques, stand-up meeting is being seen as an effective way to increase commitment and supporting among teams. Jason Yip (ThoughtWorks, Inc) points out some situations that could prevent this meeting be highly efficient (more details in &lt;a href=&quot;http://martinfowler.com/articles/itsNotJustStandingUp.html&quot; hreflang=&quot;en&quot;&gt;&lt;/a&gt;&lt;a href=&quot;http://martinfowler.com/articles/itsNotJustStandingUp.html&quot; hreflang=&quot;en&quot;&gt;Martin Fowler’s web site&lt;/a&gt;).&lt;br /&gt;
It is said that team members should not :&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Let the problems hidden;&lt;/li&gt;
&lt;li&gt;Invite people not directly involved in;&lt;/li&gt;
&lt;li&gt;Drag the meeting out;&lt;/li&gt;
&lt;li&gt;Have short memory.&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;    &lt;p&gt;More Details and Quotes :


1 - Let the problems hidden


“When people are knocked down every time they raise a problem, they will tend to stop raising problems. Beyond preventing removal of obstacles, a non-supportive stand-up works against team dynamics.”

We need to encourage people to raise problems, instead of hiding them. This would put an... &lt;a href=&quot;http://blog.netapsys.fr/index.php/post/2008/04/04/Stand-up-meeting-%3A&quot;&gt;&lt;em&gt;Lire&lt;/em&gt; Stand-up meeting : (Not?) to do lists&lt;/a&gt;&lt;/p&gt;</description>
    
    
    
          <comments>http://blog.netapsys.fr/index.php/post/2008/04/04/Stand-up-meeting-%3A#comment-form</comments>
      <wfw:comment>http://blog.netapsys.fr/index.php/post/2008/04/04/Stand-up-meeting-%3A#comment-form</wfw:comment>
      <wfw:commentRss>http://blog.netapsys.fr/index.php/feed/atom/comments/11</wfw:commentRss>
      </item>
    
</channel>
</rss>
