This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
/ JeanLouis<br /><i>"software development has been, is, and will remain fundamentally hard" (Grady Booch)</i><br /> <br />Take a look at <a href="http://www.epfwiki.net/wikis/openup/" target="_blank" rel="nofollow">Agile OpenUP</a> in the Eclipse community
DSDM isn't very common here in the states, so I'm afraid I'm not very familiar with it. I just looked at OpenUP for the first time and it seemed fairly typical, although with a phasist approach to design that seems a little ivory tower. That could be a result of trying to break everything into "workflows"--development as actually practiced involves thinking at multiple levels simultaneously, but that's hard to express in a workflow diagram.
What do you think of them?
James Shore, coauthor of <a href="http://www.amazon.com/Art-Agile-Development-James-Shore/dp/0596527675" target="_blank" rel="nofollow">The Art of Agile Development</a>. Website and blog at <a href="http://www.jamesshore.com" target="_blank" rel="nofollow">http://www.jamesshore.com</A> .
Joined: Nov 12, 2001
Sorry, DSDM is not very popular in Canada either.
About OpenUP, as stated in that post, I see it as a fair and sound process following the Agile principles.
Regarding the phases in open up, no need to be afraid. OpenUP really supports and encourages iterative development. Phases are just there to identified some key milestones through the whole delivery process
I didn't yet take a closer look at OpenUP, but the value curve in the phases diagram look untypical for an Agile project to me.
What's positive about is that value is delivered throughout the project, not concentrated at the end.
Still, the Agile processes that I'm familiar with will deliver the highest value features first (which gives highest return of investment and lowers architectural risk), which should lead to a steeper curve at the beginning which flattens to the end of the project.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: The Art of Agile Development: Opinion about non-XP methodologies