<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Code Reviews &#8211; Mandatory but Ad-Hoc?</title>
	<atom:link href="http://www.klocwork.com/blog/2010/03/code-reviews-mandatory-but-ad-hoc/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.klocwork.com/blog/2010/03/code-reviews-mandatory-but-ad-hoc/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=code-reviews-mandatory-but-ad-hoc</link>
	<description>&#62;kloctalk is a blog and a community for software development professionals who create and maintain mission-critical software and the challenges they face on a daily basis.</description>
	<lastBuildDate>Tue, 24 Jan 2012 14:57:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Developers think code reviews are great&#8230; what? &#124; &#62;kloctalk</title>
		<link>http://www.klocwork.com/blog/2010/03/code-reviews-mandatory-but-ad-hoc/comment-page-1/#comment-2415</link>
		<dc:creator>Developers think code reviews are great&#8230; what? &#124; &#62;kloctalk</dc:creator>
		<pubDate>Tue, 01 Jun 2010 15:33:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=936#comment-2415</guid>
		<description>[...] professionals a whole bunch of questions related to code reviews (some of which we&#8217;ve referenced before) and here are two interesting data points that suggest developers see real benefits from code [...]</description>
		<content:encoded><![CDATA[<p>[...] professionals a whole bunch of questions related to code reviews (some of which we&#8217;ve referenced before) and here are two interesting data points that suggest developers see real benefits from code [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: laurance</title>
		<link>http://www.klocwork.com/blog/2010/03/code-reviews-mandatory-but-ad-hoc/comment-page-1/#comment-1916</link>
		<dc:creator>laurance</dc:creator>
		<pubDate>Tue, 30 Mar 2010 04:12:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=936#comment-1916</guid>
		<description>Hello from England! I have found your domain on alltheweb. Good content! Mary J. Hamilton x</description>
		<content:encoded><![CDATA[<p>Hello from England! I have found your domain on alltheweb. Good content! Mary J. Hamilton x</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Harrison</title>
		<link>http://www.klocwork.com/blog/2010/03/code-reviews-mandatory-but-ad-hoc/comment-page-1/#comment-1800</link>
		<dc:creator>Brendan Harrison</dc:creator>
		<pubDate>Fri, 19 Mar 2010 12:47:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=936#comment-1800</guid>
		<description>Good points Gregg, thanks for chiming in. The last point about more structure = more resistance is an interesting one... embracing a more unstructured approach with some tool and easy workflow support is an approach many organizations seem to be taking.</description>
		<content:encoded><![CDATA[<p>Good points Gregg, thanks for chiming in. The last point about more structure = more resistance is an interesting one&#8230; embracing a more unstructured approach with some tool and easy workflow support is an approach many organizations seem to be taking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregg Sporar</title>
		<link>http://www.klocwork.com/blog/2010/03/code-reviews-mandatory-but-ad-hoc/comment-page-1/#comment-1781</link>
		<dc:creator>Gregg Sporar</dc:creator>
		<pubDate>Thu, 18 Mar 2010 17:32:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.klocwork.com/blog/?p=936#comment-1781</guid>
		<description>&quot;Shouldn&#039;t who reviews the code be pretty important?&quot;

Yes, but... it&#039;s frequently not that simple.  For some teams that we&#039;ve worked with, there are subject matter experts whose inclusion is required but that does not mean they are the *only* members of the team allowed on the review.

For some teams, only one member of the group of subject matter experts is required and there is flexibility as to which specific member is assigned to any particular review.  That provides a way to do a bit of load balancing.

And then for other teams, they prefer a wide open approach because too much structure will generate resistance to the idea of doing code review at all.

So there is no one size fits all rule.</description>
		<content:encoded><![CDATA[<p>&#8220;Shouldn&#8217;t who reviews the code be pretty important?&#8221;</p>
<p>Yes, but&#8230; it&#8217;s frequently not that simple.  For some teams that we&#8217;ve worked with, there are subject matter experts whose inclusion is required but that does not mean they are the *only* members of the team allowed on the review.</p>
<p>For some teams, only one member of the group of subject matter experts is required and there is flexibility as to which specific member is assigned to any particular review.  That provides a way to do a bit of load balancing.</p>
<p>And then for other teams, they prefer a wide open approach because too much structure will generate resistance to the idea of doing code review at all.</p>
<p>So there is no one size fits all rule.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

