<?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>uFunctional LLC &#187; Software teams</title>
	<atom:link href="http://www.ufunctional.com/category/software-teams/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ufunctional.com</link>
	<description>Software Development Consulting</description>
	<lastBuildDate>Tue, 31 Jan 2012 18:44:09 +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>Forced March, not Death March</title>
		<link>http://www.ufunctional.com/2012/01/17/death-march-or-forced-march/</link>
		<comments>http://www.ufunctional.com/2012/01/17/death-march-or-forced-march/#comments</comments>
		<pubDate>Wed, 18 Jan 2012 03:48:45 +0000</pubDate>
		<dc:creator>Robert Merrill</dc:creator>
				<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Software teams]]></category>
		<category><![CDATA[death march]]></category>
		<category><![CDATA[Forced March]]></category>
		<category><![CDATA[schedule pressure]]></category>

		<guid isPermaLink="false">http://www.ufunctional.com/?p=1121</guid>
		<description><![CDATA[For almost exactly two months, from mid-November 2011 through mid-January 2012, I was on a Forced March, meaning lots of overtime and weekend work to get a software system up and running. It’s still not live—the sponsor switched from Date-Driven to Done-Driven and slipped the launch date six weeks, but not after I’d worked pretty [...]]]></description>
		<wfw:commentRss>http://www.ufunctional.com/2012/01/17/death-march-or-forced-march/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lessons from a Forced March</title>
		<link>http://www.ufunctional.com/2011/12/26/lessons-from-a-forced-march/</link>
		<comments>http://www.ufunctional.com/2011/12/26/lessons-from-a-forced-march/#comments</comments>
		<pubDate>Mon, 26 Dec 2011 16:40:30 +0000</pubDate>
		<dc:creator>Robert Merrill</dc:creator>
				<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Software teams]]></category>
		<category><![CDATA[Forced March]]></category>
		<category><![CDATA[schedule pressure]]></category>

		<guid isPermaLink="false">http://www.ufunctional.com/?p=1119</guid>
		<description><![CDATA[My primary client is going live in one week (1/2/2012) on an Order Management System that&#8217;s been in the works since March 2011 and was selected in August. For me, it turned into a forced march in mid-November—six-day weeks, extra hours, and more stress all around that I would have liked. It&#8217;s part of my [...]]]></description>
		<wfw:commentRss>http://www.ufunctional.com/2011/12/26/lessons-from-a-forced-march/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Why Big Projects Often Have Problems</title>
		<link>http://www.ufunctional.com/2011/04/06/why-big-projects-often-have-problems/</link>
		<comments>http://www.ufunctional.com/2011/04/06/why-big-projects-often-have-problems/#comments</comments>
		<pubDate>Wed, 06 Apr 2011 19:40:54 +0000</pubDate>
		<dc:creator>Robert Merrill</dc:creator>
				<category><![CDATA[Software teams]]></category>
		<category><![CDATA[corporate culture]]></category>
		<category><![CDATA[project management]]></category>

		<guid isPermaLink="false">http://www.ufunctional.com/?p=927</guid>
		<description><![CDATA[This popped into my head the other day, and stuck. I need to examine this carefully. Does it really hold up, at least in my experience and that of others? If so, can something useful come out of this idea? So, expect this post to change. I’m thinking out loud a bit. Big projects cost [...]]]></description>
		<wfw:commentRss>http://www.ufunctional.com/2011/04/06/why-big-projects-often-have-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The more important the project, the less effective the team</title>
		<link>http://www.ufunctional.com/2009/09/21/the-more-important-the-project-the-less-effective-the-team/</link>
		<comments>http://www.ufunctional.com/2009/09/21/the-more-important-the-project-the-less-effective-the-team/#comments</comments>
		<pubDate>Mon, 21 Sep 2009 19:45:07 +0000</pubDate>
		<dc:creator>Robert Merrill</dc:creator>
				<category><![CDATA[Software teams]]></category>
		<category><![CDATA[Software-Intensive Businesses]]></category>

		<guid isPermaLink="false">http://www.ufunctional.com/?p=602</guid>
		<description><![CDATA[Think that your software team performs best under pressure? Not if what a Harvard Business School professor learned about other knowledge workers—auditors and consultants—applies to programmers, too. In Feeling the Heat: The Effects of Performance Pressure on Teams&#8217; Knowledge Use and Performance, Heidi Gardner explains that the pressure triggers “threat rigidity,” and causes “reduced cognitive [...]]]></description>
		<wfw:commentRss>http://www.ufunctional.com/2009/09/21/the-more-important-the-project-the-less-effective-the-team/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

