Or a sudoku solver.
Some use this to say TDD - which has ties to agile - doesn't work. But most people conclude that TDD isn't a silver bullet and you have to know about your problem domain before diving in.
Here's someone elses' blog post which includes links to both sets of posts: http://ravimohan.blogspot.com/2007/04/learning-from-sudoku-s...
Agile can't generate insight from nothing, it's not a silver bullet. But at least if you have some unit tests around your cool new code, you know that you won't accidentally break it later.
Wasn't the point of Royce's paper that waterfall wasn't even suited to avionics?
I also like to ask about the specific (and testable!) assertion Brooks made in his most famous essay.
Anyone who can answer those questions well demonstrates a working understanding of project management.
That would be interesting. Scrum says that your team should get themselves an appropriate set of tools and processes for the task at hand, and iterate, then inspect and adapt.
For a mission-critical lives-on-the-line software system, I'd imagine that there would be a lot of simulation and testing before the production release. Do you see a problem with that?
The accusation is, that the "scrum master/coach" role in agile has gone from being an in-team activity to being a project management activity. I do think that is true. I also agree that Agile has become a buzzword that companies are adopting without truly understanding it (in the vein of http://www.halfarsedagilemanifesto.org/ )
But the reason Agile won't be killed is the same reason Waterfall hasn't been killed: it's the optimal choice in some scenarios.
(And before you sneer at Waterfall, go build me a nuclear power station with Agile).