The Turn (1993)
theatlantic.com
theatlantic.com
Reminds me quite a bit of programmers who insist that any formal developments process (including lightweight agile ones) is a crutch needed only by mediocre developers (which they of course don't need) and invented by companies who can't hire only the best (where they of course would never work).
By "formal", I just mean that there's a written process for what to do when that everyone follows as long as they do not have a very good specific reason to deviate from it (and if that happens too often you try to find the reason and fix it, possibly by adjusting the process).
Things that make a big difference to me: continuous integration. Time-boxed releases focused on fully-working incremental business value. Regular reviews of the process itself. Rigid rules for what should and should not be discussed in meetings (at least the recurring all-hands ones).
Measurable differences? No, just heaps of anecdotal evidence. There's damn little quantifiable evidence for anything at project scale, no matter which industry, probably because differences between projects are so large and controlled experiments at that scale almost impossible.
Though there are similarities in that area as well: without any kind of coordinated planning, measurement of progress, and feedback-gathering, you're unable to see in what state the project really is, whether you're able to meet deadlines, stay in budget, and actually building the right thing.
And while you can do all that without a formal process, can you do it repeatably (so results are comparable and composable) across time and team members? Can you be sure you won't forget doing some of it when you're busy? How often and when should you ideally do it?
Once you've thought about that, discussed it with your team members and come to an agreement with them, what you have is a formal process. The only thing left to do is to write it down so you'll still remember it next month.
BTW, the relevant scene starts at 2:08.
For enormous fun, dangle your earbuds from their cables during the large maneuvers during take-off and landing. The wires seem to have a life all their own. People around you will stare, mesmerized. For some reason you really seem to want that wire dangling to match what you see outside.
Edit: On thinking about it, it might be double strange because you're "feeling" the bank from what you see outside and feeling the accelerations/decelerations (which may or may not match the plane's pitch which you also get from sight) that big planes do as they fly their patterns. These run together in your brain. It sometimes responds to pitch seen outside, sometimes to acceleration you feel, but never to the roll you expect from what you see. So it seems oddly, randomly broken.
Also, apparently previously discussed - http://news.ycombinator.com/item?id=1503860