<?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>Advanced Architecture concepts</title>
	<atom:link href="http://legacy.iaacblog.com/maa2012-2013-advanced-architecture-concepts/feed/" rel="self" type="application/rss+xml" />
	<link>http://legacy.iaacblog.com/maa2012-2013-advanced-architecture-concepts</link>
	<description>Master in Advanced Architecture 2012/2013</description>
	<lastBuildDate>Thu, 29 Nov 2012 08:12:57 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Advanced Teamwork</title>
		<link>http://legacy.iaacblog.com/maa2012-2013-advanced-architecture-concepts/2012/11/advanced-teamwork/</link>
		<comments>http://legacy.iaacblog.com/maa2012-2013-advanced-architecture-concepts/2012/11/advanced-teamwork/#comments</comments>
		<pubDate>Thu, 29 Nov 2012 08:12:57 +0000</pubDate>
		<dc:creator>miguel.oliveira@iaac.net</dc:creator>
				<category><![CDATA[Miguel Oliveira]]></category>

		<guid isPermaLink="false">http://legacy.iaacblog.com/maa2012-2013-advanced-architecture-concepts/?p=158</guid>
		<description><![CDATA[It seems the image of the genius architect, conceiving ideas alone in his office, is dead. Considering that these days teams are wide and multidisciplinary, here are some guidelines on teamwork : 1 &#8211; Define what each of the team members knows, their skills (so effort can be directed) 2 &#8211; One leader is good, two [...]]]></description>
				<content:encoded><![CDATA[<p>It seems the image of the <strong>genius architect</strong>, conceiving ideas alone in his office, <strong>is dead</strong>.</p>
<p>Considering that these days teams are wide and multidisciplinary, here are some guidelines on <strong>teamwork</strong> :</p>
<p>1 &#8211; Define what <strong>each of the team members </strong><strong><strong>know</strong>s</strong>, their skills (so effort can be directed)</p>
<p>2 &#8211; One leader is good, two is best, three is a crowd (too<strong> many egos</strong> at stake)</p>
<p>3 &#8211; The leaders aren`t the BOSS (they provide a common <strong>vision</strong> and bring out the best of each member)</p>
<p>4 &#8211; <strong>Open Communication</strong> (serious open non emotional communication:  professional environment)</p>
<p>5 &#8211; <strong>No Stress</strong> (pressure brings out the worst part of individuals)</p>
<p>Sources: ESIC, IDOM</p>
]]></content:encoded>
			<wfw:commentRss>http://legacy.iaacblog.com/maa2012-2013-advanced-architecture-concepts/2012/11/advanced-teamwork/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
