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 Thomas Erl
Description:This is a comprehensive tutorial that teaches fundamental and advanced SOA design principles, supplemented with detailed case studies and technologies used to implement SOAs in the real world. ***We'll have cover endorsements from Tom Glover, who leads IBM's Web Services Standards ini...
by Judith Hurwitz, Robin Bloor, Marcia Kaufman, Fern Halper
Description:Feeling overwhelmed by the buzz about SOA—service oriented architecture? Take heart! Service Oriented Architecture For Dummies, 2nd Edition makes it easy to understand, plan, and implement the latest SOA solutions for your business. Whether you’re the IT person responsible for develop...
by Thomas Erl
Description:As XML becomes an increasingly significant part of the IT mainstream, expert guidance and common-sense strategies are required to avoid the many pitfalls of applying XML incorrectly or allowing it to be used in an uncontrolled manner. This book acts as a knowledge base for issues rela...