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, Ricardo Puttini, Zaigham Mahmood
Description:“This is a great book on the topic of cloud computing.” --Kapil Bakshi, Architecture and Strategy, Cisco Systems Inc. “We will recommend this book to Oracle customers, partners, and users for their journey toward cloud computing.” --Jurgen Kress, Fusion Middleware Partner Adoption, ...
by Ian Tyndall
Description:Cloud computing is disrupting corporate IT departments. This book examines the scholarly literature available on this topic through spring 2010.
by Lars Nielsen
Description:Here it is ... the bestseller now revised and expanded to reveal the most important Cloud innovations for 2013, including key Big Data tools from Amazon, IBM, Google, Microsoft and many other industry leaders. This concise, jargon-free volume fully explains the state-of-the-art (and ...