Agile Architecture Modeling

Same techniques as architecture modeling before, agile modeling puts emphasis on just enough modeling. The purposes are

Improved productivity: Some of the critical technical issues can be potentially avoided and therefore our software increases its software productivity.
Reduced technical risk: What we model doesn't mean what we have to build it. We should not overbuild our system. (This point is highly related to the above)
Improved communication: Our software team understand better what we think we are going to build and how we think that we will build it
Scaling agile software development. Software architecture provides the technical direction required by sub-teams to define and guide their efforts within the overall project.

For more information, please refer to Agile Best Practice: Initial High-Level Architectural Modeling