<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.developerdotstar.com/community" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>developer.* Blogs - Design Reviews - Best Practices - Comments</title>
 <link>http://www.developerdotstar.com/community/node/680</link>
 <description>Comments for &quot;Design Reviews - Best Practices&quot;</description>
 <language>en</language>
<item>
 <title>Design Reviews - Best Practices</title>
 <link>http://www.developerdotstar.com/community/node/680</link>
 <description>&lt;p&gt;A lot of people would agree that design reviews can bring a lot of value to building quality software. However, when it comes to actually doing a design review we enter a somewhat blurry environment where everybody has another view on what a design is, how in-depth it should be etc, how it should be organised, etc.&lt;br /&gt;
Based on my own experience, I want to share some tips and best practices with you...&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.developerdotstar.com/community/node/680&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.developerdotstar.com/community/node/680#comment</comments>
 <category domain="http://www.developerdotstar.com/community/taxonomy/term/140">Object Oriented Design and Programming</category>
 <pubDate>Tue, 19 Dec 2006 11:00:38 -0800</pubDate>
 <dc:creator>Mario Van Damme</dc:creator>
 <guid isPermaLink="false">680 at http://www.developerdotstar.com/community</guid>
</item>
</channel>
</rss>
