Agile modeling

Agile modeling (AM) is a methodology for modeling and documenting software systems based on best practices. It is a collection of values and principles, that can be applied on an (agile) software development project. This methodology is more flexible than traditional modeling methods, making it a better fit in a fast changing environment. It is part of the agile software development tool kit.

Agile modeling is a supplement to other agile development methodologies such as Scrum, extreme programming (XP), and Rational Unified Process (RUP). It is explicitly included as part of the disciplined agile delivery (DAD) framework. As per 2011 stats, agile modeling accounted for 1% of all agile software development.

Agile modeling is one form of Agile model-driven engineering (Agile MDE), which has been adopted in several application areas such as web application development, finance, and automotive systems https://kclpure.kcl.ac.uk/portal/en/publications/the-integration-of-agile-development-and-model-driven-development-a-systematic-literature-review(af6a79a4-01a5-4cfd-a8a4-36d11890fc74).html

Core practices

There are several core practices:

Documentation

# 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 (models, documentation, software), 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.
# Architecture envisioning. The team performs light-weight, high-level modeling that is just barely good enough (JBGE) at the beginning of a software project so as to explore the architecture strategy that the team believes will work.
# Inclusive tools. Prefer modelling tools, such as whiteboards and paper, that are easy to work with (they're inclusive).
# Iteration modeling. When a requirement/work item has not been sufficiently explored in detail via look-ahead modeling the 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 (JBGE). 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 (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 {{Citation needed, date=October 2016:
* 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 software development