Hi Marc,
@Freelancers vs company workers
it is actually suited for both.
Depending on your company culture,country culture and your seniority it could be that it is more interesting for the software lead/teamlead/architect/ba than the junior junior tech guy, but I think it is an overall guide for anyone who needs to put requirements into working software. The steps are the same, the conclusion is the same...yep.
@Putting your foot down comment
As I also wrote in the book: If it happens occasionally for , let's say, a trade show or important customer demo then there's nothing wrong with that. If you are continuously (simple rule: more than once a month) asked to stay late on Fridays and nights to deploy a crazy hotfix, then you are having problems - but I probably do not need to tell you that.
A lot of programmers have that sentiment it would make them look bad and so in the worst case nothing changes, at one point the pressure pipe explodes and morale goes down. And you essentially put yourself in a one-down position towards your boss. It is then really up to you if you want to continue like that forever ever - i dont