Agile means No Planning – FALSE
Agile probably has more planning. Again planning is spread out through the whole development project rather than at the front and it is the work of everybody rather than one or two appointed individuals.
Agile means No Documentation – FALSE
You can have as much documentation as you like in Agile. Documentation is just another deliverable, if it brings you value then schedule it and product it like anything else.
Agile is New – WRONG
No Agile manifesto was published in 2001, the Scrum pattern was in 1998 and there are some who trace things back further.
Agile means No Design – INCORRECT
Agile probably means MORE DESIGN. Design is inherent all the way through development (Discovery, Alpha and Beta) at every planning meeting and more. Agile does mean the end of big-up-front design which is invalidated five minutes after someone starts coding.
Agile can only be used for building software – FALSE
There isn’t a ‘one size fits all’ tool or process for managing projects, both Agile and Waterfall have there place for any kind of project, not just IT projects. You can use this simple technique to help you decide which methodology to choose. If there are more unknowns than knowns, use Agile. Likewise, if you have more knowns than unknowns use a Waterfall based method.
Developers do what they want – FALSE
No, if this is true for you then you are doing it wrong, please call me. Agile needs more discipline from the team and what gets done should be lead from a specific role; usually the product owner or the scrum master.
Work must fit in a Sprint – WRONG
If you are doing hard core Scrum then some would say yes. It’s okay to let stories span sprints to improve flow if needed, but don’t let them continue forever. Alternatively, you could think about breaking down the story or creating an epic.