Agile Myths and Misconceptions

user_199987 0
Viewed 9356

What are the myths or misconceptions related to Agile?

There are lot of misconceptions related to Agile that an average new comer may fall into. What are the misconceptions in the Agile world and how do you justify that it is truly a misconception?

Update: Summary of Agile Myths

  • Agile doesn't allow documentation
  • Agile methods do not scale
  • Agile means no plan
  • TDD covers all the unit testing needs
  • Pair programming always results in better code
  • Agile is a silver bullet solution to software engineering problems (There is a silver bullet solution)
  • Agile doesn't need up front design
  • We're doing scrum so we don't need to do TDD, Refactoring Pair Programming, etc.
  • One can learn Agile from a book
  • Agile only works for trivial projects
  • Agile always uses "User Stories"

Read the following answers for more information about above myths and for more myths.

scrum agile extreme-programming
18 Answers

Myth: Waterfall always fails.

Reality: Most of the software you're using on your agile project was developed with waterfall. Even BDUF waterfall, in many cases.

user_1194590

Myth: Agile means XP and Scrum

Fact: There are other practices like OpenUP, AMDD, etc.

user_1999870

It's easy to know what to charge your customer. This is alway the biggest problems for us, because we don't know the scope of the project we can't give the customer a fixed price, and most customers demands a fixed price.

user_805890
Related