2026-09-18T21:57:50Zhttps://dspace.mit.edu/server/oai/requestoai:dspace.mit.edu:1721.1/795132022-01-13T07:54:46Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023
Stuart Madnick.
Glaiel, Firas (Firas S.)
Massachusetts Institute of Technology. Engineering Systems Division.
Massachusetts Institute of Technology. Engineering Systems Division
2013-07-10T14:50:52Z
2013-07-10T14:50:52Z
2012
2012
http://hdl.handle.net/1721.1/79513
849745349
Thesis (S.M.)--Massachusetts Institute of Technology, Engineering Systems Division, 2012.
Cataloged from PDF version of thesis.
Includes bibliographical references (p. 122-123).
Large-scale software engineering organizations have traditionally used plan-driven, heavyweight, waterfall-style approaches for the planning, execution, and monitoring of software development efforts. This approach often results in relatively long development schedules that are susceptible to failure, especially in a rapidly changing environment: Schedule pressure, defects and requirements changes, can drive endless redesign, delay the project, and incur extra cost. Many in the commercial software world have dealt with these pressures by adopting Agile Software Development, an approach designed to be flexible and responsive to high-change environments. Software development teams that are said to employ "Agile development" in effect practice a variety of "agile methods". These practices are advertised to reduce coordination costs, to focus teams, and to produce stable product iterations that can be released incrementally. Agile software development has become a de-facto approach to the engineering of software systems in the commercial world, and is now entering the aerospace and defense sectors. The APD model developed in this research aids in the understanding of the impact that alternative combinations of Agile practices, combined with different management policies, have on project performance, compared to a waterfall approach. This research culminates in a formulation of insights and recommendations for how to integrate Agile practices into a large-scale software engineering organization.
by Firas Glaiel.
S.M.
136 p.
eng
Massachusetts Institute of Technology
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.
http://dspace.mit.edu/handle/1721.1/7582
Engineering Systems Division.
Agile project dynamics : a strategic project management approach to the study of large-scale software development using system dynamics
Strategic project management approach to the study of large-scale software development using system dynamics
Thesis
application/pdf
false
Publication
unknown
unknown
<Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="2ae40e15-3eb1-4c0c-a0aa-11f1b3dc2989">
<Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843</Type>
<Language>eng</Language>
<Title>Agile project dynamics : a strategic project management approach to the study of large-scale software development using system dynamics</Title>
<Subtitle>Strategic project management approach to the study of large-scale software development using system dynamics</Subtitle>
<PublishedIn>
<Publication>
</Publication>
</PublishedIn>
<PublicationDate>2012</PublicationDate>
<Authors>
<Author>
<DisplayName>Glaiel, Firas (Firas S.)</DisplayName>
<Affiliation>
<OrgUnit>
</OrgUnit>
</Affiliation>
</Author>
</Authors>
<Editors>
</Editors>
<Publishers>
<Publisher>
<DisplayName>Massachusetts Institute of Technology</DisplayName>
<OrgUnit />
</Publisher>
</Publishers>
<License>http://dspace.mit.edu/handle/1721.1/7582</License>
<Keyword>Engineering Systems Division.</Keyword>
<Abstract>Large-scale software engineering organizations have traditionally used plan-driven, heavyweight, waterfall-style approaches for the planning, execution, and monitoring of software development efforts. This approach often results in relatively long development schedules that are susceptible to failure, especially in a rapidly changing environment: Schedule pressure, defects and requirements changes, can drive endless redesign, delay the project, and incur extra cost. Many in the commercial software world have dealt with these pressures by adopting Agile Software Development, an approach designed to be flexible and responsive to high-change environments. Software development teams that are said to employ "Agile development" in effect practice a variety of "agile methods". These practices are advertised to reduce coordination costs, to focus teams, and to produce stable product iterations that can be released incrementally. Agile software development has become a de-facto approach to the engineering of software systems in the commercial world, and is now entering the aerospace and defense sectors. The APD model developed in this research aids in the understanding of the impact that alternative combinations of Agile practices, combined with different management policies, have on project performance, compared to a waterfall approach. This research culminates in a formulation of insights and recommendations for how to integrate Agile practices into a large-scale software engineering organization.</Abstract>
<Access xmlns="http://purl.org/coar/access_right"
>
</Access>
</Publication>