David Linthicum may very well have coined the term “SOA Rage” in his recent posting. His posting had to do with resistance to change that can easily occur with SOA efforts. David says that, “I guess there is a certain amount of rage that’s going to be a part of any change; it’s your job to minimize it.” My issue is that David and others posting on the same topic do not provide any substantive suggestions on how to identify and minimize potential change issues. There are ways to do that. Take a look at Chapters 8 and 9 in Web Services and Service-Oriented Architectures: The Savvy Manager’s Guide. You will find a discussion on how force-field diagrams could help you identify and minimize resistance to change. By the way, I wrote those chapters in 2002. To my knowledge, no other SOA-related book discusses change to the degree I do in that book.

Search this site
Custom Search
Resource Books at Amazon.com
by Nick Ramirez
Description: An in-and-out, to-the-point introduction to Windows Installer XML Overview Brings the reader up to speed on all of the major features of WiX, including the new bootstrapper engine, Burn. Provides a richer understanding of the underlying Windows Installer technology. Showcases the...
by Joe Fawcett, Danny Ayers, Liam R. E. Quin
Description:A complete update covering the many advances to the XML language The XML language has become the standard for writing documents on the Internet and is constantly improving and evolving. This new edition covers all the many new XML-based technologies that have appeared since the previo...
by Kevin Howard Goldberg
Description: What is XML? XML, or eXtensible Markup Language, is a specification for storing information. It is also a specification for describing the structure of that information. And while XML is a markup language (just like HTML), XML has no tags of its own. It allows the person writing the ...