<?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: Project Management Made, Well A Little Easier</title>
	<atom:link href="http://www.invokemedia.com/project-management-made-well-a-little-easier/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.invokemedia.com/project-management-made-well-a-little-easier/</link>
	<description>Hungry? Here&#039;s some food for thought.</description>
	<lastBuildDate>Sat, 28 Jan 2012 05:15:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: dt</title>
		<link>http://www.invokemedia.com/project-management-made-well-a-little-easier/comment-page-1/#comment-14442</link>
		<dc:creator>dt</dc:creator>
		<pubDate>Sun, 27 Jul 2008 23:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.invokemedia.com/?p=455#comment-14442</guid>
		<description>Admittedly it doesn&#039;t cover the technical details to the level you describe, but it&#039;s not necessarily meant to replace a technical spec.  It&#039;s great for having one document that serves as a guide to the client, designer and developer respectively.  It keeps the goals clear and definitive.

Also if it describes exactly how a piece should work, there&#039;s little for a developer to hide behind.  If you have problems with loose interpretations of how something works, it&#039;s time to adjust and get a little more detail into the document.</description>
		<content:encoded><![CDATA[<p>Admittedly it doesn&#8217;t cover the technical details to the level you describe, but it&#8217;s not necessarily meant to replace a technical spec.  It&#8217;s great for having one document that serves as a guide to the client, designer and developer respectively.  It keeps the goals clear and definitive.</p>
<p>Also if it describes exactly how a piece should work, there&#8217;s little for a developer to hide behind.  If you have problems with loose interpretations of how something works, it&#8217;s time to adjust and get a little more detail into the document.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PM Hut</title>
		<link>http://www.invokemedia.com/project-management-made-well-a-little-easier/comment-page-1/#comment-14406</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Sun, 27 Jul 2008 14:19:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.invokemedia.com/?p=455#comment-14406</guid>
		<description>Can the description of the task be that simple? I know that if you just give simple descriptions than what you will get is unfinished tasks. For example, in the case above, is it JS or Server Side validation for the fields? What is unique, the email, the first name and the last name, or both?

The description does describe everything you need, but it doesn&#039;t cover all the details, which developers tend to like to miss (even when they know about them).</description>
		<content:encoded><![CDATA[<p>Can the description of the task be that simple? I know that if you just give simple descriptions than what you will get is unfinished tasks. For example, in the case above, is it JS or Server Side validation for the fields? What is unique, the email, the first name and the last name, or both?</p>
<p>The description does describe everything you need, but it doesn&#8217;t cover all the details, which developers tend to like to miss (even when they know about them).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

