<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (DennisLaumen)</title>
    <link>https://pinboard.in/u:DennisLaumen/public/</link>
    <description>recent bookmarks from DennisLaumen</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://martinfowler.com/articles/itsNotJustStandingUp.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://martinfowler.com/articles/itsNotJustStandingUp.html">
    <title>It's Not Just Standing Up: Patterns of Daily Stand-up Meetings</title>
    <dc:date>2010-09-10T07:42:11+00:00</dc:date>
    <link>http://martinfowler.com/articles/itsNotJustStandingUp.html</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[The daily stand-up meeting (also known as a "daily scrum", a "daily huddle", a "morning roll-call", etc.) is simple to describe: the whole team meets every day for a quick status update.  We stand up to keep the meeting short.  That's it.  But this short definition does not really tell you the subtle details that distinguish a good stand-up from a bad one.

Given the apparent simplicity of stand-ups, I was quite surprised the first time I saw one that wasn't working. It was immediately obvious to me what was wrong but I realised that it was not obvious to the team. I realised that my team was not aware  of the underlying principles and details that would allowed them to diagnose and solve problems with stand-ups.

People who have experienced good stand-ups will generally know what can be done when things aren't working well. For novice stand-up attendees, when things go wrong, it is much less likely that they'll figure out what to do. One way to approach this issue is to claim that it's all a matter of tacit knowledge and novices just need to attend more well-run stand-ups. I believe, however, that it's much more likely that given no assistance, novices will simply abandon the practice of daily stand-ups. This would be unfortunate since well-run stand-ups add significant value to projects.

This is my attempt to communicate some of the previously tacit knowledge on the benefits and consequences of common practices for daily stand-ups. These patterns of daily stand-up meetings are intended to help new practitioners as well as remind experienced practitioners of what they might already know in their gut. ]]></description>
<dc:subject>standupmeetings scrum jasonyip martinfowler</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:5f3c5b116974/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:standupmeetings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:jasonyip"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:martinfowler"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>