Useful reference for IT Professionals | Offshoring Information Technology: Sourcing and Outsourcing to a...

Great book! | Offshoring Information Technology: Sourcing and Outsourcing to a Global Workforce | Erran Carmel, Paul Tjia

books:


	• Offshoring Information Technology: Sourcing and Outsourcing to a Global Workforce Erran Carmel, Paul Tjia Cambridge University Press, 2006 - 282 pages average customer review:based on 7 reviews view larger image
	for more information click here

highly recommended

Useful and comprehensive

This is a rather comprehensive look of why software
development gets offshored and of how to do it right
should you decide to try it yourself. The authors are
an academic and a consultant, making the book an
appealing blend of evidence-based theory and practical
advice. The focus is primarily on software
development, with some attention paid to such
IT-enabled services as call centers.

The two most appealing things about the book are its
maintenance of a practical tone and its
comprehensiveness in identifying the many things you
need to get right to get offshoring to work right. For
example, international projects tend to get into
serious difficulty if the customer is unwilling or
unable to provide sufficiently detailed specifications
to bring task ambiguity down to the level that can
survive the communications problems caused by distance
and cultural differences.

The authors put a lot of effort into explaining why
some countries have been successful at growing an
offshoring business and others not. This insight is
valuable for companies into offshoring for the long
haul, as you need to understand how wage rates and
technology depth wax and wane over time.

The book also has a number of chapters written by
specialists in such important ancillary areas as
international contacts and managing cultural
differences. All in all, a very useful book.

for more information click here

Useful reference for IT Professionals

"All things being equal, any manager would prefer to manage a co-located team rather than a distributed team," how true. Authors Erran Carmel and Paul Tija believe that IT managers need to feel as comfortable with managing distributed teams as they are with co-located teams. They intend their book, Offshoring Information Technology, to act as a primer for IT professionals, students and teachers in business and technology programs as well as policy makers and analysts in and around governments. That is a lot of end parties to satisfy, so does this book hit the mark.

Erran Carmel had previously authored, "Global Software Development Teams", in 1999, and has deeply focused on the topic of developing software with global teams for years. It is obvious that a researcher was one of the co-authors, as very accurate listing of references are made, more than you usually see in many of these books on offshoring. These references provide another list of papers and publications that the reader can use for further research. The book makes excellent use of cross-referencing between topics, which also adds to its usage as a good reference tool.

Right off I like the preface in which the authors define the terms offshoring and outsourcing. Since I agree there are many strange definitions leading everyone to think outsourcing means offshoring, this needed to be included. The offshore stage model, previously defined by one of the authors in a research paper, puts the offshoring numbers in to perspective by dividing it in to stages and the number of Fortune 1000 companies currently using the offshoring model. These numbers may be surprising to some, as the actual usage is much smaller than is played up in the media.

The book is full of case studies, most of them fairly interesting. The case study in chapter 9 is meant to show the difference between working in a low-content country versus a high-context country like India. I, along with I believe many practitioners, will look on this case study and say that Christina (not her real name) was not a good manager, no matter where she was working, if they thought dumping a bunch of new work on a team was not going to impact the schedule. Low-content or high-content country aside, the project manager made too many assumptions and may not be the experienced project manager that she thought she was. I think others will see the same when they read it. Another real life case study gives an example of one company trying to do a comparison between countries; what do we learn from it, price wins out over quality in the end, which in reality is often the case.

The emphasis on knowledge transfer is exceptional. This area is often glossed over in many offshoring books. Chapter 7 which is dedicated to managing the offshore transition defines different ways of undertaking knowledge transfer. One of the ways that they describe is to have the developers work in different positions, i.e. put them in to the user's position, so they understand why the user works the way they do. They state that this is new. I started out in banking twenty years ago and this is how I started out, working the user positions of the applications which I was then to develop and maintain, so I do not think this concept is new. But perhaps the authors mean this is new for offshore outsourcing. In all though this section on knowledge transfer is valuable and looks at all of the different types of transfer: skills, process, domain and work and cultural norms. Good emphasis on the fact that the easiest one to achieve is skills transfer, but the other ones are more difficult to achieve. For example it is more difficult to have someone work on dispute resolutions app for credit card processing, when they do not understand how credit card processing works.

Chapter 8 on overcoming distance and time emphasizes and outlines virtual team management. Much of the information presented is included in many books on virtual team management, but as this book is a primer for IT managers, it has a place in this book. Readers will find the suggestions on iteration development; formalizing the iterations and frequency of iterations particularly helpful in a real situation. I whole heartedly agree that this is what builds trust. If you have frequent deliverables, and the remote team meets those frequent deliverables, i.e. they do what they say they are going to do, trust is built. The authors also define the range of deliverables and that it can be anything: plans, outlines, prototypes, simulations, design reviews, test results, software code reviews, module integration and documents. Again I wholeheartedly agree. This will be an area that many IT managers may have to get used to because at first to some it seems like "make work", when in fact all of what is delivered from the offshore is and should be useful for fulfilling the project.

There are a few situations where puzzling statements are used such as the quote on pg. 28, just before a section on IT-enabled services. The quote refers to E-loan and its well-documented offering to its clients of a couple of years ago. At the time E-loan offered the users of their loan service to Press 1 if they wanted their loan processed in 1 day in an Indian center, or to press 2 if they wanted their loan processed in the US which included the statement that the processing may then take longer. In March of 2004, this was written up by many Indian firms as admittance by a US company that Indians are faster. It seems strange that the authors use this statement with no no explanation; for example was it really an admittance that Indians are faster or did it really mean E-loan had 4 times as many processors in India versus the number in the US, thus accounting for how loans could be processed faster there. Or were they working round the clock in India versus only one shift in the US, another reason for the difference. In other areas the authors go to great lengths to explain issues which are reported in the press, such as how offshore labor rates are reported in detail and what they really mean versus the actual total cost of ownership.

