<?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: Design of Programmer Spaces &#8211; My DCamp Presentation</title>
	<atom:link href="http://www.silverstripesoftware.com/blog/archives/69/feed" rel="self" type="application/rss+xml" />
	<link>http://www.silverstripesoftware.com/blog/archives/69</link>
	<description></description>
	<lastBuildDate>Thu, 18 Mar 2010 15:42:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The worst business environment? Cubicles! &#187; Blog Archive</title>
		<link>http://www.silverstripesoftware.com/blog/archives/69/comment-page-1#comment-20856</link>
		<dc:creator>The worst business environment? Cubicles! &#187; Blog Archive</dc:creator>
		<pubDate>Wed, 02 Apr 2008 04:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/archives/69#comment-20856</guid>
		<description>[...] Design of Programmer Spaces    Working in an Agile team? Silver Catalyst is a lightweight project management tool for agile [...]</description>
		<content:encoded><![CDATA[<p>[...] Design of Programmer Spaces    Working in an Agile team? Silver Catalyst is a lightweight project management tool for agile [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: siddharta</title>
		<link>http://www.silverstripesoftware.com/blog/archives/69/comment-page-1#comment-5205</link>
		<dc:creator>siddharta</dc:creator>
		<pubDate>Tue, 18 Sep 2007 06:53:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/archives/69#comment-5205</guid>
		<description>Just to give a quick summary of the presentation since it does not have any voice over -

[Slides 2,3]

Working in a maze of cubicles makes a programmer feel like a chicken in a chicken farm. The key metric with cubicle layouts is - how many programmers can we stuff in one room? Cubicle layouts are probably the worst for software development. They do not cut out the noise or offer privacy, yet manage to isolate the programmer from their team.

[Slide 4,5,6,7]

The first book on looking at programming as a human activity was Gerald Weinberg&#039;s &quot;The Psychology of Computer Programming&quot; (Resource Link #2 above) way back in 1971. The book look at programming as a combination of individual and social activities. Another classic book was Peopleware (Resource Link #3) above that devoted an entire part on the office environment.

[Slide 8, 9, 10]

The four main factors affecting individual productivity are Sunlight, Noise, Space and Comfort. Most office spaces do not effectively use window space, with cubicles in the center, thus wasting the windows. 

[Slide 11]

External noise such as traffic, construction etc can be cut using noise proofing. Internal noise such as people talking and phones ringing are a bit more difficult. The best option is to separate out noise generators like Sales and put them in a different room from programmers. Also give a separate room to each team.

[Slide 12]

IBM did some research while developing their Santa Teresa facility (Resource Link #4) where they came up with these metrics for programmer space. How many of us get this much space to work in?

[Slide 13, 14]

Finally, many companies do not allow programmers to customize the working area. A working area should be comfortable to the people working there, so it is important that it be customizable. 

[Slide 15]

Coming to social activities, research shows that 30% of the time is spent working alone, while 50% is spent with one person. The remaining time is spent with more than one person. Thus there is a need in office layouts to take into consideration the 30-70 split between individual and team work. 

[Slide 16]

The Caves and Commons layout (room on the top-right) has &quot;Caves&quot; where programmers can work alone, and &quot;Commons&quot; which has 2 chairs side by side optimized for the case where you work with one other person (Resource Link #5).The conference room is ideal for larger groups to work together. Also notice how the sales team have their own office. 

[Slide 17]

A private office is another layout. Its great for individual work, but it cuts out group interaction. Notice the large amount of space, the nice lightning and the three monitors! More than one person can fit in the office when the need arises for some paired work.

[Slide 18]

Finally, a war room layout is popular among agile teams as it provides good team interaction possibilities. One problem is the noise, therefore it is better to get each team their own war room.  A war room is typically cross-functional with developers, testers and analysts sitting together. Notice the abundant sunlight and dual monitors.</description>
		<content:encoded><![CDATA[<p>Just to give a quick summary of the presentation since it does not have any voice over -</p>
<p>[Slides 2,3]</p>
<p>Working in a maze of cubicles makes a programmer feel like a chicken in a chicken farm. The key metric with cubicle layouts is &#8211; how many programmers can we stuff in one room? Cubicle layouts are probably the worst for software development. They do not cut out the noise or offer privacy, yet manage to isolate the programmer from their team.</p>
<p>[Slide 4,5,6,7]</p>
<p>The first book on looking at programming as a human activity was Gerald Weinberg&#8217;s &#8220;The Psychology of Computer Programming&#8221; (Resource Link #2 above) way back in 1971. The book look at programming as a combination of individual and social activities. Another classic book was Peopleware (Resource Link #3) above that devoted an entire part on the office environment.</p>
<p>[Slide 8, 9, 10]</p>
<p>The four main factors affecting individual productivity are Sunlight, Noise, Space and Comfort. Most office spaces do not effectively use window space, with cubicles in the center, thus wasting the windows. </p>
<p>[Slide 11]</p>
<p>External noise such as traffic, construction etc can be cut using noise proofing. Internal noise such as people talking and phones ringing are a bit more difficult. The best option is to separate out noise generators like Sales and put them in a different room from programmers. Also give a separate room to each team.</p>
<p>[Slide 12]</p>
<p>IBM did some research while developing their Santa Teresa facility (Resource Link #4) where they came up with these metrics for programmer space. How many of us get this much space to work in?</p>
<p>[Slide 13, 14]</p>
<p>Finally, many companies do not allow programmers to customize the working area. A working area should be comfortable to the people working there, so it is important that it be customizable. </p>
<p>[Slide 15]</p>
<p>Coming to social activities, research shows that 30% of the time is spent working alone, while 50% is spent with one person. The remaining time is spent with more than one person. Thus there is a need in office layouts to take into consideration the 30-70 split between individual and team work. </p>
<p>[Slide 16]</p>
<p>The Caves and Commons layout (room on the top-right) has &#8220;Caves&#8221; where programmers can work alone, and &#8220;Commons&#8221; which has 2 chairs side by side optimized for the case where you work with one other person (Resource Link #5).The conference room is ideal for larger groups to work together. Also notice how the sales team have their own office. </p>
<p>[Slide 17]</p>
<p>A private office is another layout. Its great for individual work, but it cuts out group interaction. Notice the large amount of space, the nice lightning and the three monitors! More than one person can fit in the office when the need arises for some paired work.</p>
<p>[Slide 18]</p>
<p>Finally, a war room layout is popular among agile teams as it provides good team interaction possibilities. One problem is the noise, therefore it is better to get each team their own war room.  A war room is typically cross-functional with developers, testers and analysts sitting together. Notice the abundant sunlight and dual monitors.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
