<?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>01273nam a2200157   4500</leader>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">513466</subfield>
    <subfield code="d">513466</subfield>
  </datafield>
  <controlfield tag="008">200221b           ||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Kock, Alexander</subfield>
    <subfield code="9">16360</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Project lineage management and project portfolio success</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="b">Project Management Journal</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">50(5), 2019: p.587-601.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Project portfolio approaches consider various concurrent project interdependencies but typically neglect longitudinal interdependencies. These are important for exploratory projects, which create strategic options. If these options are not exploited in successive projects they become lost opportunities. This study analyzes 138 firms regarding their extent to consciously manage project sequences. We differentiate between proactive lineage (planning a roadmap of future projects) and reactive lineage (using learnings from past projects). Results show that both practices are positively and independently related to portfolio success. We derive suggestions for future research and discuss which theoretical foundations could be used to better understand the impact of lineage management. - Reproduced.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Gemunden, Hans George</subfield>
    <subfield code="9">16361</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">387503</subfield>
    <subfield code="a">IIPA</subfield>
    <subfield code="b">IIPA</subfield>
    <subfield code="d">2020-02-21</subfield>
    <subfield code="h">50(5), 2019: p.587-601.</subfield>
    <subfield code="p">AR122642</subfield>
    <subfield code="r">2020-02-21</subfield>
    <subfield code="y">AR</subfield>
  </datafield>
</record>
