Agile modeling
Some keyphrases from the book “Agile Modeling”, Scott W. Ambler, 2002
This book is not how to model, but how to model in agile enviroments.
Agile Modeling Values
- Communication
- Simplicity
- Feedback
- Courage
- Humility
Principles
- Software is your primary goal
- Enabling the next effort is your secondary goal
- Travel light
- Assume simplicity
- Enable change
- Incremental change
- model with purpose
- Multiple models
- Quality work
- Maximize stakeholder investment
- Conent is more important than representation
- Everyone can learn from everyone else
- Know your models
- Local adaptation
- Open and honest communication
- Work with people’s instincts
Practices
- Iterative and Incremental Modeling
- Apply the right artifacts
- Create Several models
- Iterate to Another Artifact
- Model in small increments
- Teamwork
- Model with Others
- Active stakeholder participation
- Collective Ownership
- Display Models Publicly
- Simplicity
- Create Simple Content
- Depict Models Simply
- Use the Simplest Tools
- Validation
- Consider Testability
- Prove it With Code
- Productivity
- Apply Modeling Standards
- Apply Patterns Gently
- Reuse Existing Resources
- Documentation
- Discard Temporary Models
- Formalize Contract Models
- Update only when It Hurts
- Motivation
- Model to Communicate
- Model to Understand
Chaos and Order: Chaordic
Dee Hock (1999) founder of VISA, provides the following definition for the term chaordic:
The mix of chaos and order is often described as a harmonious coexistence displaying characteristics of both, with neither chaotic nor ordered behavior dominating. Some[who?] hold that nature is largely organized in such a manner; in particular, living organisms and the evolutionary process by which they arose are often described as chaordic in nature. The chaordic principles have also been used as guidelines for creating human organizations — business, nonprofit, government and hybrids—that would be neither centralized nor anarchical networks.
A nice one
When all you have is a hammer, everything looks like a nail.
-Unknown
Agile Work Areas
You realy need a whiteboard.
Recognize That There Is No “I” in Agile
Thoughts
I have to read Beck’s book on XP and Cohn’s User Stories Applied: For Agile Software Development.
How the cost works with agile? How I can predict the duration of the project if the stakeholder can change user stories for ever driving dev-team to endless refactorings. Or I have got this worng?