<?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: Exam essay: Rational Unified Process</title>
	<atom:link href="http://visual.placodermi.org/2009/01/02/exam-essay-rational-unified-process/feed/" rel="self" type="application/rss+xml" />
	<link>http://visual.placodermi.org/2009/01/02/exam-essay-rational-unified-process/</link>
	<description></description>
	<lastBuildDate>Fri, 20 Jan 2012 07:35:46 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Malek</title>
		<link>http://visual.placodermi.org/2009/01/02/exam-essay-rational-unified-process/comment-page-1/#comment-1025</link>
		<dc:creator>Chris Malek</dc:creator>
		<pubDate>Fri, 02 Jan 2009 07:21:50 +0000</pubDate>
		<guid isPermaLink="false">http://visual.placodermi.org/?p=454#comment-1025</guid>
		<description>&lt;strong&gt;My self critique:&lt;/strong&gt;

Does RUP necessitate expert staff or not?  This is actually an important point because I’m going to be saying in my article on agile software methodology that agile methodologies necessitate experts, and I want to know whether I can say that RUP does not require that.  Some say that segmentation allows specialists.  I can imagine situations in which your programmers receive fully fleshed out class diagrams and operational contracts, and in that case, you don’t necessarily need expert programmers: junior programmers will do just fine.  I suppose that you can say that RUP does allow junior staff in some roles, but expert staff in most.  There is the point that RUP incorporates both uncertainty and change and I think that more expert people will be able to handle that better.

Is RUP a more complex methodology than waterfall?  In its full form it is heavy, as heavy as waterfall perhaps, but it is perhaps more difficult because of the necessary team self-reflection, incorporating user feedback and the uncertainty, especially early on, of what the final product will do.</description>
		<content:encoded><![CDATA[<p><strong>My self critique:</strong></p>
<p>Does RUP necessitate expert staff or not?  This is actually an important point because I’m going to be saying in my article on agile software methodology that agile methodologies necessitate experts, and I want to know whether I can say that RUP does not require that.  Some say that segmentation allows specialists.  I can imagine situations in which your programmers receive fully fleshed out class diagrams and operational contracts, and in that case, you don’t necessarily need expert programmers: junior programmers will do just fine.  I suppose that you can say that RUP does allow junior staff in some roles, but expert staff in most.  There is the point that RUP incorporates both uncertainty and change and I think that more expert people will be able to handle that better.</p>
<p>Is RUP a more complex methodology than waterfall?  In its full form it is heavy, as heavy as waterfall perhaps, but it is perhaps more difficult because of the necessary team self-reflection, incorporating user feedback and the uncertainty, especially early on, of what the final product will do.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

