wood burning stoves 2.0*
The moose likes Agile and Other Processes and the fly likes Preferred methodology Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Preferred methodology" Watch "Preferred methodology" New topic
Author

Preferred methodology

Vedhas Pitkar
Ranch Hand

Joined: Jan 27, 2001
Posts: 445
IMHO, there's no one particular "development methodology" which would be applicable to all project sizes & scopes. For me, a mix of the waterfall model & the iterative model would work fine.

Start building on the iterative model, but the phases should be that of a waterfall model. This would ensure that the software is capable of sudden changes & also that everything is well documented.
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
What makes you want more waterfall?

I would like to wait longer for feedback on any decision.

I would like to discover bugs as late as possible.

I would like to invest in analysis and design for things that might not be built.

I would like to get my software in one delivery, all or nothing.

I'm being sarcastic of course, but I don't want to shut you down. Seriously, what would you like to have more of that waterfall gives you?


A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
I share Stan's puzzlement. I'm especially puzzled by the statement that waterfall is better at allowing sudden changes than iterative development...


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
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

Some developers hate change.They will complain when requirements are not fixed. Commonly heard -'Requirements are not known properly. How can we proceed' 'Things have changed suddenly. How can we incorporate it now ?'. I used to think like this before. May be because of this people like waterfall


Groovy
Christophe Verré
Sheriff

Joined: Nov 24, 2005
Posts: 14688
    
  16


I would like to wait longer for feedback on any decision.
I would like to discover bugs as late as possible.
I would like to invest in analysis and design for things that might not be built.
I would like to get my software in one delivery, all or nothing.

Great Stan. You've summed up well the mess I'm in

I would like to invest in analysis and design for things that might not be built.

This makes me think about a program I've just finished. For testing purpose, I received a simulation sheet with all data patterns we may have. I was surprised that there were patterns I didn't even think of, and of course, did not support. I asked and I was told that there were no such patterns. So why did you put that in the doc ? "Well, we might have to support that one day. But not now. We just put everything here". I thought that was wasting both their and my time.


[My Blog]
All roads lead to JavaRanch
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
I probably remembered most of that list from the wonderful Waterefall 2006 convention site.

The practice of writing complete use cases and putting them under change prevention, er, control encourages us to put everything we can possibly think of in them. We start to think we're being paid by the pound and make up requirements all day long.

I've only gotten a fraction of the way into agile, but the bits that paid off the biggest were breaking use cases into story sized chunks and prioritizing them with real live index cards. At first a fair number of cards fell off the end of the sorting table, right into the trash. Eventually we just quit making up junk requirements.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Preferred methodology