<?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>Web Development (ICA50601) &#187; Project Management</title>
	<atom:link href="http://c476.edublogs.org/category/design/project-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://c476.edublogs.org</link>
	<description>Diploma in Website Development (SWAN TAFE) Blog</description>
	<lastBuildDate>Thu, 14 Sep 2006 02:53:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Web Development Proposals &amp; resources</title>
		<link>http://c476.edublogs.org/2006/09/14/web-development-proposals-resources/</link>
		<comments>http://c476.edublogs.org/2006/09/14/web-development-proposals-resources/#comments</comments>
		<pubDate>Thu, 14 Sep 2006 02:53:11 +0000</pubDate>
		<dc:creator>Ady</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[User]]></category>

		<guid isPermaLink="false">http://c476.edublogs.org/2006/09/14/web-development-proposals-resources/</guid>
		<description><![CDATA[<p>
In a recent hunt for ways to write project proposals I saw a very nice article by a company called Taoti....  I really suggest that you look at these articles and download a copy of the Proposal and use that for the "pre-sales" section of the web development you are undertaking.
</p>]]></description>
		<wfw:commentRss>http://c476.edublogs.org/2006/09/14/web-development-proposals-resources/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Shared documentation system</title>
		<link>http://c476.edublogs.org/2005/10/04/shared-documentation-system/</link>
		<comments>http://c476.edublogs.org/2005/10/04/shared-documentation-system/#comments</comments>
		<pubDate>Tue, 04 Oct 2005 15:22:23 +0000</pubDate>
		<dc:creator>Adrian Gould</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Notices]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[User]]></category>
		<category><![CDATA[Web Links]]></category>

		<guid isPermaLink="false">http://c476.edublogs.org/?p=62</guid>
		<description><![CDATA[One possible way to create a shared system for documentation is to use the writeboard system. Have a look and see if it will help. If so let me know and I will create a writeboard for your team.
Ady
]]></description>
		<wfw:commentRss>http://c476.edublogs.org/2005/10/04/shared-documentation-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web Redesign lifecycle</title>
		<link>http://c476.edublogs.org/2005/08/16/web-redesign-lifecycle/</link>
		<comments>http://c476.edublogs.org/2005/08/16/web-redesign-lifecycle/#comments</comments>
		<pubDate>Tue, 16 Aug 2005 08:49:25 +0000</pubDate>
		<dc:creator>Ady</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://c476.edublogs.org/?p=19</guid>
		<description><![CDATA[The following images (hidden behind the &#8220;read more&#8221;) show the 5 stages of the Web Redesign life cycle.
The images indicate the sort of action that could be taken at each stage.
I tend to wonder if some are not in the right place and will argue this out at a later date.






]]></description>
		<wfw:commentRss>http://c476.edublogs.org/2005/08/16/web-redesign-lifecycle/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Site redevelopment and testing</title>
		<link>http://c476.edublogs.org/2005/08/16/site-redevelopment-and-testing-4/</link>
		<comments>http://c476.edublogs.org/2005/08/16/site-redevelopment-and-testing-4/#comments</comments>
		<pubDate>Tue, 16 Aug 2005 03:35:07 +0000</pubDate>
		<dc:creator>Ady</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://c476.edublogs.org/2005/08/16/site-redevelopment-and-testing-4/</guid>
		<description><![CDATA[When you are contracted to redevelop (or even design a site from scratch) a web site by a client you need to follow a series of stages that are outlined very well by Kelly Goto and Emily Cotler in their book Web Redesign.

They state one process fits all: 


Defining the Project:

discovery, 
planning, and 
clarification; 


Developing [...]]]></description>
		<wfw:commentRss>http://c476.edublogs.org/2005/08/16/site-redevelopment-and-testing-4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
