I just read an interesting book about Lockheed's skunkworks program. It covers a bit of WWII, Korea, Vietnam, but mostly the post-Vietnam era.
http://www.amazon.com/Skunk-Works-Personal-Memoir-Lockheed/d...
That caliber of leadership and oversight requires immense skill, authority over capital allocation, AND trust from the next level up. Organizations that can maintain this are rare and typically have a brutal filtering process.
I come across mentions of WWII era projects, designs of famous aircraft etc where the designs were incredibly well suited to the needs, and produced in incredibly short time-frames. Some of that is obviously the war-time focus, but I also notice that in many of those projects the lead position is not a non-technical manager, but a technical chief engineer where management functions must have been subservient. Unfortunately, there isn't a huge amount written about the organizational day-to-day project structures during WWII.
I think at least some of the appeal of startups and smaller companies for technically oriented people is that division of responsibility is not as formalized and contributions can flow more easily between different domains. But again, startups are structured where technical founders are at the levers of control, and that's inverted from how many companies end up organized as they grow.