Document continuously. Documentation is made throughout the life-cycle, in parallel to the creation of the rest of the solution.
Document late. Documentation is made as late as possible, avoiding speculative ideas that are likely to change in favor of stable information.
Executable specifications. Requirements are specified in the form of executable "customer tests", instead of non-executable "static" documentation.
Single-source information. Information, is stored in one place and one place only, to prevent questions about what the "correct" version / information is.
Modeling
Active stakeholder participation. Stakeholders of the solution/software being modeled should be actively involved with doing so. This is an extension of the on-site customer practice from Extreme Programming.
Inclusive tools. Prefer modelling tools, such as whiteboards and paper, that are easy to work with.
Iteration modeling. When a requirement/work item has not been sufficiently explored in detail via look-ahead modeling they team may choose to do that exploration during their iteration/sprint planning session. The need to do this is generally seen as a symptom that the team is not doing sufficient look-ahead modeling.
Just barely good enough. All artifact, including models and documents, should be just sufficient for the task at hand. JBGE is contextual in nature, in the case of the model it is determined by a combination of the complexity of whatever the model describes and the skills of the audience for that model.
Look-ahead modeling. An agile team will look down their backlog one or more iterations/sprints ahead to ensure that a requirement/work item is ready to be worked on. Also called "backlog grooming" or "backlog refinement" in Scrum.
Model storming. A short, often impromptu, agile modeling session. Model storming sessions are held to explore the details of a requirement or aspect of your design.
Multiple models. Agile modelers should know how to create a range of model types so as to apply the best model for the situation at hand.
Prioritized requirements. Requirements should be worked on in priority order.
Requirements envisioning. The team performs light-weight, high-level modeling that is JBGE at the beginning of a software project to explore the stakeholder requirements.
Limitations
There is significant dependence on personal communication and customer collaboration. Agile modeling disciplines can be difficult to apply :
On large teams without adequate tooling support
Where team members are unable to share and collaborate on models
