In the Autumn of 2000 when work first began on what was to become the Agile Modeling (AM) methodology we focused on defining a collection of values , principles , and practices for modeling and documentation on software development projects. The principles and practices were fairly granular, describing what you do in during the acts of modeling and documentation. Although valuable, many people found these principles and practices to be too difficult to understand, because of their granularity but also because of their vagueness. Then in 2003 the Agile Model Driven Development (AMDD) lifecycle began to coalesce to describe when modeling occurs on projects (or programmes as the case may be), such as architectural envisioning and requirements envisioning at the beginning of a project or model storming on a just-in-time (JIT) basis throughout the project. This in turn revealed higher level AMDD " best practices ", overviewed in the pattern language map of Figure 1 .