<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Software Engineering Roundup</title>
	<atom:link href="http://seroundup.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://seroundup.wordpress.com</link>
	<description>Your source for news, trends and ideas</description>
	<lastBuildDate>Mon, 10 Nov 2008 14:10:43 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Continuous integration by Jay Harris</title>
		<link>http://seroundup.wordpress.com/2008/11/09/continuous-integration/#comment-4</link>
		<dc:creator>Jay Harris</dc:creator>
		<pubDate>Mon, 10 Nov 2008 14:10:43 +0000</pubDate>
		<guid isPermaLink="false">http://seroundup.wordpress.com/?p=36#comment-4</guid>
		<description>Continuous Integration is absolutely all of this, but there is even more to it. Through &quot;automated deployments&quot; and &quot;making it easy to get the latest deliverables&quot;--two of Fowler&#039;s other components of CI--it is easy for the QA team to get at the latest bits and test the application. Also, another of Fowler&#039;s items, &quot;everyone can see the results of the latest build,&quot; the management teams have visibility into the state of the application, helping them make decisions, such as those surrounding deployment to a staging or production environment, or when to begin client testing.

For anyone interested in further reading, I recommend Martin Fowler&#039;s &lt;a href=&quot;http://www.martinfowler.com/articles/continuousIntegration.html&quot; rel=&quot;nofollow&quot;&gt;online article on continuous integration&lt;/a&gt; or Paul M. Duvall&#039;s book on the same topic.</description>
		<content:encoded><![CDATA[<p>Continuous Integration is absolutely all of this, but there is even more to it. Through &#8220;automated deployments&#8221; and &#8220;making it easy to get the latest deliverables&#8221;&#8211;two of Fowler&#8217;s other components of CI&#8211;it is easy for the QA team to get at the latest bits and test the application. Also, another of Fowler&#8217;s items, &#8220;everyone can see the results of the latest build,&#8221; the management teams have visibility into the state of the application, helping them make decisions, such as those surrounding deployment to a staging or production environment, or when to begin client testing.</p>
<p>For anyone interested in further reading, I recommend Martin Fowler&#8217;s <a href="http://www.martinfowler.com/articles/continuousIntegration.html" rel="nofollow">online article on continuous integration</a> or Paul M. Duvall&#8217;s book on the same topic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How we went digital without a strategy by Philip Preissing</title>
		<link>http://seroundup.wordpress.com/2008/10/24/how-we-went-digital-without-a-strategy/#comment-2</link>
		<dc:creator>Philip Preissing</dc:creator>
		<pubDate>Sat, 25 Oct 2008 12:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://seroundup.wordpress.com/?p=18#comment-2</guid>
		<description>The article contains other interesting facts about the semco company and it&#039;s company culture.

The author shares six lessons they learned to be a creative and adaptive organization:
- &lt;i&gt;Forget about the top line&lt;/i&gt;: The measure for business sucess is not it&#039;s size but how long it survives
- &lt;i&gt;Never stop being a startup&lt;/i&gt;: Every six months, each of Semco&#039;s departments has to justify it&#039;s continued existence and all employees are asked to be rehired.
- &lt;i&gt;Don&#039;t be a nanny&lt;/i&gt;: Don&#039;t treat your employees like children. People at Semco decide when and how much they work, when they get on vacation and even how they are paid. But since they know that they have to be rehired every six months, they know that their jobs are always at risk.
- &lt;i&gt;Let talent find it&#039;s place&lt;/i&gt;: Let people chose in which department they want to work.
- &lt;i&gt;Make decisions quickly and openly&lt;/i&gt;: Every employee can attend board meetings and present their business ideas. Ideas are checked against only two well-defined criteria and if they meet them, the business gets launched inside Semco.
- &lt;i&gt;Partner promiscuously&lt;/i&gt;: When you start a new business, you need help. Semco&#039;s foundation over the years were partnerships with other firms.</description>
		<content:encoded><![CDATA[<p>The article contains other interesting facts about the semco company and it&#8217;s company culture.</p>
<p>The author shares six lessons they learned to be a creative and adaptive organization:<br />
- <i>Forget about the top line</i>: The measure for business sucess is not it&#8217;s size but how long it survives<br />
- <i>Never stop being a startup</i>: Every six months, each of Semco&#8217;s departments has to justify it&#8217;s continued existence and all employees are asked to be rehired.<br />
- <i>Don&#8217;t be a nanny</i>: Don&#8217;t treat your employees like children. People at Semco decide when and how much they work, when they get on vacation and even how they are paid. But since they know that they have to be rehired every six months, they know that their jobs are always at risk.<br />
- <i>Let talent find it&#8217;s place</i>: Let people chose in which department they want to work.<br />
- <i>Make decisions quickly and openly</i>: Every employee can attend board meetings and present their business ideas. Ideas are checked against only two well-defined criteria and if they meet them, the business gets launched inside Semco.<br />
- <i>Partner promiscuously</i>: When you start a new business, you need help. Semco&#8217;s foundation over the years were partnerships with other firms.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
