*
The moose likes Agile and Other Processes and the fly likes Why Agile process when it has so many drawbacks? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Why Agile process when it has so many drawbacks?" Watch "Why Agile process when it has so many drawbacks?" New topic
Author

Why Agile process when it has so many drawbacks?

Akanksha Mittal
Greenhorn

Joined: Jul 29, 2009
Posts: 26
Hi,

I am a developer & have never worked in agile methodology. But whatever I have heard of this process is negative only.

Why do people have to leave documentation and sit in a room & do just anything & everything. I agree it is faster but do not fully agree with any other benefit.

Can somebody explain why?

If I would have been in an agile process, I would either have sacrificed my family or left the job!! Or may be I am thinking that way but its not really that much difficult.
David Newton
Author
Rancher

Joined: Sep 29, 2008
Posts: 12617

That's a pretty broad question, and it seems like you have some misconceptions about what "agile" means (although everybody has their own definition). Which parts in particular do you not see the benefit of?
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Akanksha Mittal wrote:
I am a developer & have never worked in agile methodology. But whatever I have heard of this process is negative only.


I'm working according to Agile approaches for a decade now, and I'll never go back.


Why do people have to leave documentation


They don't. It's a common misconception that in Agile you produce no documentation.

What is true is that when you switch to an Agile approach, you will quite likely produce less, and different forms of documentation than before.

Documentation as such doesn't actually have value. It only has value when it gets used. And that is because the actual value is in getting the information in the heads of the right people. But documentation is just one way to do that. Often there are alternatives that are actually more effective - face to face communication, close collaboration in a team workspace, "executable documentation" such as a suite of Acceptance Tests etc.

See also http://xprogramming.com/docindex


and sit in a room & do just anything & everything.


I haven't yet found a developer who didn't like working in a team room once he tried it.

Not sure what you mean by "doing just anything and everything". Care to elaborate?


I agree it is faster but do not fully agree with any other benefit.


In my experience, being faster is actually not the main benefit of Agile. To me they are

* higher quality
* earlier return of investment
* earlier feedback and quicker reaction to new situations/learning
* more fun


If I would have been in an agile process, I would either have sacrificed my family or left the job!!


Again, not sure what you mean by "having sacrificed your family", or why you think that's what would have happened...


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
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 30353
    
150

Akanksha,
It sounds like you think Agile is more work. Why?

And have you listed the drawbacks of waterfall? They exist as well.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
David Newton
Author
Rancher

Joined: Sep 29, 2008
Posts: 12617

IMO not only is waterfall more work, the *kind* of work it is isn't overly helpful in meeting expectations or actually producing good code.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Why Agile process when it has so many drawbacks?