<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-20T10:01:57Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/110142" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/110142</identifier><datestamp>2022-01-13T07:55:19Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131023</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor" lang="en_US">Jeanne Ross.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Umbach, Christian</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Massachusetts Institute of Technology. Engineering and Management Program</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2017-06-21T18:21:20Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2017-06-21T18:21:20Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2017</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2017</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/110142</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">987235288</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, School of Engineering, System Design and Management Program, 2017.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Cataloged from PDF version of thesis. Vita.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (pages 84-90).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">How do companies manage and govern external developer platforms? Drawing on platform ecosystem, product management, and IT governance theory a comparison of the developer platform approaches of two technology firms, Akamai, Inc. and Uber Technologies, Inc. is presented. Internal organizational structures and processes are evaluated in combination with external governance mechanism to develop and manage third party partner relations. The case studies test existing IT governance and app developer platform theory with regards to its applicability to platforms for developer products such as APIs. The two teams are analyzed along the dimensions of organizational structure, internal governance process and risk management, external governance and partner relations, as well as KPIs for team steering. A set of key governance mechanisms is identified as success factors for limiting risks around open developer platforms: Internally, API standards and working groups supported by a high degree of interconnectedness support governance and avoid de-acceleration around a company's product development process. Externally, legal agreements around terms of use shift control from the developer to the platform provider. Access limitations can serve as a supporting gatekeeper for access, or punitive penalty in case of violations of agreements. In support of contractual agreements, transparent developer communication around a firm's intended fields of innovation help avoid discords between developer platform providers and its users. Results are discussed.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Christian Umbach.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M. in Engineering and Management</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">90 pages</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en_US">eng</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en_US">Massachusetts Institute of Technology</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en_US">MIT theses are protected by copyright. They may be viewed, downloaded, or printed from this source but further reproduction or distribution in any format is prohibited without written permission.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri" lang="en_US">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Engineering and Management Program.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Management and governance of external developer platforms - at the example of Akamai, Inc. and Uber Technologies, Inc.</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dspace" element="authorsordered">false</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="cerif" element="openaire" authority="" confidence="-1">&lt;Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="bdde3bd4-b4fb-4755-82c3-14034fd83430">
	&lt;Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843&lt;/Type>
	&lt;Language>eng&lt;/Language>
   	&lt;Title>Management and governance of external developer platforms - at the example of Akamai, Inc. and Uber Technologies, Inc.&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2017&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Umbach, Christian&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
	&lt;/Authors>
   	&lt;Editors>
	&lt;/Editors>
    &lt;Publishers>
        &lt;Publisher>
            &lt;DisplayName>Massachusetts Institute of Technology&lt;/DisplayName>
            &lt;OrgUnit />
        &lt;/Publisher>
    &lt;/Publishers>
    &lt;License>http://dspace.mit.edu/handle/1721.1/7582&lt;/License>
    &lt;Keyword>Engineering and Management Program.&lt;/Keyword>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>How do companies manage and govern external developer platforms? Drawing on platform ecosystem, product management, and IT governance theory a comparison of the developer platform approaches of two technology firms, Akamai, Inc. and Uber Technologies, Inc. is presented. Internal organizational structures and processes are evaluated in combination with external governance mechanism to develop and manage third party partner relations. The case studies test existing IT governance and app developer platform theory with regards to its applicability to platforms for developer products such as APIs. The two teams are analyzed along the dimensions of organizational structure, internal governance process and risk management, external governance and partner relations, as well as KPIs for team steering. A set of key governance mechanisms is identified as success factors for limiting risks around open developer platforms: Internally, API standards and working groups supported by a high degree of interconnectedness support governance and avoid de-acceleration around a company&amp;apos;s product development process. Externally, legal agreements around terms of use shift control from the developer to the platform provider. Access limitations can serve as a supporting gatekeeper for access, or punitive penalty in case of violations of agreements. In support of contractual agreements, transparent developer communication around a firm&amp;apos;s intended fields of innovation help avoid discords between developer platform providers and its users. Results are discussed.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>