Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Why Agile process when it has so many drawbacks?

 
Akanksha Mittal
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 12617
IntelliJ IDE Ruby
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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...
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34410
346
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Akanksha,
It sounds like you think Agile is more work. Why?

And have you listed the drawbacks of waterfall? They exist as well.
 
David Newton
Author
Rancher
Posts: 12617
IntelliJ IDE Ruby
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic