<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: The perils of managing 3rd party software: do&#8217;s and don&#8217;ts</title>
	<link>http://www.visionmobile.com/blog/2008/03/the-perils-of-managing-3rd-party-software-dos-and-donts/</link>
	<description>Distilling market noise into market sense.</description>
	<pubDate>Sun, 20 Jul 2008 14:47:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Managing 3rd party software &#124; VoIP Survivor</title>
		<link>http://www.visionmobile.com/blog/2008/03/the-perils-of-managing-3rd-party-software-dos-and-donts/#comment-37845</link>
		<dc:creator>Managing 3rd party software &#124; VoIP Survivor</dc:creator>
		<pubDate>Mon, 14 Apr 2008 13:38:46 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2008/03/the-perils-of-managing-3rd-party-software-dos-and-donts/#comment-37845</guid>
		<description>[...] middleware vendors or various other types of manufacturers.I came across Åse Stiller&#8217;s guest post on VisionMobile, where he recommends vendors build an end-to-end flowchart of how source codes of [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] middleware vendors or various other types of manufacturers.I came across Åse Stiller&#8217;s guest post on VisionMobile, where he recommends vendors build an end-to-end flowchart of how source codes of [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mobile Analyst Watch</title>
		<link>http://www.visionmobile.com/blog/2008/03/the-perils-of-managing-3rd-party-software-dos-and-donts/#comment-31204</link>
		<dc:creator>Mobile Analyst Watch</dc:creator>
		<pubDate>Thu, 01 Jan 1970 01:00:00 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2008/03/the-perils-of-managing-3rd-party-software-dos-and-donts/#comment-31204</guid>
		<description>&lt;!--%kramer-pre%--&gt;VisionMobileabout The perils of managing 3rd party software: do’s and don’tsRoss Rubin at NPD Group about Motorola’s split comes as paths are convergingPhilippe Winthrop at Aberdeen Group about Motorola is splitting up&lt;!--%kramer-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a class="technorati-balloon" href="http://www.technorati.com/cosmos/search.html?url="><img src="http://static.technorati.com/images/bubble_h17.gif" class="technorati-balloon" alt="links from Technorati" style="border:0;" /></a>VisionMobileabout The perils of managing 3rd party software: do’s and don’tsRoss Rubin at NPD Group about Motorola’s split comes as paths are convergingPhilippe Winthrop at Aberdeen Group about Motorola is splitting up</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VoIP</title>
		<link>http://www.visionmobile.com/blog/2008/03/the-perils-of-managing-3rd-party-software-dos-and-donts/#comment-41360</link>
		<dc:creator>VoIP</dc:creator>
		<pubDate>Thu, 01 Jan 1970 01:00:00 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2008/03/the-perils-of-managing-3rd-party-software-dos-and-donts/#comment-41360</guid>
		<description>&lt;!--%kramer-pre%--&gt;with outsourcing specific protocol stacks and user interface engines, etc. These come from vendors which are sometimes called ISVs (Independent Software Vendors), middleware vendors or various other types of manufacturers.I came across Åse Stiller’sguest poston VisionMobile, where he recommends vendors build an end-to-end flowchart of how source codes of their products flow in and out of the organization. Such a flowchart shows insights on certain dangers and restrictions of use.&lt;!--%kramer-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a class="technorati-balloon" href="http://www.technorati.com/cosmos/search.html?url="><img src="http://static.technorati.com/images/bubble_h17.gif" class="technorati-balloon" alt="links from Technorati" style="border:0;" /></a>with outsourcing specific protocol stacks and user interface engines, etc. These come from vendors which are sometimes called ISVs (Independent Software Vendors), middleware vendors or various other types of manufacturers.I came across Åse Stiller’sguest poston VisionMobile, where he recommends vendors build an end-to-end flowchart of how source codes of their products flow in and out of the organization. Such a flowchart shows insights on certain dangers and restrictions of use.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
