Practices of Agile Modeling AM

1
Practices of Agile Modeling (AM)

• From the writings of Scott Ambler

2
Active Stakeholder Participation

• Include users who can make decisions
• Include management a champion
• Operations staff
• Help desk staff

3
Apply the Right Artifacts

• Use proper diagram for purpose of understanding /
  communicating model or process.
• E.g., Static structure class diagram
• E.g., Business process activity diagram
• Sometimes a non-UML diagram is better.
• Know strengths/weaknesses of each diagram

4
Collective Ownership

• Models (diagrams) should be public and displayed
  publicly
• Anyone on team should be encouraged to understand
  and work on diagrams
• Promotes open and honest communication
• Model with others to increase understanding and
  to communicate ideas

5
Consider Testability

• Think about how your models will be tested as
  code.
• What test data/ conditions are needed?
• Write code early on to test new algorithms and
  designs.
• Builds quality assurance into process.
• Prove concepts with actual code!

6
Create Several Models in Parallel

• Since each UML diagram has specific uses
• Create new diagrams as need/problem arises
• May have many unfinished diagrams at once. If you
  are stuck, iterate to another artifact to capture
  your ideas.

7
Create Simple Content

• Keep models are minimal as possible while
  retaining key concepts
• Can always add new features/details later
• Complicated models detract from understanding!

8
Depict Models Simply

• Use only a few types of diagrams, simpler the
  better
• Restrict use of diagramming notation
• Model in small increments increases agility to
  deliver software features to users quickly.

9
Misc

• Travel light Discard temporary models
• Reuse existing models/designs when possible
• Update only when it hurts diagrams do not have
  to be perfect
• Remember the deliverable product is code, not
  UML!