FW: [object-technology] [Jeff Sutherland's Object Technology Web Site] Seven Steps to Pain and Suffering with the Rational Unified Process

 

-----Original Message-----
From: Jeff Sutherland [mailto:jeff.sutherland@xxxxxxxxxxxx]
Sent: Friday, December 20, 2002 5:14 PM
To: object-technology@xxxxxxxxxxxxxxx
Subject: [object-technology] [Jeff Sutherland's Object Technology Web Site] Seven Steps to Pain and Suffering with the Rational Unified Process

I'v'e gotten a lot of email about the RUP patterns of failure paper, including email from the authors. The lead author, Craig Larman, has generously offered to provide copies of his paper to anyone that communicates with him through his website, www.craiglarman.com.


Larman, Craig el al. How to Fail with the Rational Unified Process: Seven Steps to Pain and Suffering. Valtech Technologies and Rational Software, 2001.

"In order to ensure absolute misunderstanding and failure in RUP adoption, we provide the following checklist or score sheet. Of course, the more points scored, the more successful the RUP failure.

You know you didn’t understand the RUP when …
o You think that inception = requirements; elaboration = design; and construction = implementation! .
o You think that the purpose of elaboration is to fully and carefully define models, which are translated into code during construction.
o You think that only prototypes are created in elaboration. In reality, the production-quality core of the risky architectural elements should be programmed in elaboration.
o You try to define most of the requirements before starting design or implementation.
o You try to define most of the design before starting implementation.
o A “long time” is spent doing requirements or design work before programming starts.
o An organization considers that a suitable iteration length is measured in months, rather than weeks.
o You think that the pre-programming phase of UML diagramming and design activities is a time to fully and accurately define designs and models in great detail, and of programming as a simple mechanical translation of these into code.
o You try to plan a project in detail from start to finish, allocating! the work to each iteration; you try to speculatively predict all the iterations, and what will happen in each one.
o An organization wants believable plans and estimates for projects before they have entered the elaboration phase.
o An organization thinks that adopting the RUP means to do many of the possible activities and create many documents, and thinks of or experiences the RUP as a formal process with many steps to be followed.

We are confident that by ... applying the checklist of misunderstandings, your adoption of the RUP and iterative development will be a spectacular mess."

--
Posted by Jeff Sutherland to Jeff Sutherland's Object Technology Web Site at 12/20/2002 4:52:48 PM

Powered by Blogger Pro

To Post a message, send it to:   object-technology@xxxxxxxxxxx

To Unsubscribe, send a blank message to: object-technology-unsubscribe@xxxxxxxxxxx

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

To Post a message, send it to:   scrumdevelopment@xxxxxxxxxxx
To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@xxxxxxxxxxx

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.