<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

<channel>
    

    <title>The nGen Works Blog: Prioritizing Functionality &#45; Five Questions Every Client Should Ask Themselves</title>
    <link>http://www.ngenworks.com/blog/detail/prioritizing_functionality_five_questions_every_client_should_ask/</link>
    <description>Five questions clients need to ask themselves about web functionality before initiating their new project.</description>
    <dc:language>en-us</dc:language>
    <dc:creator>carl@ngenworks.com</dc:creator>
    <dc:rights>Copyright 2008</dc:rights>
    <dc:date>2008-02-12T21:09:00-05:00</dc:date>
    <admin:generatorAgent rdf:resource="http://www.pmachine.com/" />



    <item>
      <title>Comment by Fred Boyle</title>
      <link>http://www.subtletech.com</link>
      <description><![CDATA[	<p>{body}</p>]]></description>
      <content:encoded><![CDATA[A great post, and so true.

The importance of "what problem/goal does this address" is HUGE.
Without carefully considering this a project can get out of hand very quickly.

Reducing the essence of a web site to core features and doing those features well is far better than creating all possible features in a so-so way.

A web site is a dynamic beast, always evolving and changing - features can be added or modified over time.]]></content:encoded>
     <dc:date>2008-02-19T14:40:12-05:00</dc:date>
    </item>


</channel>
</rss>