The Risks of outsourcing IT

<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd">
  <record>
    <leader>00000nab a2200000 i 4500</leader>
    <controlfield tag="001">MAP20071025716</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20080418121252.0</controlfield>
    <controlfield tag="007">hzruuu---uuuu</controlfield>
    <controlfield tag="008">960913e19960321usa||||    | |00010|eng d</controlfield>
    <datafield tag="040" ind1=" " ind2=" ">
      <subfield code="a">MAP</subfield>
      <subfield code="b">spa</subfield>
    </datafield>
    <datafield tag="084" ind1=" " ind2=" ">
      <subfield code="a">922.111</subfield>
    </datafield>
    <datafield tag="100" ind1="1" ind2=" ">
      <subfield code="0">MAPA20080161248</subfield>
      <subfield code="a">Earl, Michael J.</subfield>
    </datafield>
    <datafield tag="245" ind1="1" ind2="4">
      <subfield code="a">The Risks of outsourcing IT</subfield>
      <subfield code="c">Michael J. Earl</subfield>
    </datafield>
    <datafield tag="520" ind1=" " ind2=" ">
      <subfield code="a">Although large corporations continue to outsource IT services, the issues of whether and how to outsource generate strong emotions on the part of managers. Many practitioners and academics now argue for selective or "smart" sourcing. According to this author, this is probably a sensible approach to balance efficiency and effectiveness in providing IT services. However, the author argues that companies should first ask why they should not insource IT services. His perspective is based on an analysis of eleven risks of outsourcing that he identified in discussions whith both buyers and vendors in the IT outsourcing marketplace</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080607067</subfield>
      <subfield code="a">Management estratégico</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080546991</subfield>
      <subfield code="a">Empresas</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080560287</subfield>
      <subfield code="a">Proveedores</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080623791</subfield>
      <subfield code="a">Tecnología de la información</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080615574</subfield>
      <subfield code="a">Tecnologías interactivas</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080587574</subfield>
      <subfield code="a">Riesgo estratégico</subfield>
    </datafield>
    <datafield tag="740" ind1="0" ind2=" ">
      <subfield code="a">Sloan management review</subfield>
    </datafield>
    <datafield tag="773" ind1="0" ind2=" ">
      <subfield code="w">MAP20077000185</subfield>
      <subfield code="t">Sloan management review</subfield>
      <subfield code="d">Boulder</subfield>
      <subfield code="g">Spring 1996 ; p. 26-32</subfield>
    </datafield>
  </record>
</collection>