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 (such as user stories, story maps, data models, Unified Modeling Language (UML) diagrams, and more) 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 (say 30 or more) without adequate tooling support Where team members are unable to share and collaborate on models (which would make agile software development in general difficult) When modeling skills are weak or lacking. See also Story-driven modelling Agile software development Robustness diagram References External links The Agile Modeling Home Page Agile Model Driven Development (AMDD) Agile software development