<?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>The Sympriser Blog &#187; Requirements</title>
	<atom:link href="http://blog.symprise.net/category/practices/requirements/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.symprise.net</link>
	<description>Synergising the Enterprise through Software &#38; Management Innovation</description>
	<lastBuildDate>Fri, 13 Jan 2012 05:46:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>The Trust Requirement</title>
		<link>http://blog.symprise.net/2008/04/the-trust-requirement/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-trust-requirement</link>
		<comments>http://blog.symprise.net/2008/04/the-trust-requirement/#comments</comments>
		<pubDate>Tue, 15 Apr 2008 12:53:40 +0000</pubDate>
		<dc:creator>Rafael Peixoto de Azevedo</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Requirements]]></category>

		<guid isPermaLink="false">http://sympriser.wordpress.com/?p=394</guid>
		<description><![CDATA[The perceived credibility of an IT professional goes beyond his or her personal competence and integrity; it is grounded in trustful relationships. This post is a reflection on our professional relationship style. Is it effective to create and nurture trustful relationships?]]></description>
		<wfw:commentRss>http://blog.symprise.net/2008/04/the-trust-requirement/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Most Requirements are just Design Decisions</title>
		<link>http://blog.symprise.net/2008/04/most-requirements-are-just-design-decisions/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=most-requirements-are-just-design-decisions</link>
		<comments>http://blog.symprise.net/2008/04/most-requirements-are-just-design-decisions/#comments</comments>
		<pubDate>Tue, 15 Apr 2008 12:30:24 +0000</pubDate>
		<dc:creator>Rafael Peixoto de Azevedo</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Requirements]]></category>

		<guid isPermaLink="false">http://sympriser.wordpress.com/?p=392</guid>
		<description><![CDATA[<strong><em>The language we use both reflects and influences our thinking.</em></strong>

The term <strong>“requirements”</strong> has its roots on cartesian and bureaucratic thinking, that supposes a static and impersonal business world where specialists would be able to uncover, extract and document the definitive specifications for software systems.]]></description>
		<wfw:commentRss>http://blog.symprise.net/2008/04/most-requirements-are-just-design-decisions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

