<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>OpenKollab &#187; homepage</title>
	<atom:link href="http://mudball.net/openkollab/category/homepage/feed/" rel="self" type="application/rss+xml" />
	<link>http://mudball.net/openkollab</link>
	<description>Connecting Projects to Solve Massive Social Problems</description>
	<lastBuildDate>Thu, 02 Sep 2010 07:59:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Open Collaboration: Self-Organizing Innovation in Large Corporations</title>
		<link>http://mudball.net/openkollab/homepage/2009/11/29/test-post/</link>
		<comments>http://mudball.net/openkollab/homepage/2009/11/29/test-post/#comments</comments>
		<pubDate>Sun, 29 Nov 2009 16:35:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[homepage]]></category>

		<guid isPermaLink="false">http://mudball.net/openkollab/?p=301</guid>
		<description><![CDATA[Here is an excerpt from an excellent post by Dirk Riehle on open collaboration in enterprise:
In most com­pa­nies, the inno­va­tion process is orga­nized as fol­lows: A research unit sug­gests to build a pro­to­type of some inno­v­a­tive prod­uct or fea­ture, a line-of-business spon­sor signs off on the project, the research unit devel­ops the pro­to­type, a prod­uct [...]]]></description>
			<content:encoded><![CDATA[<p>Here is an excerpt from an excellent <a href="http://dirkriehle.com/2008/08/05/open-collaboration-self-organizing-innovation-in-large-corporations/">post by Dirk Riehle</a> on open collaboration in enterprise:</p>
<blockquote><p>In most com­pa­nies, the inno­va­tion process is orga­nized as fol­lows: A research unit sug­gests to build a pro­to­type of some inno­v­a­tive prod­uct or fea­ture, a line-of-business spon­sor signs off on the project, the research unit devel­ops the pro­to­type, a prod­uct unit receives it and turns it into a real product.</p>
<p>The crit­i­cal point is the trans­fer from research to prod­uct unit. Here, many things can go wrong, for example:</p>
<p><span id="more-267"> </span></p>
<ul>
<li>The pro­to­type is incom­pat­i­ble with the cur­rent prod­uct technology;</li>
<li>The inno­va­tion does not address the real prob­lems of the prod­uct unit;</li>
<li>The pro­to­type and inno­va­tion are incom­pre­hen­si­ble to the prod­uct unit;</li>
<li>The pro­to­type is late and the prod­uct unit is already devel­op­ing its own solution.</li>
</ul>
<p>The under­ly­ing prob­lem is the orga­ni­za­tional sep­a­ra­tion of research from prod­uct unit. In most com­pa­nies, research is sep­a­rated from prod­uct units to pre­vent imme­di­ate prod­uct needs from usurp­ing research and inno­va­tion resources. For effec­tive trans­fer, how­ever, research units need to con­sult with prod­uct units dur­ing the devel­op­ment of the research pro­to­type. Unfor­tu­nately, prod­uct units are typ­i­cally too busy to worry about research projects. Hence, prod­uct engi­neers are rarely assigned to engage with research projects early, or if they are, they fre­quently are too busy to do it properly.</p>
<p>At <span>SAP</span>, we have been com­ple­ment­ing the tra­di­tional top-down process of research-to-product unit trans­fer with a self-organizing bottom-up process that we call open col­lab­o­ra­tion [1]. Open col­lab­o­ra­tion is char­ac­ter­ized by the fol­low­ing three core principles:</p>
<ul>
<li>Egal­i­tar­ian: Every­one can par­tic­i­pate; no bor­ders to join­ing a project are erected.</li>
<li>Mer­i­to­cratic: Con­tri­bu­tions are eval­u­ated based on merit; senior­ity is less important.</li>
<li>Self-organizing: The col­lab­o­ra­tors choose their own col­lab­o­ra­tion processes.</li>
</ul>
<p>Open col­lab­o­ra­tion hap­pens, when forward-looking engi­neers from prod­uct units engage with researchers on their own free will rather than as the result of a top-down assign­ment. We have found that let­ting engi­neers choose by them­selves is crit­i­cal to the suc­cess of the engagement.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://mudball.net/openkollab/homepage/2009/11/29/test-post/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
