7 Agile Myths


Today I had a lightning talk at the ACE!Conference in Krakow (as you probably know, I’m a lightning talk addict ;)) and talked about seven Agile Myths. You’ll hear about these myths most of the time on management level, but some of them can be found on the development level, too. IMHO it’s important to be aware of these myths to be prepared for possible discussions.

Agile = No documentation

This is one of the most famous myths and I think we have to blame the agile manifesto for this. The line “Working software over comprehensive documentation” is often misunderstood with no documentation at all. But how could agile Frameworks like Scrum survive in highly regulated environments like the medical or financial industry if this would be right. For sure there is documentation, but we don’t waste time on documents that deliver no value to the project.

You can read the complete blog post on marcloeffler.eu.

11 thoughts on “7 Agile Myths”

  1. Hello Marc: I generally agree with all of the myths and I would certainly include an honorable mention for the No Manager role. This role does need to adapt, as do many of the hands off roles in larger organizations (including Project Managers, Technical Manager, Conceptual Architects, etc.)

    As to Agile is Faster. The terminology needs to be refined. All of my teams deliver in the first sprint. If they are not delivering then they are below my personal standards. Now, what are they delivering: Naturally a piece of value that can either be delivered to production or demonstrable in a way that our business partners can say “great keep going” or “not good, cancel the project”. Of course, there’s a middle ground but your audience needs to understand this.

    As to Agile = Software development. Absolutely correct! Agile applies to the entire organization but enabling that to occur is a big undertaking which a traditional organizations avoid. The biggest reason is that it’s a large undertaking, the process owners are often those who need to move on or have transferable skills and sadly, the Development CTOs/VP/Directors often sell agile an a development methodology in order to build their own empire. (Seen it many times.)

    However, that’s not the point I really want to make. Being pedantic, I would ask you to change your comparison of trees growing in the desert because there are many different types of trees that indeed thrive in parched, arid areas; namely deserts.

    All good stuff.


    1. Hi David

      Thanks for your comment! I’m currently working on refining my myths. Do you have a better metaphor for the tree in the desert? Maybe placing a human in the desert?


Leave a Reply

Your email address will not be published. Required fields are marked *


Notify me of followup comments via e-mail. You can also subscribe without commenting.