<?xml version="1.0"?>
<rss version="2.0">
<channel>

  
<title>Coding the Architecture - RUP elaboration</title>
<link>http://www.codingthearchitecture.com/2006/04/03/rup_elaboration.html</link>
<description> I&#039;ve just come across an article called Risk reduction with the RUP phase plan that talks about RUP&#039;s risk-driven approach and provides advice about choosing the right use cases during the elaboration phase.    It is important to educate stakeholders ...</description>
<language>en</language>
<managingEditor>Simon Brown</managingEditor>
<lastBuildDate>Thu, 20 Apr 2006 13:18:33 GMT</lastBuildDate>
  
  

  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Re: RUP elaboration</title>
    <link>http://www.codingthearchitecture.com/2006/04/03/rup_elaboration.html#comment1145539113940</link>
    <description>
      G&#039;day,
Interesting stuff and yes i generally advocate doing either the hardest or more complex use cases/funtions first since these traditionally have the higher risk if not higher business value attached.
However, I&#039;m poring over Crystal Clear at the moment and it seems there&#039;s social reasons in terms of improved morale amongst a team with doing an easy part first to get an &#039;Early Victory&#039; as Cockburn puts it. He actually goes on to advocate &lt;i&gt;Easy thing first, hard thing second&lt;/i&gt; as well which is an interesting combination.
    </description>
    <author>Mark Hesketh</author>
    <comments>http://www.codingthearchitecture.com/2006/04/03/rup_elaboration.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/04/03/rup_elaboration.html#comment1145539113940</guid>
    <pubDate>Thu, 20 Apr 2006 13:18:33 GMT</pubDate>
  </item>
  
  </channel>
</rss>