The book contains an excellent discussion on the different types of risk, very detailed, to a level not usually defined. Only one area, contractual risk, seemed to be lacking. The authors state that a buyer can mitigate contractual risk by signing a contract with a US company, if you are a US buyer, or with a UK company if you are a UK buyer, i.e. with a company which is also domiciled in your location versus in the offshore location only. The authors also refer to the chapter on Legal issues of offshoring where contractual risk will be further defined. In that chapter, however, only mention to reduce contractual risk is to work with providers who can provide a combination of onshore/offshore resources, thus enabling a buyer to access the provider's onshore resources if necessary. They seem to fail to mention one of the bigger issues; if the contract does go awry, even if you are dealing with the big Indian players, most of the assets that of that vendor are located in the offshore location. If any case, you will have to bring suit against that vendor in their home country. Large buyers already seem to be aware of this based on both outsourcing and vertical conferences I have attended over the last couple of years.

There were two areas where I thought more emphasis could have been made, if this is a book is really meant to assist IT professionals. One of these areas is helping the IT manager assess their own offshore readiness; how do they feel about the process, are they ready to change how they work, are they ready to manage by not walking around? The second area of missed opportunity is assisting IT professionals in defining what could be a new role for them in the global environment, for example by working in and/or managing the offshore office which is responsible for managing the onshore and offshore outsourcing for a client.

Offshoring Information Technology is an informative and educational book for IT managers looking to define their place in the offshoring world. The details provided on the offshoring process and through the case studies will make it easy for an IT professional to determine where they may need to gain additional knowledge to move their career forward. The book will be most useful and most familiar to those IT professionals currently working in or with large scale enterprises as most case studies and examples such as in total cost of ownership and the governance areas, use examples from large enterprises. This book is highly recommended for IT professionals who are looking at career development as well as those persons who are in a position to help their countries promote their outsourcing capabilities.

for more information click here

Great book!

Best off shore book out there... great info...lays it out pretty straight. Easy to understand and follow.

for more information click here

An excellent introductory volume and roadmap

This volume is well-written, lucid and easy to follow. The authors have done an excellent job in providing an explanatory framework for offshoring, as well as giving a realistic look at potential costs and benefits. Their list of suggestions and guidelines is comprehensive. The book avoids the trap of becoming overly technical and steers clear of being specific to any particular country or industry. I was pleasantly surprised to find chapters on such important topics as country-specific legal pitfalls, privacy rights issues, and how to sell the idea of offshoring inside a company resistant to the idea. The authors livened up their material with numerous case studies to illustrate key points. The level of detail they provided on how to write a solid Service Level Agreement (SLA) was also impressive.

Overall this was an excellent volume, and the only two objections that I have are both minor. First, the book could benefit from a small amount of updating; some of the data, especially in Part I of book, dates from 2001-2003. In any other discipline, that would still be considered fairly recent. However in technology, that verges on being stale. In addition, that was the period of the global downturn in IT. The authors' data would be obviously impacted by that global economic event. To be clear: I do not believe that any of the authors' points would be reversed by updating the data. On the contrary, I expect that current data would only strengthen their points, as the trends they identified have only accelerated since the book's first publication. Second, as noted earlier the authors provided several cases of companies who tried offshoring and either failed, or suffered setbacks. Given the fact that offshoring is not the cure-all for every company, it would have also been useful to see a couple of case studies of companies who investigated the offshoring option but decided against it. It is just as important to understand why a company declines to offshore, as it is to understand why they would undertake to do so.

This is a book that I wish I had read before working on several offshoring/outsourcing projects for former employers. It is highly recommended for anyone who is contemplating the offshore option, or who has recently been put in charge of making such an option successful.

for more information click here

Valuable Strategic Perspective

This book does an excellent job of linking offshoring to a company's business strategy. Many companies are pursuing offshoring to take advantage of lower wages in other countries. Chapter 5 shows how cost reduction can be strategic, and the other potential non-cost-based advantages of offshoring. Its treatment is also balanced, showing the downsides, costs, and risks of offshoring as well as the benefits. And it talks about choices companies have in implementing an offshore strategy.

I am Executive Director of a research center on process management, and we have done research in this area. I know and respect Erran Carmel, the author, and Peter Schumacher, who co-authored Chapter 5. Peter's work is grounded in consulting that he has done at the Value Leadership Group, which advises companies on how to think beyond cost cutting and view offshore as an opportunity to build unique competitive advantage.

for more information click here

The decision to source software development to an overseas firm (offshoring) is looked at frequently in simple economic terms - it's cheaper, and skilled labor is easier to find. In practice, however, offshoring is fraught with difficulties. As well as the considerable challenge of controlling projects at a distance, there are differences in culture, language, business methods, politics, and many other issues to contend with. Nevertheless, as many firms have discovered, the benefits of getting it right are too great to ignore. This book explains everything you need to know to put offshoring into practice, avoid the pitfalls, and develop effective working relationships. It covers a comprehensive range of the important offshoring issues: from ROI to strategy, from SLA to culture, from country comparisons to provider marketing. Written for CTOs, CIOs, consultants, and other IT executives, this book is also an excellent introduction to sourcing for business students.

for more information click here

reviews: page 1, 2

hot