Catching a glimpse of a snake charmer on a busy Indian
metropolis, is a big myth that many foreigners visiting India still cherish
(wishful thinking you might say!). But the reality is that snake charming is
illegal in India (India Wildlife Act) and has been for a number of years,
although snake charmers do still exist and are now an ‘elusive’ sight. But the
myth still exists and something similar is the case with the agile
projects and the myths surrounding them.
If you take a look at the the annual state of agile surveys for
last few years, they have been throwing similar results wrt 'Concerns' about Agile
(read as Myths – see below Reference1), reflecting the dismal failure of the agile
enthusiasts to be unable to bust the folk tales surrounding the agile projects
delivery. This post hopes to therefore Smash the Top
5 agile project myths (popular faolke tales), with
a pinch of sugar/salt (take your pick) for added flavour.
Source: Reference 1
Myth1–
Agile projects do No Planning
The traditional projects have a Big plan upfront, and planning
is highly visible, with a complete plethora of activities, draining the energy
for a couple of weeks\months, and resulting in a sometimes scary GANTT chart.
But Agile projects instead focus on Continuous planning, and planning is therefore invisible!
