<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.2" -->
<rss version="2.0">
	<channel>
		<title>Tradeoff: Go For Quality</title>
		<description>Comments for Tradeoff: Go For Quality at http://www.stevenmsmith.com , comment 1 to 4 out of 4 comments</description>
		<link>http://www.stevenmsmith.com</link>
		<lastBuildDate>Thu, 20 Nov 2008 22:17:26 +0100</lastBuildDate>
		<generator>FeedCreator 1.7.2</generator>
		<item>
			<title>Thank you, Laurent.</title>
			<link>http://www.stevenmsmith.com/my-blogs/systems/tradeoff-go-for-quality.html#comment-84</link>
			<description>I appreciate you for sharing your thoughts.

I interpret you advocate being conscious of this general law from the beginning. 

As long as the long-term process improvement plan is based on sound logic rather than fantasy, the concept makes sense to me. - Steve Smith</description>
			<pubDate>Mon, 02 Jun 2008 06:34:12 +0100</pubDate>
		</item>
		<item>
			<title>A more optimistic presentation</title>
			<link>http://www.stevenmsmith.com/my-blogs/systems/tradeoff-go-for-quality.html#comment-83</link>
			<description>Even if I fully agree on the approach (it's often something that I present), one trade-off can be that one of the product gain can improve the global process and thus make you gain time/cost.

By thinking at his concept from the beginning, you can try to design your better product in order to increase also your process to create it - Laurent Saubusse</description>
			<pubDate>Mon, 02 Jun 2008 05:46:25 +0100</pubDate>
		</item>
		<item>
			<title>Dwayne, I agree that it's not easy to do</title>
			<link>http://www.stevenmsmith.com/my-blogs/systems/tradeoff-go-for-quality.html#comment-82</link>
			<description>Thank you for sharing that approach.

I see that approach used regularly. It does enable the possibility of keeping cost and schedule the same by reducing the amount of work that needs to be done. And you are right -- it's not easy.

I would recommend this approach if the customers whose opinions mattered the most agreed the integration of all the changes resulted in higher quality. - Steve Smith</description>
			<pubDate>Mon, 26 May 2008 08:19:28 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.stevenmsmith.com/my-blogs/systems/tradeoff-go-for-quality.html#comment-79</link>
			<description>A slight twist to this is:

(1) improve quality (fewer errors)
(2) reduce the number of features

(3) keep cost and schedule the same

Not easy to do though. - Dwayne Phillips</description>
			<pubDate>Sat, 24 May 2008 09:31:15 +0100</pubDate>
		</item>
	</channel>
</rss>
