<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://xpday.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Master Classes and Breakout Sessions Track</title>
 <link>http://xpday.org/taxonomy/term/9</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>Writing on the Walls</title>
 <link>http://xpday.org/node/136</link>
 <description>&lt;p&gt;How is your project doing ? How long does it take to find out what&amp;#8217;s going on? 
Where is the essential information? Is it hidden, squirreled away inside thousand-line code 
files, spreadsheets and Word documents ? Or is it “in your face”, shown where you can&amp;#8217;t 
help but see it every day ? A successful project isn&amp;#8217;t successful because the team makes 
no mistakes, or suffers no setbacks. Whether your project sinks or swims is determined 
not by circumstance but by the speed and quality of your team&amp;#8217;s response. This tutorial 
presents simple techniques to make project status visible early and continuously, so a 
team can respond effectively. The techniques can be implemented with simple office tools: 
flipcharts, markers and yellow stickies.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/2007_call&quot; class=&quot;og_links&quot;&gt;XP Day 7 - Call for Proposals&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://xpday.org/node/136&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://xpday.org/taxonomy/term/9">Master Classes and Breakout Sessions Track</category>
 <enclosure url="http://xpday.org/files/ProjectStatusWritingOnTheWalls.pdf" length="61062" type="application/pdf" />
 <group domain="http://xpday.org/2007_call">XP Day 7 - Call for Proposals</group>
 <pubDate>Tue, 31 Jul 2007 18:29:15 +0100</pubDate>
 <dc:creator>Emmanuel Gaillot</dc:creator>
 <guid isPermaLink="false">136 at http://xpday.org</guid>
</item>
<item>
 <title>The Informed Coding Dojo</title>
 <link>http://xpday.org/node/122</link>
 <description>&lt;p&gt;The majority of coding dojos are run using reasonably well known langauges such as Java.  While this allows relatively complex problems to be solved, it also allows participants to take relatively large steps and get away with it.  This dojo uses the same format as that created by Laurent Bossavit and Emmanuel Gaillot, but is aimed at reinforcing the idea of taking baby steps.  This is achieved by using a language we hope is not known to the participants.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/2007_call&quot; class=&quot;og_links&quot;&gt;XP Day 7 - Call for Proposals&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://xpday.org/node/122&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://xpday.org/taxonomy/term/9">Master Classes and Breakout Sessions Track</category>
 <group domain="http://xpday.org/2007_call">XP Day 7 - Call for Proposals</group>
 <pubDate>Mon, 30 Jul 2007 16:29:10 +0100</pubDate>
 <dc:creator>karls</dc:creator>
 <guid isPermaLink="false">122 at http://xpday.org</guid>
</item>
</channel>
</rss>
