<?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: Doneness!</title>
	<atom:link href="http://www.armedia.com/blog/2010/02/doneness/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.armedia.com/blog/2010/02/doneness/</link>
	<description>Armedia Blog</description>
	<lastBuildDate>Thu, 29 Jul 2010 16:32:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Jimmy Nasr</title>
		<link>http://www.armedia.com/blog/2010/02/doneness/comment-page-1/#comment-90</link>
		<dc:creator>Jimmy Nasr</dc:creator>
		<pubDate>Thu, 11 Feb 2010 14:41:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.armedia.com/blog/?p=300#comment-90</guid>
		<description>Thanks for the comment Bill. You are right about quality needing to be a part of the company culture. Getting lax on process though is an easy trap to fall into--generally falling into the &quot;we don&#039;t have time for this!&quot; or lip-service category. I think an area companies need to pay a lot more attention to is providing valuable and in-context incentives for people to truly adhere to these processes; the reverse is also true of course...see Freakonomics.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Bill. You are right about quality needing to be a part of the company culture. Getting lax on process though is an easy trap to fall into&#8211;generally falling into the &#8220;we don&#8217;t have time for this!&#8221; or lip-service category. I think an area companies need to pay a lot more attention to is providing valuable and in-context incentives for people to truly adhere to these processes; the reverse is also true of course&#8230;see Freakonomics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill</title>
		<link>http://www.armedia.com/blog/2010/02/doneness/comment-page-1/#comment-86</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Wed, 10 Feb 2010 14:19:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.armedia.com/blog/?p=300#comment-86</guid>
		<description>You touched a nerve.  One of my pet peeves with myself and others is not being thorough and complete.  No matter how good you are at your work, or how long you have done it, you will have blind spots, make mistakes, and leave holes - sometimes big ones.  That is why the review process is so very important.  It&#039;s purpose is to make the project deliverable - data flow, code, documentation, whatever is being handed to the customer, as complete as is humanly possible. Everyone has a stake in success.  

Years ago I worked on a project team along side one of the Big 5 consulting firms.  I was lead on a project &quot;module,&quot; and one of my jobs was to review the design and code that the consultants produced.  In one review I discovered over 130 defects in code that was supposedly ready for user testing. I wish I could say the consultants learned from their mistakes and the project completed successfully.  However, this so-called Big 5 consultancy was very consistent in their lack of quality control.  The project failed and literally ended up on pallets, to be hauled off the business property.  Millions of dollars, and years were wasted, and professional reputations were ruined.  

Quality and consistency are supported by good process, but process is not enough. It has to be part of the company&#039;s culture.  It is uncommon to find individual consultants in one company as committed to professionalism and quality as Armedia&#039;s are.</description>
		<content:encoded><![CDATA[<p>You touched a nerve.  One of my pet peeves with myself and others is not being thorough and complete.  No matter how good you are at your work, or how long you have done it, you will have blind spots, make mistakes, and leave holes &#8211; sometimes big ones.  That is why the review process is so very important.  It&#8217;s purpose is to make the project deliverable &#8211; data flow, code, documentation, whatever is being handed to the customer, as complete as is humanly possible. Everyone has a stake in success.  </p>
<p>Years ago I worked on a project team along side one of the Big 5 consulting firms.  I was lead on a project &#8220;module,&#8221; and one of my jobs was to review the design and code that the consultants produced.  In one review I discovered over 130 defects in code that was supposedly ready for user testing. I wish I could say the consultants learned from their mistakes and the project completed successfully.  However, this so-called Big 5 consultancy was very consistent in their lack of quality control.  The project failed and literally ended up on pallets, to be hauled off the business property.  Millions of dollars, and years were wasted, and professional reputations were ruined.  </p>
<p>Quality and consistency are supported by good process, but process is not enough. It has to be part of the company&#8217;s culture.  It is uncommon to find individual consultants in one company as committed to professionalism and quality as Armedia&#8217;s are.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
