<?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: Government IT process review petition update</title>
	<atom:link href="http://blog.robbowley.net/2010/03/04/government-it-process-review-petition-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.robbowley.net/2010/03/04/government-it-process-review-petition-update/</link>
	<description>adventures in extreme programming</description>
	<lastBuildDate>Wed, 25 Aug 2010 06:23:32 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anna Shipman</title>
		<link>http://blog.robbowley.net/2010/03/04/government-it-process-review-petition-update/comment-page-1/#comment-11255</link>
		<dc:creator>Anna Shipman</dc:creator>
		<pubDate>Wed, 10 Mar 2010 13:39:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.robbowley.net/?p=1246#comment-11255</guid>
		<description>When working for a previous company I worked on one of these large, late, over-budget, bad press projects for a government department. In addition to the budgetting issues that Nick Oostvogels raises, a major problem was that the actual end users of the system were not involved anywhere in the design, and while there was a lot of to-ing and fro-ing on the design during the design phase, the application was presented to the actual users as a fait accompli and surprise, surprise, didn&#039;t meet their needs. 

I don&#039;t think Agile will necessarily solve this problem either - in government departments they have people who are in charge of IT, so your &quot;customer&quot; may well be completely uninvolved in the day-to-day usage of the system. What is going to be another hard sell to government is having end users work with what they will see as an incomplete system.</description>
		<content:encoded><![CDATA[<p>When working for a previous company I worked on one of these large, late, over-budget, bad press projects for a government department. In addition to the budgetting issues that Nick Oostvogels raises, a major problem was that the actual end users of the system were not involved anywhere in the design, and while there was a lot of to-ing and fro-ing on the design during the design phase, the application was presented to the actual users as a fait accompli and surprise, surprise, didn&#8217;t meet their needs. </p>
<p>I don&#8217;t think Agile will necessarily solve this problem either &#8211; in government departments they have people who are in charge of IT, so your &#8220;customer&#8221; may well be completely uninvolved in the day-to-day usage of the system. What is going to be another hard sell to government is having end users work with what they will see as an incomplete system.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
