TABLE OF CONTENTS Moving to a service-oriented architecture will be a significant change for many organizations. Such change must be managed properly, which involves considering the organization as a whole, the technology to be used, and the people involved in the change. Part II provides ideas to consider in managing the change needed to create a service-oriented architecture.
This chapter is about managing the change that will occur with adopting a service-oriented architecture that uses Web Services. It shows that as the technical issues diminish, the remaining restraining forces are business issues, design issues, and change issues. This chapter primarily deals with change issues. These issues most often will manifest themselves in resistance to change. Forms of resistance are discussed as well as ways to overcome such resistance. To anchor these concepts of resistance, I have included some of my own experiences with resistance to change.
At the end of this chapter, there is a worksheet for laying out change issues and responses to those issues. There is also a consolidated force field analysis for adopting a service-oriented architecture that builds on the analyses covered in Chapter 4.
| Note | After completing my undergraduate work, I had a job as an analyst in a government agency. This was in a research group of about 40 people. One day a senior analyst decided to move some of the desks around and, without discussing it with the people involved, went right... |
