<?xml version="1.0" encoding="UTF-8"?>
<record
    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"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01186nam a2200169   4500</leader>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">512780</subfield>
    <subfield code="d">512780</subfield>
  </datafield>
  <controlfield tag="008">191217b           ||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Eriksson, Kent et al</subfield>
    <subfield code="9">14640</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Projects in the business ecosystem: the case of short sea shipping and logistics </subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="b">Project Management Journal</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">50(2), 2019: p.195-209.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">This article develops a conceptual framework to analyze the governance of projects within a business ecosystem. The framework is applied to the case of a vessel delivery project in the short sea shipping business ecosystem, which is a cargo and logistics infrastructure service at sea. We develop a model that identifies contentious lock-ins among the workflows, and show how they can be resolved by governance that can increase performance of the sea logistics infrastructure. The model shows the interdependence of the short sea shipping business ecosystem and the vessel project, and it shows how performance is enhanced by their integration. - Reproduced.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Ecosystem</subfield>
    <subfield code="9">14641</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Infrastructure </subfield>
    <subfield code="9">14642</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="a">Project Management Journal</subfield>
  </datafield>
  <datafield tag="906" ind1=" " ind2=" ">
    <subfield code="a">Project management </subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">ddc</subfield>
    <subfield code="c">AR</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">ddc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">386828</subfield>
    <subfield code="a">IIPA</subfield>
    <subfield code="b">IIPA</subfield>
    <subfield code="d">2019-12-17</subfield>
    <subfield code="h">50(2), 2019: p.195-209.</subfield>
    <subfield code="p">AR122110</subfield>
    <subfield code="r">2019-12-17</subfield>
    <subfield code="y">AR</subfield>
  </datafield>
</record>
