<?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-19T00:42:36Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/58525" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/58525</identifier><datestamp>2022-01-13T07:54:46Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>com_1721.1_80738</setSpec><setSpec>com_1721.1_1773</setSpec><setSpec>col_1721.1_131023</setSpec><setSpec>col_1721.1_80739</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">Ricardo Valerdi.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Tibazarwa, Augustine</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">2010-09-13T14:09:13Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2010-09-13T14:09:13Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2009</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2009</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/58525</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">630142279</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2009.</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 (p. 112-115).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Process automation vendors must consider agility as a basis to gain a competitive edge in innovation. Process Automation systems can impact the operating cost of manufacturing equipment, the safe control of large quantities of energy and the safety of dangerous substances used during manufacturing. The manufacturing segment expects greater automation of larger processes, increased capability of process automation systems, and higher quality of those systems. At the same time, business requirements for process automation vendors demand shorter time to market, and greater market return for each dollar invested in product development. Therefore, process automation vendors must determine how to preserve discipline in development processes while adopting process agility necessary to meet dynamic business conditions. Interviews with 9 leaders from 6 companies (2 manufacturers, 2 process automation vendors and 2 automation consulting firms), survey feedback from development personnel and research of literature on state-of-the-art and state-of-the-practice, yielded over 90 findings and observations on process automation business needs, development of automation offerings, and on suitability of agile practices to process automation product development. Agile methods may require changes to manufacturer work processes, but would enable an automation vendor to unlock more of the manufacturer's production value.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">(cont.) Disciplined adoption of agile methods is crucial for agility to take hold throughout an automation vendor's organization, and to meet the concerns of process automation stakeholders. Rather than dismiss the suitability of agile development to process automation, a prescriptive guidance is provided that integrates an opportunistic risk-based assessment of how much agility is appropriate. The four values and twelve principles of the Agile Manifesto are a good basis for 8 additional agile practices for process automation: transitioning to agile, investing in agile capability, managing critical system parameters, engineering system-robustness, balancing project risk, continuous system validation, assuring domain expertise and clarifying ecosystem role.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Augustine Tibazarwa.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">141 p.</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">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">Disciplined agility for process control &amp; automation</dim:field>
   <dim:field mdschema="dc" element="title" qualifier="alternative" lang="en_US">Disciplined agility for process control and automation</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="8e8e5327-1dfd-4f0f-9298-4c4246b244d2">
	&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>Disciplined agility for process control &amp;amp; automation&lt;/Title>
   	&lt;Subtitle>Disciplined agility for process control and automation&lt;/Subtitle>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2009&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Tibazarwa, Augustine&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>Process automation vendors must consider agility as a basis to gain a competitive edge in innovation. Process Automation systems can impact the operating cost of manufacturing equipment, the safe control of large quantities of energy and the safety of dangerous substances used during manufacturing. The manufacturing segment expects greater automation of larger processes, increased capability of process automation systems, and higher quality of those systems. At the same time, business requirements for process automation vendors demand shorter time to market, and greater market return for each dollar invested in product development. Therefore, process automation vendors must determine how to preserve discipline in development processes while adopting process agility necessary to meet dynamic business conditions. Interviews with 9 leaders from 6 companies (2 manufacturers, 2 process automation vendors and 2 automation consulting firms), survey feedback from development personnel and research of literature on state-of-the-art and state-of-the-practice, yielded over 90 findings and observations on process automation business needs, development of automation offerings, and on suitability of agile practices to process automation product development. Agile methods may require changes to manufacturer work processes, but would enable an automation vendor to unlock more of the manufacturer&amp;apos;s production value.&lt;/Abstract>
   	&lt;Abstract>(cont.) Disciplined adoption of agile methods is crucial for agility to take hold throughout an automation vendor&amp;apos;s organization, and to meet the concerns of process automation stakeholders. Rather than dismiss the suitability of agile development to process automation, a prescriptive guidance is provided that integrates an opportunistic risk-based assessment of how much agility is appropriate. The four values and twelve principles of the Agile Manifesto are a good basis for 8 additional agile practices for process automation: transitioning to agile, investing in agile capability, managing critical system parameters, engineering system-robustness, balancing project risk, continuous system validation, assuring domain expertise and clarifying ecosystem role.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>