I agree; I've had one recent job that was agile, and it was done pretty well. Neither management nor customers were overbearing, if things didn't get done on t

I agree; I've had one recent job that was agile, and it was done pretty well. Neither management nor customers were overbearing, if things didn't get done on time we'd talk about why the estimate was so wrong, if things took longer than expected we'd just push them to the next sprint, etc. Overall, the whole thing was just a useful way of keeping people on-track, and aware of what their coworkers were doing, and organizing and prioritizing work tasks in a flexible manner, and providing a process to keep things that way. The stuff with Fibonacci numbers was a bit silly but it was fine; it's just a rough way of estimating the difficulty of a task (which is different from the time needed, because this varies by developer skill). It was also good for making sure that new code got reviewed and tested properly before being merged. Of course, it doesn't work well if you use it in a cargo-cult manner. It needs to be applied intelligently to what your team is doing.