What do you think?
Rate this book
Building an Enterprise Architecture Practice: Tools, Tips, Best Practices, Ready-to-Use Insights
This book provides practical advice on how to develop an enterprise architecture practice. The authors developed different tools and models to support organizations in implementing and professionalizing an enterprise architecture function. Coverage applies these tools and models to a number of different organizations and, as a result, will help readers avoid potential pitfalls and achieve success with enterprise architecture.
222 pages, Paperback
First published December 31, 2005
3 people are currently reading
39 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 4 of 4 reviews
April 1, 2019
90$
Amazon:As a practicing Enterprise Architect (EA) I have found the to be an good book for reference - if used as a filler along with other books. If your are new to EA this is a good book to have in your library, however it is not the only one you will need. This book is somewhat thin on content in many critical areas, but what is present is of fairly good quality. An example of missing detail would be how to create and maintain an ongoing EA practice that will survive beyond the first budget review cycle. This book talks about the steps of creating a practice in theory and uses a sample company as an example, however it is idealized for the book and does not reflect reality in today's world of "what have you done for me lately" economics. It is quite expensive for what you get, considering that it is just enough to make you realize that you need a whole lot more that you did not get.
This book does exactly what it promises: giving tips and guidance for those that need to start an enterprise architecture unit. The book is not intended for accomplished enterprise architects; those will find only little value - a lot of common ground and already understood practices in enterprise architecture. For those that are far less than accomplished asking themselves: "What am I supposed to do?" the book has a lot to offer. First: the book is a reasonable introduction to enterprise architecture itself and the major issues to be aware of when starting implementing an architecture. Although it falls short of the rigor and detail that is found for example, in the "TOGAF Architecture Development Method" and is based on a older version thereof, it does give the reader the understanding to comprehend the much higher complexity of formal enterprise architecture frameworks. Second: the book stresses the need for a balanced approach by dividing the beginning architect's attention between business benefits to be gained from enterprise architecture and the need for its implementation on the ground. Third: the book gives some valuable advice on how to measure progress whilst gaining architectural maturity in both, organization and implementation. On the shadow side of the book it must be said that the number of criteria (18) to follow-up on is unrealistically high and need to be simplified and reduced (as we did) to 3 or perhaps 4 measurement criteria. Nonetheless, for beginning enterprise architects a good way to start.
The book has 11 years. Too old, doesn't present any market methodology.
Great book for an EA starting out, or for anyone needing a more detailed overview of the process of Enterprise Architecture.
I have not gone through the whole book but going through the first 3 chapters I kind of liked the pace at which the book is written. The fundamentals are clearly documented with equal emphasis on product , process and people. Nice clear diagram to covey the concepts. I think it is a good buy.
Amazon:As a practicing Enterprise Architect (EA) I have found the to be an good book for reference - if used as a filler along with other books. If your are new to EA this is a good book to have in your library, however it is not the only one you will need. This book is somewhat thin on content in many critical areas, but what is present is of fairly good quality. An example of missing detail would be how to create and maintain an ongoing EA practice that will survive beyond the first budget review cycle. This book talks about the steps of creating a practice in theory and uses a sample company as an example, however it is idealized for the book and does not reflect reality in today's world of "what have you done for me lately" economics. It is quite expensive for what you get, considering that it is just enough to make you realize that you need a whole lot more that you did not get.
This book does exactly what it promises: giving tips and guidance for those that need to start an enterprise architecture unit. The book is not intended for accomplished enterprise architects; those will find only little value - a lot of common ground and already understood practices in enterprise architecture. For those that are far less than accomplished asking themselves: "What am I supposed to do?" the book has a lot to offer. First: the book is a reasonable introduction to enterprise architecture itself and the major issues to be aware of when starting implementing an architecture. Although it falls short of the rigor and detail that is found for example, in the "TOGAF Architecture Development Method" and is based on a older version thereof, it does give the reader the understanding to comprehend the much higher complexity of formal enterprise architecture frameworks. Second: the book stresses the need for a balanced approach by dividing the beginning architect's attention between business benefits to be gained from enterprise architecture and the need for its implementation on the ground. Third: the book gives some valuable advice on how to measure progress whilst gaining architectural maturity in both, organization and implementation. On the shadow side of the book it must be said that the number of criteria (18) to follow-up on is unrealistically high and need to be simplified and reduced (as we did) to 3 or perhaps 4 measurement criteria. Nonetheless, for beginning enterprise architects a good way to start.
The book has 11 years. Too old, doesn't present any market methodology.
Great book for an EA starting out, or for anyone needing a more detailed overview of the process of Enterprise Architecture.
I have not gone through the whole book but going through the first 3 chapters I kind of liked the pace at which the book is written. The fundamentals are clearly documented with equal emphasis on product , process and people. Nice clear diagram to covey the concepts. I think it is a good buy.
This entire review has been hidden because of spoilers.
April 13, 2021
Basically what's in the book title matches the content, but, it's not an easy book. The author presents some good examples and tools for what is EA and how to use it depending on your company reality, but I found the examples quite vague and some very difficult to understand and follow.
It's not a bad book per se, but it's not ideal for who is entering on the subject.
It's not a bad book per se, but it's not ideal for who is entering on the subject.
December 27, 2019
Good book, it has a good introduction. The first part is good, but the second part more on an explanation of DYA Framework.
Updated:
"It is difficult for organizations to change. Many strategic initiatives end in failure because the required changes are viewed in isolation rather than in relation to each other"
Updated:
"It is difficult for organizations to change. Many strategic initiatives end in failure because the required changes are viewed in isolation rather than in relation to each other"
Read
April 10, 2016Like the simpler approach then bernard or spewak but more concrete than weill & ross
Displaying 1 - 4 of 4 reviews