I haven’t lived through as many methodologies that Boehm and Turner have, and as a result, their book offers an insights into what the industry has been through. For those who’ve only worked in an agile manner, it demonstrates some of the drivers of more rigorous process driven methods, and for those who’ve only worked in the latter style, shows what a more lightweight process brings to the table.
They even offer a model for you to assess to what degree you need to blend the two for your particular situation. I appreciate the model is driven through a risk analysis of your current situation, and they even acknowledge, albeit briefly, how you might move your organisation towards more agility or less when needed.
You definitely won’t agree with everything they say, yet don’t let that blind you to other important things they do have to say. For example, straight from the onset, I don’t see agility and discipline as two opposing forces. Perhaps agility and defined process is more appropriate. I also find it hard to believe some of the situations they describe, such as when the developer working in a waterfall style tracks how much time they spend, to the minute, designing, coding, on the phone, in meetings, etc. I think all developers I know struggle with a weekly timesheet, let alone tracking activities down to every minute of every hour.
Summary: Every agilista should read this book to gain a bit more of a balanced view of their world.