<?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-19T07:05:13Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/132811" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/132811</identifier><datestamp>2025-10-30T17:51:28Z</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">Steven D. Eppinger.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Crofoot, Lisa.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Engineering and Management Program.</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="date" qualifier="accessioned">2021-10-08T16:48:19Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2021-10-08T16:48:19Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2020</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2020</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://hdl.handle.net/1721.1/132811</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">1262990574</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, May, 2020</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Cataloged from the official version of thesis.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (pages 59-61).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Agile product development promises improved productivity, fast development cycles, and high employee satisfaction. Large-scale agile development frameworks (e.g., SAFe, Sage, Scrum [at symbol] Scale, Spotify, LeSS) adapt agile principles for programs where multiple teams must work together to build complex products and services. In this research, we explore how large-scale agile organizations manage cross-team interfaces and dependencies. We reviewed existing frameworks and interviewed fourteen individuals from six different organizations. We learned that many large-scale agile practices act as coordination mechanisms. Large-scale agile programs use these coordination mechanisms to: (1) reduce the quantity and complexity of cross-team interfaces; (2) identify interfaces up front; (3) surface interfaces as they emerge in development; (4) manage interfaces during development; and (5) build a shared understanding between teams. Experienced practitioners consider how agile roles, events, artifacts, and other mechanisms contribute to coordination in each of these areas. While large-scale agile frameworks provide recommended practices, we suggest programs should adapt these approaches to fit their specific needs. Future research may help to evolve large-scale agile practices by further exploring: product, process and program architecture, coordination mechanisms and effectiveness, and leadership and accountability.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Lisa Crofoot.</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="description" qualifier="collection" lang="en_US">S.M.inEngineeringandManagement Massachusetts Institute of Technology, System Design and Management Program</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">61 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 may be protected by copyright. Please reuse MIT thesis content according to the MIT Libraries Permissions Policy, which is available through the URL provided.</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 of cross-team interfaces in large-scale agile development</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="imported" lang="en_US">2021-10-08T16:48:19Z</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="mit" element="thesis" qualifier="degree" lang="en_US">Master</dim:field>
   <dim:field mdschema="mit" element="thesis" qualifier="department" lang="en_US">SysDes</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="b068f970-1ef1-46e0-913a-d6e7d1ca82f3">
	&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 of cross-team interfaces in large-scale agile development&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2020&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Crofoot, Lisa.&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>Agile product development promises improved productivity, fast development cycles, and high employee satisfaction. Large-scale agile development frameworks (e.g., SAFe, Sage, Scrum [at symbol] Scale, Spotify, LeSS) adapt agile principles for programs where multiple teams must work together to build complex products and services. In this research, we explore how large-scale agile organizations manage cross-team interfaces and dependencies. We reviewed existing frameworks and interviewed fourteen individuals from six different organizations. We learned that many large-scale agile practices act as coordination mechanisms. Large-scale agile programs use these coordination mechanisms to: (1) reduce the quantity and complexity of cross-team interfaces; (2) identify interfaces up front; (3) surface interfaces as they emerge in development; (4) manage interfaces during development; and (5) build a shared understanding between teams. Experienced practitioners consider how agile roles, events, artifacts, and other mechanisms contribute to coordination in each of these areas. While large-scale agile frameworks provide recommended practices, we suggest programs should adapt these approaches to fit their specific needs. Future research may help to evolve large-scale agile practices by further exploring: product, process and program architecture, coordination mechanisms and effectiveness, and leadership and accountability.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>