<?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: High Level Design Review Check-List</title>
	<atom:link href="http://blog.karmona.com/index.php/2009/12/12/high-level-design-review-check-list/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.karmona.com/index.php/2009/12/12/high-level-design-review-check-list/</link>
	<description>Pragmatic Software Management, Internet Trends, Life and more...</description>
	<lastBuildDate>Fri, 30 Jul 2010 19:50:36 +0300</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Moti Karmona &#124; מוטי קרמונה</title>
		<link>http://blog.karmona.com/index.php/2009/12/12/high-level-design-review-check-list/comment-page-1/#comment-186</link>
		<dc:creator>Moti Karmona &#124; מוטי קרמונה</dc:creator>
		<pubDate>Tue, 22 Dec 2009 18:26:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.karmona.com/?p=573#comment-186</guid>
		<description>You know it is very hard for me to admit but I think you are right... ;)</description>
		<content:encoded><![CDATA[<p>You know it is very hard for me to admit but I think you are right&#8230; ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gadi</title>
		<link>http://blog.karmona.com/index.php/2009/12/12/high-level-design-review-check-list/comment-page-1/#comment-178</link>
		<dc:creator>Gadi</dc:creator>
		<pubDate>Sun, 13 Dec 2009 17:46:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.karmona.com/?p=573#comment-178</guid>
		<description>Very comprehensive list! One thing I do feel is missing, however, is prioritization (of the features being reviewed, not of that list...). I think it&#039;s important to have the features to be implemented prioritized by the design review time, as this will at least mean someone had given thought to what&#039;s more important in the feature to be designed and implemented, and can also give context to the other parties involved (QA, Operations, etc.), guiding them where to focus and what to attend to first (and hopefully saving precious DR meeting time of arguing on the lowest priority aspects in the feature list).</description>
		<content:encoded><![CDATA[<p>Very comprehensive list! One thing I do feel is missing, however, is prioritization (of the features being reviewed, not of that list&#8230;). I think it&#8217;s important to have the features to be implemented prioritized by the design review time, as this will at least mean someone had given thought to what&#8217;s more important in the feature to be designed and implemented, and can also give context to the other parties involved (QA, Operations, etc.), guiding them where to focus and what to attend to first (and hopefully saving precious DR meeting time of arguing on the lowest priority aspects in the feature list).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
