Agile Modeling Workshop

Foundations

Agile Modeling (AM)

A practice-based approach to modeling and documentation that is lightweight, collaborative, and just enough to support effective communication and design.

Just Barely Good Enough (JBGE)

Creating models and documents only as detailed as needed to serve their purpose, avoiding wasted effort on excess detail.

Model to Communicate vs. to Understand

Some models exist to communicate with others; others are quick sketches to help the modeler think. Purpose determines effort and permanence.

Models Support Software

In Agile Modeling, working software is the primary measure of progress; models serve delivery rather than becoming the goal.

Values

Communication

A core AM value: models are primarily tools to build shared understanding among people.

Simplicity

Favoring the simplest model that conveys the idea, avoiding unnecessary complexity.

Feedback

Sharing models early and often to get quick feedback and correct course.

Courage

Willingness to make decisions, discard models that no longer add value, and change direction.

Humility

Recognizing others have knowledge you lack, so modeling is collaborative rather than solitary.

Principles

Model with a Purpose

Only create a model if it addresses a real need or question; otherwise it is waste.

Multiple Models

Use the right model for the job; different diagrams reveal different aspects of a system.

Embrace Change

Expect requirements and understanding to evolve, and keep models flexible and disposable.

Incremental Modeling

Model in small increments as needed rather than producing large upfront specifications.

Travel Light

Keep only the models and documents worth maintaining, since every artifact has a carrying cost.

Techniques

Model Storming

Quick, just-in-time modeling sessions — often at a whiteboard — to work through a specific issue collaboratively.

Whiteboard Sketching

Informal sketches to explore and communicate ideas rapidly without heavyweight tools.

Inclusive Modeling

Using simple, accessible tools and notations so all stakeholders can participate in modeling.

CRC Cards

Class-Responsibility-Collaborator cards used to explore object designs collaboratively and cheaply.

Domain Modeling

Sketching the key concepts and relationships of the problem domain to build shared understanding.

Just-in-Time Modeling

Modeling right before implementation when knowledge is greatest, not far in advance.

Practices

Active Stakeholder Participation

Involving stakeholders directly in modeling so requirements and designs reflect real needs.

Prove It with Code

Validating models by implementing and testing them, letting working software confirm the design.

Single Source of Information

Storing each piece of information once to avoid duplication and inconsistency.

Update Only When It Hurts

Revising a model only when out-of-date information causes real problems, not for its own sake.

Applying It

Balancing Modeling and Delivery

Using enough modeling to reduce risk and align the team while keeping the focus on delivering working software.

Documentation in Agile

Producing lean, valuable documentation that serves a real audience, rather than comprehensive documents by default.