<?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-19T22:58:45Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/105297" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/105297</identifier><datestamp>2022-01-13T07:54:46Z</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">Nelson P. Repenning.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Garcia, Erik Roberto</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">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Engineering Systems Division</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2016-11-14T19:05:39Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2016-11-14T19:05:39Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2014</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2014</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/105297</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">962306052</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, 2014.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">DVD-ROM contains supplemental models: four .mdl files and two .vdf files.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Cataloged from PDF version of thesis.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (pages 63-64).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The United States Department of Defense has been plagued with failing programs that are over budget, behind schedule, and exhibit poor performance during testing. Once a program has cost, schedule, or capability issues, follow-on development efforts adopt the underlying issues only to reinforce poor performance. To address these issues that lead to firefighting, one option is to use an Agile software development process to introduce capabilities earlier in the development process for effective testing. Two System Dynamics models compare Agile with the traditional Waterfall development approach to determine: if Agile development reduces the conflict between cost, schedule, and capability constraints; if Agile development reduces firefighting; and will Agile development impact other development tasks. Based on the simulation of each model, Agile did improve the dynamics of parallel development cycles by maximizing the productivity of the entire development team. Under the same System and Software Engineering team size and development release schedule, Agile development increases the quantity of requirements introduced within a development cycle. However, Agile development emphasized less on maturing new technologies leading to considerably less innovative builds. Thesis Supervisor:</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Erik Roberto Garcia.</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">64 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="relation" qualifier="requires" lang="en_US">System requirements: Windows and DVD-ROM drive.</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en_US">M.I.T. theses are protected by copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about 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 Systems Division.</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">Resource dependencies in parallel development of military systems : a comparison of waterfall and agile development methodologies</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="9592e87b-63c2-47ef-9ec2-8441a316245b">
	&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>Resource dependencies in parallel development of military systems : a comparison of waterfall and agile development methodologies&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2014&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Garcia, Erik Roberto&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 Systems Division.&lt;/Keyword>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>The United States Department of Defense has been plagued with failing programs that are over budget, behind schedule, and exhibit poor performance during testing. Once a program has cost, schedule, or capability issues, follow-on development efforts adopt the underlying issues only to reinforce poor performance. To address these issues that lead to firefighting, one option is to use an Agile software development process to introduce capabilities earlier in the development process for effective testing. Two System Dynamics models compare Agile with the traditional Waterfall development approach to determine: if Agile development reduces the conflict between cost, schedule, and capability constraints; if Agile development reduces firefighting; and will Agile development impact other development tasks. Based on the simulation of each model, Agile did improve the dynamics of parallel development cycles by maximizing the productivity of the entire development team. Under the same System and Software Engineering team size and development release schedule, Agile development increases the quantity of requirements introduced within a development cycle. However, Agile development emphasized less on maturing new technologies leading to considerably less innovative builds. Thesis Supervisor:&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>