Agile Models Distilled: Potential Artifacts for Agile Modeling

NOTE: This page is currently being refactored (May 2021). Our apologies for any clunkiness during this period


To be effective, the principle Multiple Models tells us that agile modelers should know a wide variety of modeling techniques so that they have the skills and knowledge to apply the right artifact(s) for the situation at hand. Unfortunately this is easier said than done. This page links to summary descriptions of a wide variety of modeling artifacts. Each page describes the artifact, provides an example or two, and provides links to suggested resources.

Note that we use the term model to be inclusive of maps, roadmaps, canvases, sketches, plans, and other types of artifacts that can be used to explore and communicate ideas.

We have organized this page by categories of model application, we hope to help make it easier to find potential modeling techniques. But this categorization strategy isn't exact, as you can see some model types appear in several categories and you may disagree with several of our categorizations. The important thing is to focus on how to apply given modeling technique rather than the categorication of it. The categories that we've chosen are:

Business Exploration Models

There are several models that you may consider when exploring the business environment, including the potential opportunity, for an endeavor. There tends to be overlap with discovery models. Potential business exploration models include:

Discovery Models

We use the term discovery to refer to activities surrounding the identification and exploration of potential customers, including their potential desires, needs, environments, and preferences. There is potential overlap with business exploration models, requirements-analysis models and user experience (UX) models. Potential discovery models include:

Requirements-Analysis Models

Requirements-analysis models are typically used to explore and capture the perceived desires/needs of stakeholders. There tends to be overlap with discovery models, process/flow models, and user experience (UX) models. Potential requirements-analysis models include:

Architectural Models

Description TBD. Potential architectural models include:

Process/Flow Models

Description TBD. Potential process/flow models include:

Technical Design Models

Description TBD. Potential technical design models include:

User Experience (UX) Design Models

Description TBD. Potential UX design models include:

Validation Models

Description TBD. Potential validation models include: