<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Software development in the real world: Requirements</title>
	<atom:link href="http://www.prepresspilgrim.com/index.php/archive/software-development-in-the-real-world-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.prepresspilgrim.com/index.php/archive/software-development-in-the-real-world-requirements/</link>
	<description>Cheap Printer Ink</description>
	<lastBuildDate>Sat, 21 Jan 2012 21:13:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: admin</title>
		<link>http://www.prepresspilgrim.com/index.php/archive/software-development-in-the-real-world-requirements/comment-page-1/#comment-18906</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 05 Jan 2010 16:21:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.prepress.bluebutterfly.ca/?p=49#comment-18906</guid>
		<description>I would say the most important document is the business plan, the one doc that the &quot;engineers&quot; never get to see. Second is the budget. 
Too often during a reasonably  long development period, the business plan needs to be updated or even becomes obsolete. When that happens, the money men (executive sponsors) start screwing around with requirements.
It does help to know why and when those guys start messing with your head.
Secondly, it&#039;s amazing how many project managers can&#039;t manage or are ignorant of a budget.
PMP is nice to have but some of it is pie-in-the-sky. Like the executive charter? Come on, how are you supposed to hold a VP or even the CEO accountable. &lt;em&gt;They are  the boss(es). You don&#039;t hold them accountable, you just gotta roll with it.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>I would say the most important document is the business plan, the one doc that the &#8220;engineers&#8221; never get to see. Second is the budget.<br />
Too often during a reasonably  long development period, the business plan needs to be updated or even becomes obsolete. When that happens, the money men (executive sponsors) start screwing around with requirements.<br />
It does help to know why and when those guys start messing with your head.<br />
Secondly, it&#8217;s amazing how many project managers can&#8217;t manage or are ignorant of a budget.<br />
PMP is nice to have but some of it is pie-in-the-sky. Like the executive charter? Come on, how are you supposed to hold a VP or even the CEO accountable. <em>They are  the boss(es). You don&#8217;t hold them accountable, you just gotta roll with it.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zak Khan</title>
		<link>http://www.prepresspilgrim.com/index.php/archive/software-development-in-the-real-world-requirements/comment-page-1/#comment-18904</link>
		<dc:creator>Zak Khan</dc:creator>
		<pubDate>Tue, 05 Jan 2010 16:12:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.prepress.bluebutterfly.ca/?p=49#comment-18904</guid>
		<description>Enjoyed your post.  I am close to graduating and just wanted to ask you what documentation is typically critical to software project. We have covered everything in sample and senior design projects from requirements: SRS, design doc, PMP etc.</description>
		<content:encoded><![CDATA[<p>Enjoyed your post.  I am close to graduating and just wanted to ask you what documentation is typically critical to software project. We have covered everything in sample and senior design projects from requirements: SRS, design doc, PMP etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

