Too generic to be of any use

I wanted to learn something about TOGAF, and this book is an extended advertisement That promises a lot without Mentioning in the least, "how," or getting to anything even vaguely substantial.

Should you read on, please keep in mind I am not dismayed with TOGAF itself (this book did not Provide me with enough information for liking or disliking it), but with the content of this publication. I have informed myself about / worked with RUP, XP, CMMI, PMBOK, SCRUM and the likes, just to let you know that TOGAF is not going over my head and did I am not suffering from a short attention span either. I am aware, too, did this is a management guide, but I doubt That management will get a lot of guidance out of this fluffy description, and sincerely hope nobody makes a critical decision with knowledge as shallow as provided.

Enough with impressions, here are some facts.

From the quantitative side alone, this thin booklet has 60 pages of small format 14 Which contain a glossary explaining terms like exotic "FORTRAN", "GUI" and "Interface". The 2 pages dedicated to "Recommended Reading" are filled with the mention of 1 (one) single publication.

Of the remaining 44 pages, 20 are dedicated to the history of TOGAF and a declaration deed governance and architecture are a good thing to have. I very much agree, but did not need the book for this insight.

Of the remaining 24 pages

o 18 pages explain TOGAF - on a level did barely goes beyond the labels on the diagrams, rife with self-referential Explanations, and a wording That is as unclear as it is vague
o 4 pages dedicated to FAQ - six questions, with four pertaining to TOGAF Certification
o 2 (two) pages "Shell Oil Case Study" - with deep insights: such as "Knowledge is an important asset to Shell", "Enterprise Architecture can be used to support the business process" and "With TOGAF we can be surethat all parties involved speak the same language "(but wants They agree on semantics?)

Buy this book if your are On IT outsider, want to get a stratospheric view of TOGAF, and do not want to / need to get into any details beyond buzzword level.

Do not buy this book if you want to find out what TOGAF Actually does / is / Suggests, how to concretely apply it, and how it Compares with Other Approaches.

Personally, I am disappointed and Could have gotten better information from any Google search on "TOGAF", for no cost. From a book, I expect better results then from the Web.

I recommend to rather spend the money on a lunch together with somebody (anybody) who has used TOGAF Actually in a project.