<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0"> 
<channel>
<title>Tom Hathaway Business Coach Articles</title>
<description>Recent Articles From EvanCarmichael.com</description>
<link>http://www.evancarmichael.com/</link>
<item>
<link>http://www.evancarmichael.com/Business-Coach/2652/Six-Stages-in-the-Evolution-of-a-Business-Requirement.html</link>
<guid isPermaLink="true">http://www.evancarmichael.com/Business-Coach/2652/Six-Stages-in-the-Evolution-of-a-Business-Requirement.html</guid>
<title>Six Stages in the Evolution of a Business Requirement</title>
<description>Business requirements exist in the wilds of organizations around the world.  We do not really know whether business requirements exist at all until we capture them. To ensure the safety of the business community and the developer community, the job of the business analyst is to tame these requirements. To be tamed, the requirements has to evolve through the phases of sentenced, whatified, scoped, clarified, quantified, and confirmed.</description>
</item>
<item>
<link>http://www.evancarmichael.com/Business-Coach/2652/Dowsing-for-Requirements.html</link>
<guid isPermaLink="true">http://www.evancarmichael.com/Business-Coach/2652/Dowsing-for-Requirements.html</guid>
<title>Dowsing for Requirements</title>
<description>Dowsing is a method for "devining" where water might be before you drill. Given the challenges of getting good business requirements from the business community, it might be time to try to apply this fringe technique to the process of business analysis.</description>
</item>
</channel>
</rss>