<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Helms, Hal</title>	<link>http://tc.eserver.org/authors/Helms,_Hal</link>
	<description>A bibliography of works by Helms, Hal in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Helms, Hal</title>
		<link>http://tc.eserver.org/dir/Helms,_Hal</link>
	</image>
	<item>
		<title>In Defense of Scope Creep</title>
		<link>http://tc.eserver.org/13763.html</link>
		<guid>http://tc.eserver.org/13763.html</guid>
		<description>Web developers are a tough lot, willing to brave constantly changing technologies, competing “standards,” and tools that are often clumsy and dull. Yet brave as we are, two little words strike fear in the hearts of even the boldest of us, making us consider a change to a less stressful job-air traffic control, perhaps.&#xD;&#xD;Scope creep threatens to undermine all our hard work, causing rewrite after rewrite of carefully crafted markup and code. In short, scope creep is evil. That’s the prevailing wisdom. But consider the results of four studies done over the last five years that show that as little as 20% of corporate software projects are successful. Prevailing, it may be, but is it wisdom?</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Helms,_Hal.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>