<?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: The Pyramid of Reuse</title>
	<atom:link href="http://www.technologyprofessional.org/2009/08/the-pyramid-of-reuse/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.technologyprofessional.org/2009/08/the-pyramid-of-reuse/</link>
	<description>Advance the profession.  Advance your career.</description>
	<lastBuildDate>Mon, 04 Apr 2011 23:34:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Vijay Narayanan</title>
		<link>http://www.technologyprofessional.org/2009/08/the-pyramid-of-reuse/#comment-22</link>
		<dc:creator>Vijay Narayanan</dc:creator>
		<pubDate>Sat, 05 Sep 2009 22:31:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.technologyprofessional.org/tpv2/?p=2171#comment-22</guid>
		<description>Phil,
Interesting post. Agree that software reuse will not happen by accident and needs careful orchestration of people, process, and tools. Your point about leveraging reuse opportunities across the development lifecycle is very valid as well. Many teams miss reuse opportunities because of inadequate communication about reusable assets as well as a lack of appropriate incentives around reuse. Teams need to be rewarded for both contributing to and leveraging reusable assets. Also some developers have difficulty distinguishing code reuse from systematic reuse. Finally, there is a need for pursuing reuse in conjunction with business objectives (not simply a technology goal in itself).</description>
		<content:encoded><![CDATA[<p>Phil,<br />
Interesting post. Agree that software reuse will not happen by accident and needs careful orchestration of people, process, and tools. Your point about leveraging reuse opportunities across the development lifecycle is very valid as well. Many teams miss reuse opportunities because of inadequate communication about reusable assets as well as a lack of appropriate incentives around reuse. Teams need to be rewarded for both contributing to and leveraging reusable assets. Also some developers have difficulty distinguishing code reuse from systematic reuse. Finally, there is a need for pursuing reuse in conjunction with business objectives (not simply a technology goal in itself).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

