A key feature of agile software development is its prioritisa-tion of responding to changing requirements over planning ahead. If an agile development team spends too much time planning and designing architecture then responding to change will be extremely costly, while not doing enough architectural design puts the project at risk of failure. Striking the balance depends heavily on the context of the system being built, the environment and the development teams. This Grounded Theory research into how much architecture agile teams design up-front has identified system complexity as an important factor in determining how much planning a team does up-front, while system size, although related to complexity, has a much less direct impact. Furthermore, when determining how much design to do up-front, value to the customer can be a more important factor than overall development cost. Understanding these factors can help agile teams to determine how much up-front planning is appropriate for the systems they develop.
CITATION STYLE
Waterman, M., Noble, J., & Allan, G. (2013). The effect of complexity and value on architecture planning in agile software development. In Lecture Notes in Business Information Processing (Vol. 149, pp. 238–252). Springer Verlag. https://doi.org/10.1007/978-3-642-38314-4_17
Mendeley helps you to discover research relevant for your work.