<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Project lineage management and project portfolio success</title>
  </titleInfo>
  <name type="personal">
    <namePart>Kock, Alexander</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Gemunden, Hans George</namePart>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <publisher>Project Management Journal</publisher>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">print</form>
    <extent>50(5), 2019: p.587-601.</extent>
  </physicalDescription>
  <abstract>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.</abstract>
  <relatedItem type="host">
    <name>
      <namePart>Project Management Journal</namePart>
    </name>
  </relatedItem>
  <recordInfo>
    <recordCreationDate encoding="marc">200221</recordCreationDate>
  </recordInfo>
</mods>
