No doubt, well written and largely relevant, it still suffers from some signs of it being mostly written in the 1970’s. Things that stick out like sore thumbs are ideas like assigng 7 or 8 support personnel to two programmers with only one doing any work and talking about higher level programming languages as something that may come to be popular in the future.

None the less, it’s important for its historical perspective and in general is a good review of how to keep a big software project from grinding to a halt.

If you’ve had some software engineering classes and read some web sites, you’ve probably heard all this, if only because everyone else has so it’s all kind of a given. Good to have it laid out like that for you, though.