<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/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>Tools for Agility - A white paper by Kent Beck</title><link>http://blogs.msdn.com/jeffbe/archive/2008/07/05/tools-for-agility-a-white-paper-by-kent-beck.aspx</link><description>Ajoy Krishnamoorthy , a product manager on our team, recently worked with Kent Beck to publish a great white paper on tooling for the agile team. The section on transparency really resonated with me especially this passage: A transparent team can more</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Tools for Agility - A white paper by Kent Beck</title><link>http://blogs.msdn.com/jeffbe/archive/2008/07/05/tools-for-agility-a-white-paper-by-kent-beck.aspx#8693556</link><pubDate>Sat, 05 Jul 2008 17:21:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8693556</guid><dc:creator>Peter Ritchie</dc:creator><description>&lt;p&gt;I think transparency is a cornerstone of Agile. &amp;nbsp;Agile promotes better communication with the customer. &amp;nbsp;Hiding behind a vale of secrecy means you're not communicating with the customer is many ways.&lt;/p&gt;
&lt;p&gt;I think transparency allows customers to &amp;quot;talk&amp;quot; to the development team--talking to them about what they want, not telling them what to do because the team is nebulous.&lt;/p&gt;
&lt;p&gt;Innovation and experimentation can come out this communication; but I don't think it falls out of simply being agile. &amp;nbsp;Effectiveness and efficiency are improved through Agile; but projects only get more effective and more efficient through transparency because of this increased communicability.&lt;/p&gt;
&lt;p&gt;I would say that a team saying they can't detail what they're doing because it would slow them down isn't truly agile--they're not communicating effectively with the customer. &amp;nbsp;Agile isn't simply an excuse to avoid the traditional artifacts that aren't the software deliverables...&lt;/p&gt;
</description></item><item><title>re: Tools for Agility - A white paper by Kent Beck</title><link>http://blogs.msdn.com/jeffbe/archive/2008/07/05/tools-for-agility-a-white-paper-by-kent-beck.aspx#8700485</link><pubDate>Mon, 07 Jul 2008 09:06:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8700485</guid><dc:creator>Carl</dc:creator><description>&lt;p&gt;Transparency goes beyond the team members' communicating to management and outsiders. &amp;nbsp;It involves telling your fellow developers what you're doing; putting UML diagrams on a Wiki or white board to show what your code is going to look like and how it'll behave and regular, tested commits of code.&lt;/p&gt;
</description></item></channel></rss>