<?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: Customer Connected Engineering</title>
	<atom:link href="http://shapingsoftware.com/2009/05/19/customer-connected-engineering/feed/" rel="self" type="application/rss+xml" />
	<link>http://shapingsoftware.com/2009/05/19/customer-connected-engineering/</link>
	<description>Patterns and Practices for Software Success.</description>
	<pubDate>Thu, 17 May 2012 20:36:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: JD</title>
		<link>http://shapingsoftware.com/2009/05/19/customer-connected-engineering/comment-page-1/#comment-54085</link>
		<dc:creator>JD</dc:creator>
		<pubDate>Tue, 16 Jun 2009 06:32:53 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2009/05/19/customer-connected-engineering/#comment-54085</guid>
		<description>@ Robert

"Do you want one" is a nice, concise test.  I like it.</description>
		<content:encoded><![CDATA[<p>@ Robert</p>
<p>&#8220;Do you want one&#8221; is a nice, concise test.  I like it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RobertSeviour</title>
		<link>http://shapingsoftware.com/2009/05/19/customer-connected-engineering/comment-page-1/#comment-54066</link>
		<dc:creator>RobertSeviour</dc:creator>
		<pubDate>Mon, 15 Jun 2009 21:49:32 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2009/05/19/customer-connected-engineering/#comment-54066</guid>
		<description>Hi folks,

This thread centers on a pet peeve - that people invest tons of time, money and hope in projects which fail because what they (the inventor) believe is the golden future is not recognised as such by the market. 
The surest way to get quality feedback is to try and sell the product. If you ask someone, 'Do you want one?', you'll quickly know what's great and what stinks.

My article on this topic, with example:  &lt;a href="http://seviourbooks.com/articles/classic-inventors-mistake.htm/" rel="nofollow"&gt;- A classic inventor's mistake&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Hi folks,</p>
<p>This thread centers on a pet peeve - that people invest tons of time, money and hope in projects which fail because what they (the inventor) believe is the golden future is not recognised as such by the market.<br />
The surest way to get quality feedback is to try and sell the product. If you ask someone, &#8216;Do you want one?&#8217;, you&#8217;ll quickly know what&#8217;s great and what stinks.</p>
<p>My article on this topic, with example:  <a href="http://seviourbooks.com/articles/classic-inventors-mistake.htm/" rel="nofollow">- A classic inventor&#8217;s mistake</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Good Links, May 25, 2009 &#171; Emad&#8217;s Weblog</title>
		<link>http://shapingsoftware.com/2009/05/19/customer-connected-engineering/comment-page-1/#comment-53174</link>
		<dc:creator>Good Links, May 25, 2009 &#171; Emad&#8217;s Weblog</dc:creator>
		<pubDate>Mon, 25 May 2009 21:37:20 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2009/05/19/customer-connected-engineering/#comment-53174</guid>
		<description>[...] Posted by emadmagdy on May 25, 2009  Customers Connected Engineering (CCE): It is a way to build software with customers engaged in all phases of the Software development life cycle. its aim is “Software Built with customers, for customers”&#160; http://shapingsoftware.com/2009/05/19/customer-connected-engineering/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Posted by emadmagdy on May 25, 2009  Customers Connected Engineering (CCE): It is a way to build software with customers engaged in all phases of the Software development life cycle. its aim is “Software Built with customers, for customers”&#160; <a href="http://shapingsoftware.com/2009/05/19/customer-connected-engineering/" rel="nofollow">http://shapingsoftware.com/2009/05/19/customer-connected-engineering/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JD</title>
		<link>http://shapingsoftware.com/2009/05/19/customer-connected-engineering/comment-page-1/#comment-52789</link>
		<dc:creator>JD</dc:creator>
		<pubDate>Wed, 20 May 2009 06:41:38 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2009/05/19/customer-connected-engineering/#comment-52789</guid>
		<description>@ Andy

Good stuff.  I like your precision around "self validate."

I agree that projects fail when there's not enough customer connection.  Too many unchecked assumptions stretched over too long is a recipe for failure.

That's a great way to summarize it - "CCE uses customers to test and measure the effectiveness of your product early and often."

@ Henk

Thank you.  I'm a fan of standing on the shoulder's of giants and lifting others up.</description>
		<content:encoded><![CDATA[<p>@ Andy</p>
<p>Good stuff.  I like your precision around &#8220;self validate.&#8221;</p>
<p>I agree that projects fail when there&#8217;s not enough customer connection.  Too many unchecked assumptions stretched over too long is a recipe for failure.</p>
<p>That&#8217;s a great way to summarize it - &#8220;CCE uses customers to test and measure the effectiveness of your product early and often.&#8221;</p>
<p>@ Henk</p>
<p>Thank you.  I&#8217;m a fan of standing on the shoulder&#8217;s of giants and lifting others up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henk</title>
		<link>http://shapingsoftware.com/2009/05/19/customer-connected-engineering/comment-page-1/#comment-52763</link>
		<dc:creator>Henk</dc:creator>
		<pubDate>Tue, 19 May 2009 22:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2009/05/19/customer-connected-engineering/#comment-52763</guid>
		<description>Thank you 

Your contribution to the community with the variety of topics are extremely valuable and you provide such a refreshing sense of direction among complex chaos.

Keep up the good work, I am sure I speak for many when I say that you are an incredible human being.

Henk</description>
		<content:encoded><![CDATA[<p>Thank you </p>
<p>Your contribution to the community with the variety of topics are extremely valuable and you provide such a refreshing sense of direction among complex chaos.</p>
<p>Keep up the good work, I am sure I speak for many when I say that you are an incredible human being.</p>
<p>Henk</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Eunson</title>
		<link>http://shapingsoftware.com/2009/05/19/customer-connected-engineering/comment-page-1/#comment-52755</link>
		<dc:creator>Andy Eunson</dc:creator>
		<pubDate>Tue, 19 May 2009 20:25:04 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2009/05/19/customer-connected-engineering/#comment-52755</guid>
		<description>Everyone's immediate response should be one of the following.
a. "hell yeah"
b. "amen"
c. "duh!" - my personal favorite
d. All of the above

At its essence this is saying "you have to ask customers what is valuable to them". (you can add your own 'duh' here).

I've been a consultant for 16 years with over 30 customers. What I've seen and learned is that when any producer (software, hardware, books - anything consumer driven) runs off and builds without involving customers throughout the production life cycle their efforts typically fail miserably.

Why would guidance or guidance frameworks be any different?

The whole WORLD is focused on being able to deliver more value at a lower cost.

I'm pretty sure that there's a consensus that fixing problems earlier  is easier and far cheaper than later.

Involving the customer is how you do it.

Doesn't TQM, XP, agile and the plethora of project management knowledge all incorporate some level of identifying what the customer values? hell yeah

I like how CCE formalizes the customer involvement. Everyone has a tendency to "self-valdiate" through intellection and minimize the need for human interaction (something about geek tendencies towards introversion). This manifests itself as "I know what's important, I'll just go ahead and create it and when people see it they'll see that I'm smart and wonderful". The road to ruin.

We see this most evident in perf and scale. People spend massive amounts of time focused on thinking about what might be the problem and never test/measure. This is the exact same issue.

CCE uses customers to test and measure the effectiveness of your product early and often.

Amen!</description>
		<content:encoded><![CDATA[<p>Everyone&#8217;s immediate response should be one of the following.<br />
a. &#8220;hell yeah&#8221;<br />
b. &#8220;amen&#8221;<br />
c. &#8220;duh!&#8221; - my personal favorite<br />
d. All of the above</p>
<p>At its essence this is saying &#8220;you have to ask customers what is valuable to them&#8221;. (you can add your own &#8216;duh&#8217; here).</p>
<p>I&#8217;ve been a consultant for 16 years with over 30 customers. What I&#8217;ve seen and learned is that when any producer (software, hardware, books - anything consumer driven) runs off and builds without involving customers throughout the production life cycle their efforts typically fail miserably.</p>
<p>Why would guidance or guidance frameworks be any different?</p>
<p>The whole WORLD is focused on being able to deliver more value at a lower cost.</p>
<p>I&#8217;m pretty sure that there&#8217;s a consensus that fixing problems earlier  is easier and far cheaper than later.</p>
<p>Involving the customer is how you do it.</p>
<p>Doesn&#8217;t TQM, XP, agile and the plethora of project management knowledge all incorporate some level of identifying what the customer values? hell yeah</p>
<p>I like how CCE formalizes the customer involvement. Everyone has a tendency to &#8220;self-valdiate&#8221; through intellection and minimize the need for human interaction (something about geek tendencies towards introversion). This manifests itself as &#8220;I know what&#8217;s important, I&#8217;ll just go ahead and create it and when people see it they&#8217;ll see that I&#8217;m smart and wonderful&#8221;. The road to ruin.</p>
<p>We see this most evident in perf and scale. People spend massive amounts of time focused on thinking about what might be the problem and never test/measure. This is the exact same issue.</p>
<p>CCE uses customers to test and measure the effectiveness of your product early and often.</p>
<p>Amen!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

