Looking past the military stuff, some of them are quite applicable to startups even to this day.
The number of people having any connection with the project must be restricted in an almost vicious manner. Use a small number of good people (10% to 25% compared to the so-called normal systems).
This is something large corporations struggle with today. The prevalence of of startups seems to indicate that there isn't a good alternative to the track of promoting good engineers to management. Engineers who want to do design work don't want to be managers.
I'm reminded of a charter school I read about in the NYT(don't have the link sorry) that was unusual for paying its best teachers more than the principal. They had a principal who understood that even though he was the teachers boss he needed to attract good teachers with high salary.
I've seen how destructive not having those two policies in play can be, even in a small organization. You have to give the people on charge the authority and ability to get things done, and you have to make sure the people who do the work get the chance to see firsthand whether or not the work "flies" in the real world.
I found this one on documentation particularly applicable.. 5. There must be a minimum number of reports required, but important work must be recorded thoroughly.