|
|
|
» Agile Modeling (AM) Principles v2
Agile Modeling (AM) defines a collection of core and supplementary principles that when applied on a software development project set the stage for a collection of modeling practices. Some of the principles have been adopted from eXtreme Programming (XP) and are well documented in Extreme Programming Explained, which in turn adopted them from common software engineering techniques. For the most part the principles are presented with a focus on their implications to modeling efforts and as a result material adopted from XP may be presented in a different light.
The AM principles are organized into two lists, core principles which you must adopt to be able to claim that you're truly taking an Agile Model Driven Development (AMDD) approach and supplementary principles which you should consider tailoring into your software process to meet the exact needs of your environment.
Core Principles:
- Assume Simplicity
- Embrace Change
- Enabling the Next Effort is Your Secondary Goal
- Incremental Change
- Maximize Stakeholder ROI
- Model With a Purpose
- Multiple Models
- Quality Work
- Rapid Feedback
- Working Software Is Your Primary Goal
- Travel Light
Supplementary Principles:
- Content is More Important Than Representation
- Open and Honest Communication
Author: Scott W. Ambler
Read More ...
| Comments |
Currently, there are no comments. Be the first to post one!
You must be logged in to post a comment. You can login here
|
|