<?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: Merge your intranet and web teams</title>
	<atom:link href="http://jboye.com/blogpost/merge-intranet-team-with-web-team/feed/" rel="self" type="application/rss+xml" />
	<link>http://jboye.com/blogpost/merge-intranet-team-with-web-team/</link>
	<description>The international community for web and intranet professionals</description>
	<lastBuildDate>Mon, 30 Jan 2012 19:45:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Christian Peter Larsen</title>
		<link>http://jboye.com/blogpost/merge-intranet-team-with-web-team/comment-page-1/#comment-4348</link>
		<dc:creator>Christian Peter Larsen</dc:creator>
		<pubDate>Mon, 20 Sep 2010 14:12:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=986#comment-4348</guid>
		<description>Being a vendor delivering both intranets and websites portal i couldnt agree more with Brian (and the post). No doubt the organisation will benefit of a merger of the website-  and intranetteam. Besides the shared knowledge and aligned strategy within the communications processes of the two - there are numerous way to benefit on the budget from such a merge.

Let it be said: Im not an evangalist in the sence that you should run the same appl. as platform for both inter- and intranet. In some cases it might be a fruitfull strategy - and then the benefits in terms of developing and maintenance are evident. But eventhough the platfom isnt shared you can still benefit on the budget in numerous ways. E.g. Custommade applications can be adopted between the two - this however requires that the two teams knows what each other are doing.</description>
		<content:encoded><![CDATA[<p>Being a vendor delivering both intranets and websites portal i couldnt agree more with Brian (and the post). No doubt the organisation will benefit of a merger of the website-  and intranetteam. Besides the shared knowledge and aligned strategy within the communications processes of the two &#8211; there are numerous way to benefit on the budget from such a merge.</p>
<p>Let it be said: Im not an evangalist in the sence that you should run the same appl. as platform for both inter- and intranet. In some cases it might be a fruitfull strategy &#8211; and then the benefits in terms of developing and maintenance are evident. But eventhough the platfom isnt shared you can still benefit on the budget in numerous ways. E.g. Custommade applications can be adopted between the two &#8211; this however requires that the two teams knows what each other are doing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Kaupa</title>
		<link>http://jboye.com/blogpost/merge-intranet-team-with-web-team/comment-page-1/#comment-197</link>
		<dc:creator>Brian Kaupa</dc:creator>
		<pubDate>Sun, 25 Jan 2009 18:54:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=986#comment-197</guid>
		<description>Nice post. This arrangement can also offer the following added benefits:
* cost reductions by leveraging some of the same infrastructure (app servers, web servers, firewalls, etc…)
* ability to conduct smaller scale tests of new functionality before showing them to the world (i.e. allow the intranet to be the ‘test bed’ for new technologies/widgets)
* developer bench strength</description>
		<content:encoded><![CDATA[<p>Nice post. This arrangement can also offer the following added benefits:<br />
* cost reductions by leveraging some of the same infrastructure (app servers, web servers, firewalls, etc…)<br />
* ability to conduct smaller scale tests of new functionality before showing them to the world (i.e. allow the intranet to be the ‘test bed’ for new technologies/widgets)<br />
* developer bench strength</p>
]]></content:encoded>
	</item>
</channel>
</rss>

