<?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>Wadeware &#187; Best Practices</title>
	<atom:link href="http://www.wadeware.net/tag/best-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wadeware.net</link>
	<description>IT Consulting + Training &#38; Support</description>
	<lastBuildDate>Tue, 17 Jan 2012 21:30:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>URLs: To see, or not to see? That is the question…</title>
		<link>http://www.wadeware.net/technical-documentation/urls-to-see-or-not-to-see-that-is-the-question/</link>
		<comments>http://www.wadeware.net/technical-documentation/urls-to-see-or-not-to-see-that-is-the-question/#comments</comments>
		<pubDate>Mon, 13 Jun 2011 22:26:57 +0000</pubDate>
		<dc:creator>Steve Wacker</dc:creator>
				<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[discussions]]></category>
		<category><![CDATA[editing]]></category>
		<category><![CDATA[hypertext]]></category>
		<category><![CDATA[Rants and Raves]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[URLs]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=1949</guid>
		<description><![CDATA[This post provides a bit of history about hypertext and discusses different options for displaying hyperlinks. It also seeks input from readers about whether full URLs (hyperlinks) are useful and their preferences for how URLs display.]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/urls-to-see-or-not-to-see-that-is-the-question/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to Discover Your Business Requirements</title>
		<link>http://www.wadeware.net/technical-documentation/how-to-discover-your-business-requirements/</link>
		<comments>http://www.wadeware.net/technical-documentation/how-to-discover-your-business-requirements/#comments</comments>
		<pubDate>Mon, 18 Apr 2011 20:47:47 +0000</pubDate>
		<dc:creator>Holly Amundson</dc:creator>
				<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Training]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=1820</guid>
		<description><![CDATA[Having clearly defined requirements at the start of a project is extremely important. Requirements help establish and maintain a solid target throughout a project, help minimize wasted time and frustration, and can help ensure an organization maximizes its return on investment. This document contains suggested steps for discovering and defining business requirements.]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/how-to-discover-your-business-requirements/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Adding Value to Software Development through Effective Testing</title>
		<link>http://www.wadeware.net/software-development/adding-value-to-software-development-through-effective-testing/</link>
		<comments>http://www.wadeware.net/software-development/adding-value-to-software-development-through-effective-testing/#comments</comments>
		<pubDate>Thu, 24 Feb 2011 23:58:53 +0000</pubDate>
		<dc:creator>Anu Balasubramanian</dc:creator>
				<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Applications]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=1536</guid>
		<description><![CDATA[Anu shares the value of developing a strong detailed test plan and test cases so that projects don't run overbudget due to quality control issues and last minute re-factoring to meet the real business requirements.]]></description>
		<wfw:commentRss>http://www.wadeware.net/software-development/adding-value-to-software-development-through-effective-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>5 Instructional Design Best Practices</title>
		<link>http://www.wadeware.net/it-courseware/5-instructional-design-best-practices/</link>
		<comments>http://www.wadeware.net/it-courseware/5-instructional-design-best-practices/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 18:40:02 +0000</pubDate>
		<dc:creator>Dennis Rea</dc:creator>
				<category><![CDATA[IT Courseware]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[How To]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=854</guid>
		<description><![CDATA[A common mistake in courseware design is trying to force students to learn too much too soon. Keep them engaged throughout your learning sessions by following these instructional design best practices.]]></description>
		<wfw:commentRss>http://www.wadeware.net/it-courseware/5-instructional-design-best-practices/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>5 Good Reasons to Use a Style Guide</title>
		<link>http://www.wadeware.net/technical-documentation/5-good-reasons-to-use-a-style-guide/</link>
		<comments>http://www.wadeware.net/technical-documentation/5-good-reasons-to-use-a-style-guide/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 17:20:46 +0000</pubDate>
		<dc:creator>Steve Wacker</dc:creator>
				<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Style Guides]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=774</guid>
		<description><![CDATA[Steve Wacker, a technical documentation writer and editor at Wadeware, shares 5 good reasons to use a style guide when developing technical content.]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/5-good-reasons-to-use-a-style-guide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

