As the name implies, AMDD is the agile version of Model Driven Development (MDD). MDD is an approach to software development where extensive models are created before source code is written. A primary example of MDD is the Object Management Group (OMG)’s Model Driven Architecture (MDA) standard. With MDD a serial approach to development is often taken, MDD is quite popular with traditionalists, although as the RUP/EUP shows it is possible to take an iterative approach with MDD. The difference with AMDD is that instead of creating extensive models before writing source code you instead create agile models which are just barely good enough that drive your overall development efforts. AMDD is a critical strategy for scaling agile software development beyond the small, co-located team approach that we saw during the first stage of agile adoption.
W. Royce. ICSE '87: Proceedings of the 9th international conference on Software Engineering, page 328--338. Los Alamitos, CA, USA, IEEE Computer Society Press, (1987)
K. Sousa, H. Mendonça, and J. Vanderdonckt. Task Models and Diagrams for User Interface Design, volume 5963 of Lecture Notes in Computer Science, Springer Berlin Heidelberg, (2010)
K. Sousa, H. Mendonça, and J. Vanderdonckt. Task Models and Diagrams for User Interface Design, volume 4849 of Lecture Notes in Computer Science, Springer Berlin Heidelberg, (2007)
M. Veit, and S. Herrmann. AOSD '03: Proceedings of the 2nd international conference on Aspect-oriented software development, page 140--149. New York, NY, USA, ACM, (2003)
J. Zhang, Y. Lin, and J. Gray. chapter Generic and Domain-Specific Model Refactoring Using a Model Transformation
Engine, page 199-217. Springer Berlin Heidelberg, (2005)