<?xml version="1.0" encoding="ISO-8859-1"?><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<front>
<journal-meta>
<journal-id>0123-2126</journal-id>
<journal-title><![CDATA[Ingeniería y Universidad]]></journal-title>
<abbrev-journal-title><![CDATA[Ing. Univ.]]></abbrev-journal-title>
<issn>0123-2126</issn>
<publisher>
<publisher-name><![CDATA[Pontificia Universidad Javeriana]]></publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id>S0123-21262018000100033</article-id>
<article-id pub-id-type="doi">10.11144/javeriana.iyu22-1.aaaa</article-id>
<title-group>
<article-title xml:lang="en"><![CDATA[Agile Architecture in Action (AGATA)]]></article-title>
<article-title xml:lang="es"><![CDATA[Arquitectura ágil en acción (AGATA)]]></article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname><![CDATA[Muñoz-Sanabria]]></surname>
<given-names><![CDATA[Luis Freddy]]></given-names>
</name>
<xref ref-type="aff" rid="Aff"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname><![CDATA[Hurtado-Alegría]]></surname>
<given-names><![CDATA[Julio Ariel]]></given-names>
</name>
<xref ref-type="aff" rid="Aff"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname><![CDATA[Álvarez-Rodríguez]]></surname>
<given-names><![CDATA[Francisco Javier]]></given-names>
</name>
<xref ref-type="aff" rid="Aff"/>
</contrib>
</contrib-group>
<aff id="Af3">
<institution><![CDATA[,Fundación Universitaria de Popayán  ]]></institution>
<addr-line><![CDATA[Popayán ]]></addr-line>
<country>Colombia</country>
</aff>
<aff id="Af4">
<institution><![CDATA[,Universidad del Cauca  ]]></institution>
<addr-line><![CDATA[Popayán ]]></addr-line>
<country>Colombia</country>
</aff>
<aff id="Af5">
<institution><![CDATA[,Universidad Autónoma de Aguascalientes  ]]></institution>
<addr-line><![CDATA[Aguascalientes ]]></addr-line>
<country>Mexico</country>
</aff>
<pub-date pub-type="pub">
<day>00</day>
<month>06</month>
<year>2018</year>
</pub-date>
<pub-date pub-type="epub">
<day>00</day>
<month>06</month>
<year>2018</year>
</pub-date>
<volume>22</volume>
<numero>1</numero>
<fpage>33</fpage>
<lpage>51</lpage>
<copyright-statement/>
<copyright-year/>
<self-uri xlink:href="http://www.scielo.org.co/scielo.php?script=sci_arttext&amp;pid=S0123-21262018000100033&amp;lng=en&amp;nrm=iso"></self-uri><self-uri xlink:href="http://www.scielo.org.co/scielo.php?script=sci_abstract&amp;pid=S0123-21262018000100033&amp;lng=en&amp;nrm=iso"></self-uri><self-uri xlink:href="http://www.scielo.org.co/scielo.php?script=sci_pdf&amp;pid=S0123-21262018000100033&amp;lng=en&amp;nrm=iso"></self-uri><abstract abstract-type="short" xml:lang="en"><p><![CDATA[Abstract  Introduction:  This work proposes Agile Architecture in Action (AGATA), a software process framework that scales agile methods to larger teams.  Methodology:  following a human interface model, several Extreme Programming (XP) development teams work together around a central team that takes advantage of the ability of architectural methods to define the solution at the architectural level, improving communication and maintaining agile parameters.  Results:  AGATA was applied in a development project, involving software engineers and software engineering senior students that participated in a graduate practical course. In this case study we measured communication based in the architecture and face-to-face channels, taking into account the degree of distortion and quality of the channels. The main results show that communication levels in the whole team are reasonable and that the channels proposed by AGATA maintain agile parameters as to intergroup relationship and client deliveries. There are reports indicating scaling problems as teams grow; particularly, communication worsens.  Conclusions:  It is necessary to propose clear channels of communication. AGATA practices managed to maintain agile elements with a large team.]]></p></abstract>
<abstract abstract-type="short" xml:lang="es"><p><![CDATA[Resumen   Introducción: Este trabajo propone Agile Architecture in Action (AGATA), un marco de proceso de software que escala métodos ágiles a equipos más grandes.  Metodología:  Siguiendo un modelo de interfaz humano, varios equipos de desarrollo de Extreme Programming (XP) trabajan juntos alrededor de un equipo central que aprovecha la capacidad de métodos arquitectónicos para definir la solución a nivel arquitectónico, mejorando la comunicación y manteniendo los parámetros ágiles.  Resultados:  AGATA se aplicó en un proyecto de desarrollo, en el que participaron ingenieros de software y estudiantes de último año de ingeniería de software, que participaron en un curso práctico de posgrado. En este caso de estudio se midieron los canales de comunicación la arquitectura y el cara a cara, teniendo en cuenta el grado de distorsión y la calidad de los canales. Los principales resultados muestran que los niveles de comunicación en todo el equipo son razonables y que los canales propuestos por AGATA mantienen parámetros ágiles en cuanto a relaciones intergrupales y entregas de clientes. Hay informes que indican problemas de escala, a medida que los equipos crecen; en particular, la comunicación.  Conclusiones:  es necesario proponer canales claros de comunicación; las prácticas utilizando AGATA lograron mantener los elementos ágiles con un equipo grande.]]></p></abstract>
<kwd-group>
<kwd lng="en"><![CDATA[Software architecture]]></kwd>
<kwd lng="en"><![CDATA[scaling]]></kwd>
<kwd lng="en"><![CDATA[agile methods]]></kwd>
<kwd lng="en"><![CDATA[software process]]></kwd>
<kwd lng="es"><![CDATA[Arquitectura de software]]></kwd>
<kwd lng="es"><![CDATA[escala]]></kwd>
<kwd lng="es"><![CDATA[métodos ágiles]]></kwd>
<kwd lng="es"><![CDATA[procesos de software]]></kwd>
</kwd-group>
</article-meta>
</front><back>
<ref-list>
<ref id="B1">
<label>[1[</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Beck]]></surname>
<given-names><![CDATA[K.]]></given-names>
</name>
<name>
<surname><![CDATA[Andres]]></surname>
<given-names><![CDATA[C.]]></given-names>
</name>
</person-group>
<source><![CDATA[Extreme Programming explained: embrace change]]></source>
<year>2004</year>
<edition>1st</edition>
<publisher-loc><![CDATA[New Jersey, NJ, US ]]></publisher-loc>
<publisher-name><![CDATA[Pearson Education]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B2">
<label>[2[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Nord]]></surname>
<given-names><![CDATA[R. L.]]></given-names>
</name>
<name>
<surname><![CDATA[Tomayko]]></surname>
<given-names><![CDATA[J. E]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[Software Architecture Centric Methods and Agile Development]]></article-title>
<source><![CDATA[IEEE Software]]></source>
<year>2006</year>
<volume>23</volume>
<numero>2</numero>
<issue>2</issue>
<page-range>47-53</page-range></nlm-citation>
</ref>
<ref id="B3">
<label>[3[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Reifer]]></surname>
<given-names><![CDATA[D. J.]]></given-names>
</name>
<name>
<surname><![CDATA[Maurer]]></surname>
<given-names><![CDATA[F.]]></given-names>
</name>
<name>
<surname><![CDATA[Erdogmus]]></surname>
<given-names><![CDATA[H.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[Scaling Agile Methods]]></article-title>
<source><![CDATA[IEEE Software]]></source>
<year>2003</year>
<volume>20</volume>
<numero>4</numero>
<issue>4</issue>
<page-range>12-4</page-range></nlm-citation>
</ref>
<ref id="B4">
<label>[4[</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Beck]]></surname>
<given-names><![CDATA[K.]]></given-names>
</name>
<name>
<surname><![CDATA[Fowler]]></surname>
<given-names><![CDATA[M.]]></given-names>
</name>
</person-group>
<source><![CDATA[Planning Extreme Programming]]></source>
<year>2000</year>
<edition>1st</edition>
<publisher-loc><![CDATA[Boston, MA, US ]]></publisher-loc>
<publisher-name><![CDATA[Addison- Wesley, Longman Publishing Co]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B5">
<label>[5[</label><nlm-citation citation-type="">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Ambler]]></surname>
<given-names><![CDATA[S. W]]></given-names>
</name>
</person-group>
<source><![CDATA[The Agile Scaling Model (ASM): adapting agile methods for complex environments]]></source>
<year>2009</year>
</nlm-citation>
</ref>
<ref id="B6">
<label>[6[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[MacKellar]]></surname>
<given-names><![CDATA[B.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[A case study of group communication patterns in a large project software engineering course,]]></article-title>
<source><![CDATA[Software Eng. Educ. Training (CSEE&amp;T)]]></source>
<year>2012</year>
<publisher-loc><![CDATA[Nanjing, Jiangsu, China ]]></publisher-loc>
</nlm-citation>
</ref>
<ref id="B7">
<label>[7[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Rodríguez]]></surname>
<given-names><![CDATA[D.]]></given-names>
</name>
<name>
<surname><![CDATA[Sicilia]]></surname>
<given-names><![CDATA[M. A.]]></given-names>
</name>
<name>
<surname><![CDATA[García]]></surname>
<given-names><![CDATA[E.]]></given-names>
</name>
<name>
<surname><![CDATA[Harrison]]></surname>
<given-names><![CDATA[R.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[Empirical findings on team size and productivity in software development]]></article-title>
<source><![CDATA[J. Syst. Software]]></source>
<year>2012</year>
<volume>85</volume>
<numero>3</numero>
<issue>3</issue>
<page-range>562-70</page-range></nlm-citation>
</ref>
<ref id="B8">
<label>[8[</label><nlm-citation citation-type="">
<source><![CDATA[Extreme Programming: A gentle introduction]]></source>
<year></year>
</nlm-citation>
</ref>
<ref id="B9">
<label>[9[</label><nlm-citation citation-type="">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Kent]]></surname>
<given-names><![CDATA[Beck]]></given-names>
</name>
<name>
<surname><![CDATA[Charles]]></surname>
<given-names><![CDATA[Andres]]></given-names>
</name>
</person-group>
<source><![CDATA[Extreme programming explained: embrace change]]></source>
<year>2012</year>
<page-range>224</page-range><publisher-loc><![CDATA[Addison-Wesley ]]></publisher-loc>
</nlm-citation>
</ref>
<ref id="B10">
<label>[10[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Pendharkar]]></surname>
<given-names><![CDATA[P. C.]]></given-names>
</name>
<name>
<surname><![CDATA[Rodger]]></surname>
<given-names><![CDATA[J. A.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[The relationship between software development team size and software development cost]]></article-title>
<source><![CDATA[Commun. ACM]]></source>
<year>2009</year>
<volume>52</volume>
<numero>1,</numero>
<issue>1,</issue>
<page-range>141-4</page-range></nlm-citation>
</ref>
<ref id="B11">
<label>[11[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Yang]]></surname>
<given-names><![CDATA[C.]]></given-names>
</name>
<name>
<surname><![CDATA[Liang]]></surname>
<given-names><![CDATA[P]]></given-names>
</name>
<name>
<surname><![CDATA[Avgeriou]]></surname>
<given-names><![CDATA[P]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[A systematic mapping study on the combination of software architecture and agile development]]></article-title>
<source><![CDATA[J Syst Software]]></source>
<year>2016</year>
<volume>111</volume>
<page-range>157-84</page-range></nlm-citation>
</ref>
<ref id="B12">
<label>[12[</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Hadar]]></surname>
<given-names><![CDATA[E.]]></given-names>
</name>
<name>
<surname><![CDATA[Silberman]]></surname>
<given-names><![CDATA[G. M.]]></given-names>
</name>
</person-group>
<source><![CDATA[Agile architecture methodology: long term strategy interleaved with short term tactics]]></source>
<year>2008</year>
<conf-name><![CDATA[ OOPSLA Companion &#8216;08 Companion to the 23rd ACM SIGPLAN conf. on Object-oriented programming syst. languages and app]]></conf-name>
<conf-loc>Nashville </conf-loc>
<page-range>641-52</page-range><publisher-loc><![CDATA[TN, US ]]></publisher-loc>
</nlm-citation>
</ref>
<ref id="B13">
<label>[13[</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Erder]]></surname>
<given-names><![CDATA[M.]]></given-names>
</name>
<name>
<surname><![CDATA[Pureur]]></surname>
<given-names><![CDATA[P]]></given-names>
</name>
</person-group>
<source><![CDATA[Continuous architecture: Sustainable architecture in an agile and cloud-centric world]]></source>
<year>2006</year>
<publisher-loc><![CDATA[Walthman, MA, US ]]></publisher-loc>
<publisher-name><![CDATA[Morgan Kauffmann, Elsevier]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B14">
<label>[14[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Kazman]]></surname>
<given-names><![CDATA[R.]]></given-names>
</name>
<name>
<surname><![CDATA[Bass]]></surname>
<given-names><![CDATA[L.]]></given-names>
</name>
<name>
<surname><![CDATA[Klein]]></surname>
<given-names><![CDATA[M.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[The essential components of software architecture design and analysis]]></article-title>
<source><![CDATA[J Syst. Software]]></source>
<year>2006</year>
<volume>79</volume>
<numero>8</numero>
<issue>8</issue>
<page-range>1207-16</page-range></nlm-citation>
</ref>
<ref id="B15">
<label>[15[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Zaychik]]></surname>
<given-names><![CDATA[V]]></given-names>
</name>
<name>
<surname><![CDATA[Regli]]></surname>
<given-names><![CDATA[W C.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[Capturing communication and context in the software project lifecycle]]></article-title>
<source><![CDATA[Res. Eng. Des]]></source>
<year>2003</year>
<volume>14</volume>
<numero>2</numero>
<issue>2</issue>
<page-range>75-88</page-range></nlm-citation>
</ref>
<ref id="B16">
<label>[16[</label><nlm-citation citation-type="">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Marjaie]]></surname>
<given-names><![CDATA[S-A.]]></given-names>
</name>
<name>
<surname><![CDATA[Rathod]]></surname>
<given-names><![CDATA[U.]]></given-names>
</name>
</person-group>
<source><![CDATA[Communication in agile software projects: qualitative analysis using grounded theory in system dynamics]]></source>
<year>2014</year>
</nlm-citation>
</ref>
<ref id="B17">
<label>[17[</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Reinhardt]]></surname>
<given-names><![CDATA[W.]]></given-names>
</name>
</person-group>
<source><![CDATA[Communication is the key-Support durable knowledge sharing in software engineering by microblogging]]></source>
<year></year>
<conf-name><![CDATA[ 1stWorkshop on Software Eng. within Social software Environments (SENSE09)]]></conf-name>
<conf-date>March 3, 2009</conf-date>
<conf-loc>Kaiserslautern, Germany </conf-loc>
</nlm-citation>
</ref>
<ref id="B18">
<label>[18[</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Sanabria]]></surname>
<given-names><![CDATA[L. Muñoz]]></given-names>
</name>
<name>
<surname><![CDATA[Alegría]]></surname>
<given-names><![CDATA[J. Hurtado]]></given-names>
</name>
</person-group>
<source><![CDATA[XA: Una extensión XP para apoyar estudios de arquitectura]]></source>
<year></year>
<conf-name><![CDATA[ XIComputer Congress (CCC)]]></conf-name>
<conf-date>2015</conf-date>
<conf-loc>Colombia </conf-loc>
</nlm-citation>
</ref>
<ref id="B19">
<label>[19[</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Marchesi]]></surname>
<given-names><![CDATA[M.]]></given-names>
</name>
<name>
<surname><![CDATA[Succi]]></surname>
<given-names><![CDATA[G.]]></given-names>
</name>
<name>
<surname><![CDATA[Wells]]></surname>
<given-names><![CDATA[D.]]></given-names>
</name>
<name>
<surname><![CDATA[Williams]]></surname>
<given-names><![CDATA[L.]]></given-names>
</name>
</person-group>
<source><![CDATA[Extreme programming perspectives]]></source>
<year>2002</year>
<page-range>624</page-range><publisher-loc><![CDATA[New Jersey, NJ, US ]]></publisher-loc>
<publisher-name><![CDATA[Pearson Education, Addison Wesley]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B20">
<label>[20[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Pendharkar]]></surname>
<given-names><![CDATA[P]]></given-names>
</name>
<name>
<surname><![CDATA[Rodger]]></surname>
<given-names><![CDATA[J.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[The relationship Between Software Development Team Size and Software Development Cost]]></article-title>
<source><![CDATA[ACM]]></source>
<year>2009</year>
<month>,</month>
<volume>52</volume>
<numero>1</numero>
<issue>1</issue>
<page-range>141-4</page-range></nlm-citation>
</ref>
<ref id="B21">
<label>[21[</label><nlm-citation citation-type="">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Schwaber]]></surname>
<given-names><![CDATA[K.]]></given-names>
</name>
<name>
<surname><![CDATA[Sutherland]]></surname>
<given-names><![CDATA[J.]]></given-names>
</name>
</person-group>
<source><![CDATA[The scrum Guide: The definitive guide to scrum: the rules of the game. Scrum]]></source>
<year>2013</year>
</nlm-citation>
</ref>
<ref id="B22">
<label>[22[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Runeson]]></surname>
<given-names><![CDATA[P]]></given-names>
</name>
<name>
<surname><![CDATA[Höst]]></surname>
<given-names><![CDATA[M.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[Guidelines for conducting and reportingcase study research in software engineering]]></article-title>
<source><![CDATA[Empirical Software]]></source>
<year>2009</year>
<volume>14</volume>
<numero>2</numero>
<issue>2</issue>
<page-range>131-64</page-range></nlm-citation>
</ref>
<ref id="B23">
<label>[23[</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Jensen]]></surname>
<given-names><![CDATA[R. N.]]></given-names>
</name>
<name>
<surname><![CDATA[Moller]]></surname>
<given-names><![CDATA[T.]]></given-names>
</name>
<name>
<surname><![CDATA[Tjornehoj]]></surname>
<given-names><![CDATA[G.]]></given-names>
</name>
</person-group>
<source><![CDATA[Architecture and design in eXtreme programming: introducing &#8216;developer stories&#8217;]]></source>
<year>2006</year>
<conf-name><![CDATA[ Int. Conf. on Extreme Progr. Agile Process. Software Eng. XP 2006. Lecture Notes in Comput. Sci, 4044]]></conf-name>
<conf-loc>Berlin, Heidelberg </conf-loc>
<page-range>133-42</page-range></nlm-citation>
</ref>
<ref id="B24">
<label>[24[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Kuppuswami]]></surname>
<given-names><![CDATA[S.]]></given-names>
</name>
<name>
<surname><![CDATA[Vivekanandan]]></surname>
<given-names><![CDATA[K.]]></given-names>
</name>
<name>
<surname><![CDATA[Ramaswamy]]></surname>
<given-names><![CDATA[P.]]></given-names>
</name>
<name>
<surname><![CDATA[Rodrigues]]></surname>
<given-names><![CDATA[P.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[The effects of individual XP practices on software development effort]]></article-title>
<source><![CDATA[Newsletter ACM SIGSOFT Software Eng. Notes]]></source>
<year>2003</year>
<volume>28</volume>
<numero>6</numero>
<issue>6</issue>
<page-range>6</page-range></nlm-citation>
</ref>
<ref id="B25">
<label>[25[</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Tobón]]></surname>
<given-names><![CDATA[L. M. Echeverry]]></given-names>
</name>
<name>
<surname><![CDATA[Delgado Carmona]]></surname>
<given-names><![CDATA[L. E]]></given-names>
</name>
</person-group>
<source><![CDATA[Caso práctico de la metodología ágil XP al desarrollo de software]]></source>
<year>2007</year>
<publisher-loc><![CDATA[Colombia ]]></publisher-loc>
<publisher-name><![CDATA[Universidad Tecnológica de Pereira]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B26">
<label>[26[</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Martin]]></surname>
<given-names><![CDATA[A.]]></given-names>
</name>
<name>
<surname><![CDATA[Noble]]></surname>
<given-names><![CDATA[J.]]></given-names>
</name>
<name>
<surname><![CDATA[Biddle]]></surname>
<given-names><![CDATA[R.]]></given-names>
</name>
</person-group>
<source><![CDATA[&#8220;Programmers are from Mars, customers are from Venus: A practical guide for customers on XP Projects,&#8221;]]></source>
<year></year>
<conf-name><![CDATA[ 06Proc. 2006 conf. Pattern languages of programs]]></conf-name>
<conf-date>Oct. 2006</conf-date>
<conf-loc>Portland, Oregon, US </conf-loc>
</nlm-citation>
</ref>
<ref id="B27">
<label>[27[</label><nlm-citation citation-type="">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Wojcik]]></surname>
<given-names><![CDATA[R.]]></given-names>
</name>
<name>
<surname><![CDATA[Bachmann]]></surname>
<given-names><![CDATA[F.]]></given-names>
</name>
<name>
<surname><![CDATA[Bass]]></surname>
<given-names><![CDATA[L.]]></given-names>
</name>
</person-group>
<source><![CDATA[Attribute-Driven Design (ADD) Version 2. Software Architecture Technology Initiative]]></source>
<year>2006</year>
</nlm-citation>
</ref>
<ref id="B28">
<label>[28[</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Barbacci]]></surname>
<given-names><![CDATA[M. R.]]></given-names>
</name>
</person-group>
<source><![CDATA[Quality Attribute Workshops QAW]]></source>
<year>2002</year>
<month>,</month>
<edition>3rd</edition>
<publisher-name><![CDATA[Architecture Tradeoff Analysis Initiative]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B29">
<label>[29[</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Abrahamsson]]></surname>
<given-names><![CDATA[P]]></given-names>
</name>
<name>
<surname><![CDATA[Salo]]></surname>
<given-names><![CDATA[O.]]></given-names>
</name>
<name>
<surname><![CDATA[Ronkainen]]></surname>
<given-names><![CDATA[J.]]></given-names>
</name>
<name>
<surname><![CDATA[Warsta]]></surname>
<given-names><![CDATA[J.]]></given-names>
</name>
</person-group>
<source><![CDATA[Agile software development methods: Review and analysis]]></source>
<year>2002</year>
<conf-name><![CDATA[ VTT Electronics, Oulu, Finland, ESPO]]></conf-name>
<conf-date>2002</conf-date>
<conf-loc> </conf-loc>
</nlm-citation>
</ref>
<ref id="B30">
<label>[30[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Reifer]]></surname>
<given-names><![CDATA[D. J.]]></given-names>
</name>
<name>
<surname><![CDATA[Maurer]]></surname>
<given-names><![CDATA[F.]]></given-names>
</name>
<name>
<surname><![CDATA[Erdogmus]]></surname>
<given-names><![CDATA[H.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[Scaling agile methods]]></article-title>
<source><![CDATA[IEEE Software]]></source>
<year>2003</year>
<volume>20</volume>
<numero>4</numero>
<issue>4</issue>
<page-range>12-4</page-range></nlm-citation>
</ref>
<ref id="B31">
<label>[31[</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Sillitti]]></surname>
<given-names><![CDATA[A.]]></given-names>
</name>
<name>
<surname><![CDATA[Succi]]></surname>
<given-names><![CDATA[G.]]></given-names>
</name>
<name>
<surname><![CDATA[Aurum]]></surname>
<given-names><![CDATA[A.]]></given-names>
</name>
<name>
<surname><![CDATA[Wohlin]]></surname>
<given-names><![CDATA[C.]]></given-names>
</name>
</person-group>
<source><![CDATA[Requirements engineering for agile methods,&#8221; in Engineering and Managing Software Requirements]]></source>
<year>2005</year>
<page-range>309-26</page-range><publisher-loc><![CDATA[Berlin, Heidelberg ]]></publisher-loc>
<publisher-name><![CDATA[Springer]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B32">
<label>[32[</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Gittins]]></surname>
<given-names><![CDATA[R.]]></given-names>
</name>
<name>
<surname><![CDATA[Hope]]></surname>
<given-names><![CDATA[S.]]></given-names>
</name>
</person-group>
<source><![CDATA[A study of Human Solutions in Extreme Programming]]></source>
<year>2001</year>
<conf-name><![CDATA[ Proc. PPIG13]]></conf-name>
<conf-date>Apr. 2001</conf-date>
<conf-loc>Bournemouth, UK </conf-loc>
<page-range>41-51</page-range></nlm-citation>
</ref>
<ref id="B33">
<label>[33[</label><nlm-citation citation-type="">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Beck]]></surname>
<given-names><![CDATA[K.]]></given-names>
</name>
</person-group>
<source><![CDATA[Manifesto for agile software development]]></source>
<year>2001</year>
</nlm-citation>
</ref>
<ref id="B34">
<label>[34[</label><nlm-citation citation-type="">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Biolchini]]></surname>
<given-names><![CDATA[J.]]></given-names>
</name>
<name>
<surname><![CDATA[Mian]]></surname>
<given-names><![CDATA[P Gomes]]></given-names>
</name>
<name>
<surname><![CDATA[Natali]]></surname>
<given-names><![CDATA[A. C. Cruz]]></given-names>
</name>
<name>
<surname><![CDATA[Travassos]]></surname>
<given-names><![CDATA[G. H.]]></given-names>
</name>
</person-group>
<source><![CDATA[Systematic Review in Software Engineering]]></source>
<year>2005</year>
<month>,</month>
</nlm-citation>
</ref>
<ref id="B35">
<label>[35[</label><nlm-citation citation-type="">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Kitchenham]]></surname>
<given-names><![CDATA[B.]]></given-names>
</name>
</person-group>
<source><![CDATA[Procedures for performing systematic reviews]]></source>
<year>2004</year>
</nlm-citation>
</ref>
<ref id="B36">
<label>[36[</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Layman]]></surname>
<given-names><![CDATA[L.]]></given-names>
</name>
<name>
<surname><![CDATA[Williams]]></surname>
<given-names><![CDATA[L.]]></given-names>
</name>
<name>
<surname><![CDATA[Cunningham]]></surname>
<given-names><![CDATA[L.]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[Exploring extreme programming in context: An industrial case study]]></article-title>
<source><![CDATA[Proc. Agile Develop. Conf]]></source>
<year>2004</year>
<page-range>32-41</page-range><publisher-loc><![CDATA[Salt Lake City, UT, US ]]></publisher-loc>
</nlm-citation>
</ref>
</ref-list>
</back>
</article>
