There are plenty of anecdotes about companies which, through exceptional feats of agility, have been able to overcome seemingly impossible hurdles and triumph against steep odds. Some of them are even true.
But Agile development, at least with a capital A, remains a huge challenge for many established companies, especially in creating software. After all, it requires them to relinquish control over key aspects of developers and the development process precisely at a time when the risk of failing to exercise effective control can be a career-stopper. So while agility is respected, at least in principle, its wholehearted implementation is sometimes lacking.
The reasons are easy to understand. The Agile manifesto for software innovation smacks of kumbaya. In a ruthlessly competitive world, it calls for collaboration. In an environment dominated by formal processes and structures, it praises individuals and their interactions. Instead of hardball negotiations, it calls for customer collaboration. And instead of adhering to a set of previously adopted plans, it demands the flexibility to respond to change.
RSS
