Agile Myths

Several Agile myths have been floating around in the industry. Below listed are some of the common ones:

No Planning

  • Agile methods generally conduct more planning than traditional methods starting from

Vision > Roadmap > Release > Iteration > Daily planning (daily Standup)

 

No Estimating

  • Agile methods use a different method of determing how long a piece of work will take
  • Relative sizing is used in Agile
  • Sizing happens at story level in story points and at tasks level in hours.

 

No Documentation

  • Agile Values Working software over comprehensive documentation. Meaning no irrelevant documents. Create documents only if they add value.

 

No Visibility beyond the iteration

Agile provides broad visibility through the following artifacts:

  • Roadmap plans
  • Release plans
  • Product backlog
  • Release Backlog
  • Release BurnUp/Burn down
  • Team Velocity etc

 

Agile is a silver bullet

If you have problems with your development team, making a switch to Agile will not fix them, instead it will make them appear to be more broken.

  • Developers that don’t code well will break the build more often
  • Team with poor communication will communicate poorly more often.
  • Defects will be injected more often and quality issues will appear to be everywhere

The value of Agile is not that it fixes your problems, but that it exposes them early enough to allow the team time to get them fixed.

 

Like my blog?