“A common cause of disaster in software development is that the end product is precisely what the customer originally ordered,” an article in the September 20th 2001 print edition of The Economist said. “In a world moving at Internet speed, a customer’s objectives are constantly being revised, so programmers have to be able to hit a moving target. Is there any formula for coping with this sort of unpredictability?
“With this in mind, 17 leading software gurus holed up in a Utah ski resort in February 2001 to produce a Manifesto for Agile Software Development. Portentous as it may sound, the manifesto represented the distillation of several successful team-oriented techniques, and hoped to inspire innovation groups outside the confines of software development.” [click to continue…]
VN:F [1.8.3_1051]
Rating: 4.0/5 (2 votes cast)
Tagged as:
agile manifesto,
software
I met a Malawian, a gatekeeper at a game reserve there, who was mauled during a lion attack. His face is terribly scarred and he’s missing an ear; but he’s alive.
That got me thinking about you. It’s likely you’ve been mauled too. Not by a lion, but by something more powerful and pervasive: Bureaucracy. And you’ve got the scars to prove it; yet somehow you’ve made it through.
Bureaucracy is the mother-of-all legacy systems. It directs what you do and how you do it. And if you want to overturn it, or simply change it a little, or arrest its operation for just one team, it won’t let you. I’ll bet it’s the single biggest impediment to your agile ambitions. But you’re correct to want to change it, because these days bureaucracy is not the best organizing principle we can think of. [click to continue…]
VN:F [1.8.3_1051]
Rating: 4.5/5 (2 votes cast)
Tagged as:
agile,
bureaucracy,
change,
entrepreneur,
leader