<?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>Dodatki &#187; 2355</title>
	<atom:link href="http://www.dodatki.ilawa.pl/category/2355/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dodatki.ilawa.pl</link>
	<description>Addons</description>
	<lastBuildDate>Fri, 07 May 2010 09:15:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>The role of leadership in software development</title>
		<link>http://www.dodatki.ilawa.pl/2010/02/15/the-role-of-leadership-in-software-development/</link>
		<comments>http://www.dodatki.ilawa.pl/2010/02/15/the-role-of-leadership-in-software-development/#comments</comments>
		<pubDate>Mon, 15 Feb 2010 04:48:53 +0000</pubDate>
		<dc:creator>Dodatki</dc:creator>
				<category><![CDATA[2355]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Scrum Master]]></category>
		<category><![CDATA[Technical Architect]]></category>

		<guid isPermaLink="false">http://www.dodatki.ilawa.pl/2010/02/15/the-role-of-leadership-in-software-development/</guid>
		<description><![CDATA[Google Tech Talks May 6, 2008 ABSTRACT When you look around, there are a lot of leaders recommended for software development. We have the functional manager and the project manager, the scrum master and the black belt, the product owner and the customer-on-site, the technical leader and the architect, the product manager and the chief [...]]]></description>
			<content:encoded><![CDATA[<div style="float:right; padding: 12px"></div>
<div>
<div class="cc_video"><object width="425" height="355"><param name="movie" value="http://www.youtube.com/v/ypEMdjslEOI&#038;hl=en"></param><param name="wmode" value="transparent"></param><embed src="http://www.youtube.com/v/ypEMdjslEOI&#038;hl=en" type="application/x-shockwave-flash" wmode="transparent" width="425" height="355"></embed></object></div>
<p><br/>Google Tech Talks May 6, 2008 ABSTRACT When you look around, there are a lot of leaders recommended for software development. We have the functional manager and the project manager, the scrum master and the black belt, the product owner and the customer-on-site, the technical leader and the architect, the product manager and the chief engineer. Clearly that&#8217;s too many leaders. So how many leaders should there be, what should they do, what shouldn&#8217;t they do, and what skills do they need? This &#8230;<em>Submited by:<strong>googletechtalks</strong></em></div>
]]></content:encoded>
			<wfw:commentRss>http://www.dodatki.ilawa.pl/2010/02/15/the-role-of-leadership-in-software-development/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
	</channel>
</rss>

